I've watched more than one company try to cut its way out of a growth problem. It rarely works, and the way it fails follows a pattern worth understanding.
The setup is almost always the same. Revenue is declining, new business has slowed, and the customers they have aren't sticking the way they used to. Things are heading the wrong direction, and the instinct, the one that feels responsible and decisive, is to reduce spend. So the company runs a reduction in force. Across the board, every function cut by roughly the same amount. It feels fair and it feels disciplined.
Revenue keeps declining.
So they do it again. Another round, again spread evenly across the org. And here's where this ends up: revenue is still falling, and now there aren't enough people to actually fix it. The teams that could have driven the turnaround, the ones closing new business and keeping existing customers, got cut at the same rate as everything else, because "fair" meant "equal." Now they have to re-hire into those exact functions and wait months for new staff to ramp before the turnaround can even begin. The cuts didn't save time. They cost time.
This is the trap. When cash is tight, "reduce burn" sounds like a single, obvious instruction. It isn't. Burn is not one number to be minimized, it's a collection of very different expenses that happen to share a bank account. And treating them all the same is how you cut the thing that was keeping you alive.
Not All Burn Is Equal
Here's the reframe that changes how you cut: the dollar amount of an expense tells you almost nothing about whether you should cut it.
Thirty thousand dollars a month spent on something that directly drives revenue and thirty thousand dollars a month spent on something frivolous are, on a spreadsheet, identical. Same line, same magnitude, same impact on runway. But they are not the same expense. One is an investment with a return; the other is pure cost. If you're looking at burn as a single number to shrink, you can't tell them apart, and under pressure, the frivolous one often survives while the productive one gets cut, because the productive one is usually bigger and therefore looks like the better "win."
That's the whole game. Before you cut anything, you have to know which of your dollars are working and which aren't. That's a metrics question, not a budgeting one, and it's one of the reasons connected FP&A matters long before you think you need it.
The Two Questions I Actually Ask
When I'm helping a founder decide what to reduce, I'm not looking at the size of expenses. I'm running each one through two filters.
1. Does this dollar directly drive revenue?
This is the first and most important test. Some spend is directly connected to bringing in or keeping revenue: the people closing deals, the team preventing churn, the marketing that reliably produces pipeline. Other spend is genuinely discretionary, nice to have, defensible in good times, but not load-bearing. The mistake in the pattern above was failing to draw this line. Had they drawn it, they'd have seen that cutting their revenue-driving and retention functions was self-defeating: those weren't costs, they were the mechanism for reversing the exact problem they were trying to solve. You protect the revenue engine and cut around it, not through it.
2. Is this cost fixed or variable?
The second lens is about flexibility. Fixed costs, salaries, leases, annual contracts, are committed and hard to unwind, and cutting them (especially headcount) is slow, painful, and expensive to reverse. Variable costs flex with activity and can often be dialed down quickly without permanent damage. When you need to reduce burn, variable costs are usually where to look first, because you can adjust them without dismantling capability you'll need again in three months. Reaching straight for headcount, a fixed cost with a long, costly reversal, should be a late move, not a first one. In the pattern above, they led with it, twice, and are now paying the reversal cost.
Run those two questions across your spend and a very different picture emerges than "cut everyone 15%." You find the discretionary, variable dollars that aren't driving anything, and you find the revenue-driving spend you should defend even when money is tight. A rolling 13-week cash flow forecast is the tool most founders use to keep both views in front of them at once.
Why "Fair" Cuts Are Usually the Wrong Ones
The across-the-board cut is popular because it feels equitable and it's easy to execute. No hard conversations about which team matters more; everyone shares the pain equally.
But a business isn't a set of equally important parts. Some functions are directly responsible for the revenue you're trying to protect, and some aren't. An even cut ignores that entirely, it takes the same slice from the team saving your renewals as it does from the team you could lose without anyone noticing for a quarter. "Fair" optimizes for the appearance of even-handedness. It does not optimize for survival.
The harder, better path is to make deliberate, uneven decisions: protect what drives and defends revenue, cut deeper into what doesn't, and be honest about which is which. That requires knowing your numbers well enough to defend each call, which is exactly the work that gets skipped when panic sets in.
Reducing Burn the Right Way
Pulling this together, here's the sequence I'd run instead of a reflexive cut:
Start with the metrics, not the spreadsheet. Understand what each meaningful expense is actually producing before you decide its fate. An expense you can't tie to an outcome is a candidate for cutting; an expense with a clear return is a candidate for protecting, sometimes even growing.
Cut discretionary before essential, and variable before fixed. Exhaust the spend that isn't driving anything and can be unwound easily before you touch committed costs or the revenue engine.
Treat headcount as the last lever, not the first. It's the slowest to reverse and the most expensive to get wrong, as the companies in that pattern learned when they had to re-hire the capability they'd just eliminated. See our take on in-house vs. outsourced finance costs for how the same logic applies to your own team.
Protect the turnaround. If revenue is the problem, the people and spend that drive revenue are the solution, not the target. Cutting them doesn't extend your runway, it removes your ability to use it.
Reducing burn isn't about spending less. It's about spending deliberately: knowing which dollars are working, defending those, and being ruthless with the ones that aren't. Done that way, you extend your runway while protecting the parts of the business that were going to carry you out of the hole.
Done the other way, evenly, reactively, by size, you save money in the short term and lose the company slowly.
The Bottom Line
At Finative, helping founders understand the context behind their numbers, which spend drives the business and which just sits on it, is core to what we do. Our fractional CFO services and FP&A services are built for exactly this decision. If you're facing hard decisions about where to cut, we're happy to help you make them with the full picture in front of you.