Answering the question you were asked is easy. Asking whether it is the right question is the job.

The question arrives on a Tuesday. It is specific. Should we hire another project manager before the busy season. Should we buy the equipment this year. Should we update the forecast before the bank call. Should we make the tax move before year end.

It is a real question. You can name it. You can send it in a text. You can put it on the agenda. For owners and operators between $500K and $10M, that is often how the week starts. Something needs a yes or a no, and the business will not pause while you find a better framing.

Answering it cleanly feels like competence. You open the file. You run the math. You give a recommendation. The meeting ends on time.

We've noticed that this is also how a week gets missed. The asked question is usually the one you can already see. The week you are actually in is often sitting one layer under it.

The asked question is the one you can already name

Founders do not ask tactic questions because they are shallow. They ask them because tactics are what the calendar forces into language.

A hire has a start date. Equipment has a vendor waiting. Tax has a filing window. A forecast has a meeting attached to it. Those are nameable. They are also downstream of something quieter.

The hire question is often a capacity question, or a quality question, or a pricing problem wearing a job title. The equipment question is often a cash timing question. The tax question is often a liquidity question with a deadline on it. The forecast question is often a decision that has not been named yet, dressed up as a model.

If you answer the surface version, you can still be right on the numbers and wrong on the week.

Here's something we've learned the slow way. A clean answer to the asked question can still leave payroll timing, collections, and owner pay untouched. Those are the things that actually move the next thirty days.

A clean answer can still miss the week you are in

Imagine the hire is approved. The model said the margin could take it. The offer goes out on Thursday. Then two invoices that were supposed to land this week slip into next month. Payroll still hits on Friday. The new salary starts before the receivables catch up. Nobody was dishonest. The asked question just was not the whole question.

Or the equipment gets bought because the year is running out and the deduction looks attractive. The operating account can cover the deposit. It cannot cover the deposit, the insurance bump, and a slow January at the same time. The tactic was defensible. The week after the purchase is tighter than anyone said out loud.

This is not a story about bad math. It is a story about answering too quickly.

We see the same pattern with a forecast. Someone asks if the number is right. The honest reply might be that the number is internally consistent. That still does not tell you whether you should hire, wait, draw, or leave the money in the account. A correct forecast can still leave the decision unnamed.

When we are asked about a tax idea under a deadline, the pull is to treat the deadline as the decision. In those rooms, we said the cash flow has to come first. Not because the tax idea was foolish. Because the business still has to fund payroll, vendors, and the next sixty days. A savings that starves the operating account is not a savings you can use.

The asked question wanted a move. The real question was what the move does to cash this month and the next.

Same founder. Different phase. Different question.

A company burning cash for growth is not the same business as one getting ready to sell. It can be the same founder. Same product. Same logo on the truck. The question has still changed.

In a growth burn, the useful question is often whether the spend is buying a receivable you can actually collect, and whether the timing of that collection can carry payroll. Speed is the temptation. Cash conversion is the constraint. You can be winning on revenue and still be one slow week away from a hard Friday.

When the same company starts thinking about a sale, speed is no longer the point. The useful question becomes whether the numbers tell a story a buyer can sit with, whether owner pay is mixed into the operations, and whether collections look like a system or a scramble. The hire you would make in year three of growth is not the hire you would make eighteen months before a transaction.

We see owners ask growth questions inside a harvest season, and harvest questions inside a build season. Both can sound sophisticated. Both can be the wrong week.

Diagnosing the phase is not a personality exercise. It is looking at what the business is trying to protect right now. Growth protects momentum. A sale protects a clean story and a clean cash cycle. A tight month protects Friday. If you skip the phase, you will give a good answer to last year's question.

The founder has not become a different person. The decision has.

What the right question looks like in the working week

The right question is usually plainer than the tactic. It lives in cash, collections, payroll timing, and owner pay. Those four will tell you more about whether the asked question is the real one than a longer memo will.

If someone asks whether to hire, the working week version is closer to this. What is late right now, and would another person change that this month, or only change the org chart. Can collections support another paycheck before the new work turns into cash. What happens to owner pay if the hire is a quarter early. A role can be obviously needed and still be a month too soon.

If someone asks whether to buy equipment, the working week version is whether the operating account can absorb the purchase without moving payroll or stretching vendors. It is also whether the job that needs the equipment is actually booked, or only hoped for. Hope is not a receivable.

If someone asks for a new forecast, the working week version is which decision the forecast is supposed to change this month. Hire or wait. Draw or leave it. Push collections or extend terms. A forecast that does not change a decision is a document, not a question.

If someone asks about tax, the working week version is cash first, then timing, then the filing. We said the cash flow has to come first because that is the order the business lives in, even when the calendar is shouting about December.

Owner pay belongs in this list because it is where a lot of otherwise sound answers quietly fail. A hire, a truck, or a contribution can look fine until you put the owner's actual draw back into the week. Then the math changes. The right question includes the person who has to live on the other side of the decision, not only the company on the spreadsheet.

How to tell you are answering versus diagnosing

Answering has a shape. The question comes in. The file opens. The recommendation goes back. You can feel the relief of completion.

Diagnosing is slower at the front and faster later. You repeat the question so it is shared. Then you ask what would have to be true for that answer to be useful this month. Then you look at cash, collections, payroll, and owner pay before you bless the tactic.

You are answering if the conversation never leaves the item that was asked. You are diagnosing if the conversation names the decision underneath it.

A few tells we use on ourselves, and that you can use in your own meetings:

If you can give the answer without looking at the next four payroll dates, you are probably answering.

If you can bless a hire without knowing what is uncollected and how old it is, you are probably answering.

If the forecast is being updated because it is the end of the month, and not because a decision is waiting, you are probably answering.

If the tax idea is being measured on savings and not on what it does to the operating account, you are probably answering.

If owner pay is treated as a leftover, instead of a line that has to survive the decision, you are probably answering.

Diagnosing does not mean stalling. It means the first useful output is a named decision, not a named deliverable. Should we hire is a request. Can we fund this role through a slow collections month without cutting owner pay is a decision. Those are not the same piece of work.

The second one takes a little more sitting still. It also tends to prevent the expensive kind of being right.

Name the decision. Then the work follows.

A useful partner is not the person who replies the fastest. It is the person who can say, plainly, here is what you asked, and here is what we think you are actually deciding.

Then the work has somewhere to land. The hire model, the cash view, the collections push, the tax timing, the forecast. Those are tools. They get useful after the decision has a name.

We've learned not to treat that pause as cleverness. The pause is the job. Answering the question you were asked is easy. Anyone with a file and a deadline can do that part. Asking whether it is the right question is what keeps the next thirty days from becoming a surprise.

The work follows the decision. Not the other way around.

Answering the question you were asked is easy. Asking whether it is the right question is the job.

If you want a clear read on the question you are in, and whether it is the one worth answering this week, we will spend 30 minutes on it with you.

No pitch. No pressure. Schedule your 30-minute diagnostic with Arrowhead Strategy Group.