I was recently reviewing the financial model of a software company with aggressive growth ambitions.

The ambition wasn’t the problem. The numbers were. Over the previous six months, the pipeline had remained anaemic and new revenue was non-existent. During that same period, the founder had progressively hired six software engineers, adding more than $1.2m of annual payroll.

For context, this was a company with around $5m of ARR. So, another $1.2m of engineering payroll was hardly a rounding error. There’d also been almost no corresponding investment in sales or marketing.

There was no announcement by the founder that product was the constraint on growth. Nor that the company would therefore commit to engineering rather than distribution. No grand strategic declaration. No carefully crafted deck entitled Where We’re Placing Our Bets.

Each engineer had been hired for a reason. A roadmap gap. An AI feature. A technical bottleneck. A customer request. Infrastructure that needed work. All perfectly reasonable.

But once those decisions were put together in the financial model, something larger became visible. Whatever the founder intended, the company was putting its incremental capital behind product, i.e., it had made a strategic bet.

The cost wasn’t theoretical. The additional payroll massively increased cash burn and reduced runway to less than 12 months. The company had to go back to investors for a bridge round earlier than planned.

Your spending eventually becomes your strategy

Strategy is usually discussed in terms of markets, products, positioning and competitive advantage. Founders talk about moving upmarket, entering a new geography, building an enterprise product or becoming the category leader.

But strategy also shows up somewhere less glamorous: the payroll file.

Look at where headcount has grown, which investments keep getting approved, where the next dollar goes and which initiatives remain perpetually deferred. Those decisions often tell you more about the strategy a company is actually pursuing than the strategy deck does.

A founder may say distribution is the priority. But if most incremental hiring has gone into engineering, the financial commitments are telling a different story.

This usually doesn’t happen because anyone makes one dramatic decision. You hire an engineer because the roadmap is slipping. A few months later, an important prospect needs a feature. Technical debt becomes uncomfortable, so you hire again. Someone leaves and gets replaced.

Every decision is local and comes with a viable business case. The capital commitment isn’t.

Six engineers makes the pattern obvious. But the same thing happens at a smaller scale. Two hires here, another software platform there, a contractor who quietly becomes permanent, or a replacement hire who somehow costs 30% more than the person being replaced.

None of them looks like a strategic bet on its own. Add them together and they can become one.

Immediate problems have an advantage

Operational problems are loud. A customer complaining about a missing feature is visible. A support queue getting longer is visible. A platform slowing under load is visible. A roadmap falling behind is visible.

The opportunity cost of solving those problems is harder to see. You don’t see the salesperson you didn’t hire, the market you didn’t enter or the experiments you couldn’t run. And runway has the annoying habit of looking fine until it suddenly isn’t.

That gives immediate problems a natural advantage when capital gets allocated. They arrive with evidence. Customers are complaining, deadlines are slipping and people are asking for help. The alternative is usually hypothetical and, unfortunately, hypothetical problems rarely send Slack messages at 11pm.

Every function can also make a convincing case for more resources. Customers always want more product. Sales always wants more leads. Engineering always has technical debt. Support always has something breaking.

None of that is surprising. Growing companies have problems. The question is which of those problems deserves the next meaningful commitment of capital.

Not every problem deserves the next dollar

For many B2B SaaS companies, one of the biggest tensions is between product and distribution.

Suppose growth is weak. The problem may genuinely be product. Customers aren’t activating, retention is poor, or deals are stalling because critical functionality is missing. In that situation, hiring more salespeople could simply send more prospects towards something that isn’t ready.

But the reverse happens too. Customers who reach the product stay. They get value. Win rates are respectable once qualified buyers enter the funnel. The problem is that there simply aren’t enough qualified buyers.

Adding another few engineers in that situation may produce a better product without producing much more revenue.

Neither case is always obvious. Product gaps are particularly good at making themselves known. There will always be another feature, integration or piece of technical debt demanding attention. Product roadmaps have never been famous for declaring themselves finished.

Distribution problems can be deceptive too. A thin pipeline doesn’t automatically mean you need three more salespeople. The positioning may be wrong, the market may be too small or the sales motion may simply not work.

The objective isn’t to identify one perfect bottleneck and throw money at it. It’s to be explicit about what you believe the investment is going to change.

What would have to become true?

This is the question I find most useful when looking at a material spending decision:

What would have to become true for this investment to have been worth making?

Take an engineering hire. A weak answer is that the team is stretched and the roadmap is behind.

That may be completely true. It still doesn’t tell you what economic outcome the additional cost is expected to produce.

A better answer might be that you’re losing enterprise deals because you don’t support a particular integration. The pipeline contains $1.5m of ARR where this is a documented blocker. Another engineer should allow you to ship it within four months and, based on those opportunities, improve conversion.

That can still turn out to be wrong. But now there’s a hypothesis.

You can ask whether a $200k annual cost is proportionate to the opportunity, whether four months is fast enough, and whether there’s genuine evidence that the feature is influencing buying behaviour.

The same logic applies to a sales hire.

Suppose your case is that one AE can work $1m of qualified pipeline a year and your win rate is 25%. That implies roughly $250k of new ARR. At an 80% gross margin, that produces about $200k of first-year gross profit.

If the AE costs around $200k fully loaded, that isn’t obviously a compelling investment once you allow for ramp time, marketing support and the minor inconvenience that salespeople rarely behave exactly as they do in the model.

The economics may still work. Perhaps the rep turns that pipeline more than once a year. Perhaps expansion is strong or customer lifetime is long enough to justify the acquisition cost. But now you know what has to be true.

And if you can’t answer basic questions such as how much qualified pipeline an existing AE can handle, what they convert, or how long they take to ramp, that tells you something too. Before adding another salesperson, the first problem may simply be understanding the productivity of the sales capacity you already have.

The point isn’t to demand certainty. Startups don’t offer much of that. It’s to turn a spending request into an explicit economic hypothesis rather than accepting that the team is busy as sufficient evidence for another hire.

The cost isn’t just the cost

A dollar can only be committed to one thing at a time. Spending $1m on engineering doesn’t simply mean engineering costs $1m more. It changes what the company can afford to do next.

Perhaps the enterprise sales team gets delayed. Perhaps geographic expansion waits. Perhaps the next capital raise comes forward. Perhaps the business loses six months of runway.

Some investments create new options rather than closing them. A product capability might unlock a new market. Better infrastructure might allow the company to pursue enterprise customers. The point is that a meaningful commitment changes the choices available afterwards.

This matters particularly in SaaS because many of the largest cost decisions are recurring. You can stop a $50k experiment if it doesn’t work. A team of ten people is a somewhat less elegant experiment.

There’s also a compounding effect. Hire three people and you may soon need a manager. Build a larger team and new infrastructure, software and coordination costs follow. Plans and dependencies start to form around the original decision.

Before long, continuing in the same direction becomes easier than questioning whether the original thesis still holds. A decision that made sense six months ago can become the justification for another decision today, even though the circumstances have changed.

That’s why size, duration and reversibility matter. A company with three years of runway can tolerate investments with longer feedback loops than one with nine months left. Once runway gets short, you’re not just evaluating the expected return. You’re asking whether the company has enough time to discover whether the thesis was right.

That was the problem with the company I was reviewing. By the time those engineering decisions had accumulated, the business hadn’t simply increased its product investment. It had materially shortened the time available to prove the growth thesis.

The consequence was a bridge round. Nothing focuses attention on capital allocation quite like having to explain to existing investors why you need to see them again sooner than expected.

Look at your own numbers

There’s a fairly simple way to see whether this is happening in your company.

Take the hires and meaningful recurring spending commitments you’ve added over the last 12 months. Use the annual fully loaded cost of each hire, not just salary, and include recurring software, contractors or other commitments large enough that you would have discussed them before approving them.

For replacement hires, count the increase in annual cost rather than treating the entire replacement as new investment. You’re trying to understand how the cost base changed, not reconstruct payroll movements with the enthusiasm of a forensic accountant.

Group the additions by function: product and engineering, sales and marketing, customer success, operations and infrastructure. Then add them up.

You don’t need a six-tab financial model for this. Twenty minutes and a spreadsheet will probably do. And yes, I realise I’m a finance person recommending a spreadsheet. There are limits to reinvention.

Now ignore what your strategy deck says for a moment. Look only at where the incremental money actually went and ask:

If you’d been shown this allocation 12 months ago, would you have deliberately chosen to make this bet?

Maybe the answer is yes. If most incremental capital went into engineering because retention was poor and the product clearly needed work, that may be exactly what the company required.

But perhaps you said distribution was the priority and discover most incremental payroll still went into product. Or perhaps you thought you were conserving cash and find that a series of individually modest decisions added $800k to the annual cost base.

That’s useful information, but it isn’t yet a reason to start cutting people or reversing decisions.

The next step is to make the implied bet explicit. What outcome were those commitments supposed to create? Has that outcome started to appear? Is the evidence still supporting the original thesis? And if you were making the same decision today, knowing what you know now, would you still commit the capital?

If the answer is yes, keep going. At least you know what you’re betting on.

If the answer is no, the problem isn’t necessarily that the original decision was bad. The business may simply have changed. What matters is recognising that before another six months of perfectly defensible decisions quietly commits the next million dollars in the same direction.

Founders experience spending decisions one at a time. Capital experiences them in aggregate. By the time you add those decisions together, a series of perfectly sensible operating choices may already have become your strategy.