The most common mistake in startup runway planning during growth is cutting whatever is easiest to cancel this month, without a forecast that shows what the cut actually saves over the next two quarters. The consequence is a runway that looks longer on paper while the parts of the business that produce cash quietly weaken. Decide cuts in the order the forecast supports, not the order the invoice list suggests.
Build the forecast before choosing anything to cut
Before discussing specific cuts, get clear on what your financial information can actually support. A runway decision made from a bank balance and a rough sense of next month's sales is a guess with a spreadsheet attached. What you need is a rolling cash forecast: opening cash, committed inflows, committed outflows, and the timing gap between when you pay suppliers and when customers pay you.
The forecast should run at least thirteen weeks forward, week by week, and ideally extend to a full year at monthly granularity. The thirteen-week view catches the near-term squeezes, Cfo Services like payroll dates landing before a large receivable clears. The longer view answers the strategic question: if revenue stays flat, when does cash hit a level you consider the floor?
Growth companies often have a forecast that is really a budget with optimism baked in. The two documents serve different purposes. The budget expresses what you intend to happen; the cash forecast models what happens to cash if collections slip, a large customer delays, or hiring proceeds as planned. Run at least one scenario where revenue comes in below plan and one where it arrives on schedule but pays late.
Watch the working capital line specifically. A company can grow revenue every month and still burn cash faster, because inventory, receivables, and prepaid expenses all absorb cash before revenue returns it. When that is happening, the first lever is not a headcount cut; it is collection terms, inventory levels, or payment timing with suppliers.
If you lack the in-house capacity to build this, fractional finance support is a common arrangement at this stage. The point is not the title of whoever builds it. The point is that the forecast exists, someone owns updating it weekly, and the management team actually reads it before making spending decisions.
What to protect: the functions that generate and collect cash
Some spending looks discretionary in the accounting software but is structurally load-bearing. Sales activity, even expensive sales activity, is what produces the inflows your runway depends on. Collections work, meaning someone actively chasing invoices, is what converts booked revenue into cash. Cutting either one improves this month's burn number while damaging the only mechanism that ends the burn.
Protect the finance function itself, too. It is tempting to treat bookkeeping, forecasting, and investor reporting as overhead that a founder can absorb. In practice, when the person doing finance work is also running the company, the forecast goes stale precisely when it matters most. Late or inconsistent financials also create problems later: if you raise debt, bring in equity, or sell the company, the diligence process will examine the quality of your records, and rebuilding them under time pressure costs more than maintaining them.
Product and delivery capacity sits in a middle zone. If cutting it means failing current customers, the savings are borrowed against your reputation. If it means pausing speculative features that no current customer has asked for, it may be the right cut. The distinction is between capacity that serves signed revenue and capacity that serves hoped-for revenue.
One practical test: for any line item, ask which forecast row it feeds. If the answer is an inflow row or a row protecting an existing contract, it stays. If the answer is a hypothesis, it becomes a candidate. This keeps the conversation factual instead of turning every cut into a territorial argument.
None of this means protected functions escape scrutiny. Protecting sales activity does not mean protecting every tool subscription the sales team once trialed. Protecting finance does not mean paying for reporting nobody reads. Audit the spending inside a function before deciding whether the function itself shrinks.
Three cutting approaches compared
Founders under cash pressure tend to choose among three broad approaches, and the differences between them matter more than any individual line item. One is the across-the-board trim, where every budget line is reduced by a similar proportion. One is the staged, forecast-driven cut, where you sequence reductions based on scenario outcomes. One is the structural reset, where you revisit the entire cost base and operating model at once.
| Attribute | Across-the-board trim | Staged, forecast-driven cuts | Structural reset |
|---|
| Speed to implement | Fast, often within one cycle | Moderate, follows the forecast cadence | Slow, usually a quarter or more |
| Protection of revenue drivers | Weak, cuts fall everywhere equally | Strong, cuts follow scenario analysis | Depends on the quality of the redesign |
| Demand on management time | Low | Medium, requires weekly attention | High, can dominate a quarter |
| Fit when runway is comfortable | Poor, solves a problem you may not have | Good, becomes routine management | Excessive for tuning |
| Fit when runway is short | Rarely enough on its own | Works if started early enough | Often necessary |
| Message to the team | Shared pain, low information | Reasoned, tied to stated criteria | Clear but disruptive |
The across-the-board trim has one honest use: it buys time when a decision must land within days. Its weakness is that it cuts the productive and the speculative at the same rate, which means the ratio between them never improves. If you apply it, treat it as a stopgap with a stated expiry, not a strategy.
The staged approach fits most growth situations because it matches how uncertainty actually resolves. You cut the clearly speculative items now, define tripwires, and hold deeper cuts in reserve until the forecast says they are needed. It requires the discipline to act when a tripwire is crossed, not to renegotiate it.
The structural reset is the honest answer when the forecast shows that no sequence of trims gets you to a sustainable position. It carries real costs: distraction from customers, attrition of people you wanted to keep, and a period of reduced delivery capacity. Choosing it late, after months of incremental cuts have exhausted goodwill, is usually worse than choosing it early and deliberately.
Order of operations: what to cut first, in practice
With the forecast in place and an approach chosen, the sequence itself follows a fairly consistent logic. The earliest cuts should be the ones with the longest lag between decision and cash impact, because those are the savings you bank rather than merely announce. A subscription cancelled today stops next month's charge; a hiring plan paused today stops a salary that would have started in two months and carried payroll taxes and benefits on top.
A workable sequence for most growing companies:
- Unused and duplicate tools: software that nobody has logged into, overlapping subscriptions, seats held for roles that went unfilled.
