Runway and Burn: The Two Numbers That Decide Your Startup's Next Year

Ask a founder their runway and you'll usually get a number with a smile. Check the maths and it's often wrong by three months — always in the optimistic direction. And three phantom months are lethal, because everything you'd do about a shortfall (raise, cut, pivot) takes at least that long.

This is the honest arithmetic, and what actually moves it.

The Real Calculation

Gross burn — everything that leaves the account monthly. Net burn — that, minus money actually collected (not booked, not invoiced — collected). Runway = cash in bank ÷ net burn.

Three corrections that turn the smile-number into the true one:

• Use the worst recent month, not the average. Averages hide the direction things are moving.
• Subtract committed one-offs — tax deadlines, annual renewals, the deposit, severance. These are landmines the monthly average never shows.
• Model revenue flat. If growth arrives, wonderful — you'll have extra runway. Planning on it is how founders discover, at month four, that hope was in the denominator.

Two runway numbers deserve to exist side by side: current-course, and if-revenue-stopped. The gap between them is your dependence on things going right. Wire the calculation into a live view — the AI-native finance tools keep it current without a weekly spreadsheet ritual, and the 13-week cash forecast covers the near-field detail.

The Thresholds That Should Trigger Action

• 18+ months: operate. Build, sell, don't think about money daily.
• 12 months: decide. If raising: start now — rounds take 6-9 months in honest markets. If not: pick the path to default-alive today.
• 6 months: act, no longer choose. Cuts made here save you; cuts imagined here don't.
• 3 months: triage. Every conversation is cash-in-30-days or it doesn't happen.

The pattern in every startup post-mortem: the founders knew at twelve months and moved at five. The knowing was never the problem.

What AI Changes About Burn — Genuinely

The 2026 difference isn't that AI "saves money" in the abstract. It's that a disciplined team now gets more distance per rupee in three specific ways:

1. Headcount deferred. The marketing hire, the ops admin, the first support person — big slices of these roles are now workflows. Every hire deferred six months at startup salaries is a month of runway, roughly. Run the automate-before-you-delegate filter before every offer letter.
2. Founder throughput. The constraint on early startups is founder hours. AI fluency returns 10-15 of them a week — from drafting, research, reporting, admin. That's not a metaphorical saving; it's the difference between shipping and stalling at the same burn.
3. Spend visibility. Monthly, feed the expense export to your assistant: "rank by growth rate, flag anything unused, find duplicates." Ten minutes; it routinely finds 5-8% of burn hiding as zombie subscriptions and forgotten upgrades.

The caution that pairs with this: AI spend itself creeps. Seats, tokens, tools nobody opens. Same audit, same ruthlessness — the stack serves runway, not the reverse.

Cut vs Push: The One-Question Tiebreak

At every threshold the board asks: extend runway or spend for growth? The tiebreak: do your unit economics deserve fuel? Positive contribution margin, payback under a year, cohorts improving — push, even at the cost of runway. Anything else — cutting isn't retreat, it's buying time to fix the machine before feeding it. (The unit economics guide is the companion read.)

Runway isn't a finance metric. It's the clock on every experiment you're allowed to run. Founders who treat it that way — and who use the tools to stretch it — simply get more tries. That mindset, with the full toolkit, is what AI for Startups is built around.