Cutting burn without killing momentum

Every cut removes two things

A cut removes a cost. It also removes some amount of capacity: the ability to build, sell, support, or decide. Those are never removed in equal proportion, and the whole skill is in the ratio.

Cancelling a licence nobody has opened in four months removes cost and no capacity. Letting go of the one person who understands your billing logic removes a salary and roughly all of your ability to change how you charge. Both show up in the burn figure as a number going down. Only one of them is a saving.

So the question to ask about any proposed cut is not how much does this save. It is what can we no longer do, and does that matter to the plan?

Cut in order of capacity, not size

The instinct is to sort the expense list by amount and start at the top. That is backwards. Sort by how much capacity each line carries, and work up from zero.

1. Dead weight. Unused seats, duplicate tools, the staging environment for a product you shelved, the annual plan for something you use twice a year. Pure cost, no capacity. Do all of this in an afternoon and stop congratulating yourself. It is housekeeping, not strategy.
2. Deferrable spend. The rebrand, the conference, the second monitor round, the hire you were going to make in Q3. Real value, but value that keeps. Delay does not destroy it.
3. Substitutable spend. The same job done a cheaper way. A smaller plan, a contractor instead of an agency, self-serve instead of managed. Capacity preserved, quality slightly down, cost meaningfully down.
4. Capacity itself. Headcount, and the tools your team actually works in every day. This is where cutting starts costing you the thing you were trying to protect.

Most teams in trouble skip straight to four because it is the only category big enough to move the number quickly. Sometimes that is genuinely correct. It should never be the first move, and it should never be the only move you have thought about.

Four cuts that look smart and usually aren't

1. The across-the-board salary cut

It feels equitable, which is exactly the problem. An even percentage is not an even burden: it lands hardest on the people with the least financial slack, and it is most easily ignored by the people with the most options, who are also, reliably, the people you least want to lose. You have applied a tax that your strongest people can escape and your weakest cannot.

A smaller team at full pay is almost always better than the same team at reduced pay. It is a worse conversation and a better outcome.

2. Cutting the thing that generates the pipeline

Marketing and sales spend is the easiest line to cut because its return is slow and arguable. That slowness cuts both ways. Stop it in March and the hole appears in July, long after everyone has agreed the cut was painless, and far too late to reverse cheaply.

If you are going to cut here, cut the parts you cannot attribute, and keep the parts you can. If you cannot attribute any of it, that is a measurement problem to fix before it becomes a cutting decision.

3. Tools that cost less than the time they save

A $200/month tool that saves a senior engineer four hours a month is not a cost, it is a discount. Cancelling it converts a visible line item into an invisible one: the same work still happens, just slower and by someone more expensive. Your burn barely moves and your throughput drops.

The honest test is whether the work goes away with the tool. If the work stays, you have not cut anything. You have relocated it somewhere the spreadsheet cannot see.

4. The slow drip of small cuts

Three rounds of trimming over five months does more damage than one deeper round in month one. Each round restarts the speculation, each round tells everyone the last round did not work, and nobody plans anything longer than the gap between them.

If a cut is coming, make it once, make it enough, and say out loud that it is the last one, then be right about that. Cutting to a number you actually believe in is the only version that buys back focus as well as cash.

The test worth applying to every line

Before signing off on any cut, ask:

If the plan works, will we regret having removed this?

Runway exists so you can reach a specific milestone: shipping the thing, closing the round, hitting the revenue number that makes the next conversation easy. A cut that buys three months but removes your ability to reach that milestone has not extended your life. It has extended the wait.

This is the same question behind default alive or default dead, asked from the cost side rather than the growth side. If you are default dead, cutting alone will rarely save you. You are trying to reach profitability, and past a point each cut moves that target further away. Know which problem you have before you pick the instrument.

Tell people the number

The strongest argument for transparency here is not moral, it is practical. A team that does not know the runway cannot help protect it. They approve spend they would have questioned, plan work at a horizon that no longer exists, and read every cut as a signal about something other than arithmetic.

You do not have to share the whole picture. “We have roughly nine months, we are cutting to get to fourteen, and here is the milestone that matters” is enough to change a hundred small decisions you will otherwise have to make yourself.

What to do with the months you bought

The cut is the easy half. The months are worthless unless something changes in them, and the most common failure after a successful cost reduction is relief. The team exhales, the pressure drops, and the same trajectory resumes on a longer timeline.

Decide the milestone before you cut, not after. Then check the burn against it monthly rather than quarterly, because a runway figure recalculated four times a year is a historical document.

Where to start

Read your last three months of expenses line by line and put every one into the four categories above. Most teams find the first two categories add up to more than they expected, and it costs nothing but an afternoon to find out.

You cannot categorise spend you have not captured, so if those numbers currently live in a spreadsheet someone updates when they remember, fixing that comes first. And if you want the arithmetic rather than the argument, the runway guide covers the formula and the five standard levers this post is the counterweight to.

Klerky keeps expenses, income and a runway figure in one place so the burn number moves when your spending does, rather than when someone remembers to update a tab. It is an operating view, not accounting — no P&L, no double entry, and you enter your own cash-on-hand figure, since there is no bank connection. If you only want the number, the runway calculator is free and needs no signup.