Runway scenario planning: why one number is never enough

Your runway looks backward, not forward

Ask any founder how much runway they have, and they'll give you a number instantly. Cash divided by burn rate. Three months rolling average. Clean, defensible, ready for any investor call.

The problem is what the calculation is actually measuring.

Your runway number is a backward-looking average. It reflects the business that existed two or three months ago, not the one operating today, and certainly not the one you'll be running in six months. The rolling average smooths volatility to produce a stable figure that is comfortable to report but increasingly detached from reality as your business evolves.

This is a fundamental limitation of what a single number can tell you. The runway metric was designed to answer one question: how long can we survive at our current rate? But that's rarely the question you actually need to answer when making operating decisions.

The question you need to answer is: where are we going?

When a customer delays renewal by a quarter, revenue recognition shifts. When expansion plans funded by Q3 revenue come in 20% under plan, the entire cash picture changes.

Each event arrives with a plausible explanation. No single moment looks like an emergency. Taken together, a company that reported 16 months of runway in January is having a very different kind of conversation by September, and the headline number never warned anyone.

This is the pattern that makes runway crises so reliably devastating. They are almost always predicted by information that was already available, if anyone had been willing to look at it honestly.

How runway scenario planning works: 3 numbers instead of 1

The solution is straightforward. Replace your single runway figure with three scenarios, run in parallel. Each one answers a different version of the same question: how long do we have?

1. Best case

Your plan plays out optimistically, but not fantastically. Key deals close on schedule. Hiring goes to plan. Revenue growth meets your targets. This is not a dream scenario; it is a realistic upside view where the assumptions you've made hold.

2. Base case

Your current trajectory with no major changes. This is probably the number you already have. It assumes revenue and burn continue roughly as they are today. It is useful for investor conversations. It is not useful for stress-testing your business.

3. Stress case

This is where scenario planning becomes genuinely useful. Take two of your key assumptions and make them wrong. A customer churns a quarter early. A new hire starts two months later than planned. Revenue comes in 20% below target. Given that, how long do you have, and what is the first thing that breaks?

Building the stress case takes roughly an hour. What it returns is something your base case cannot offer: a clear-eyed account of how much actual distance exists between your current position and the point where your options start disappearing.

Runway scenario planning: structure overview

‍

The spread is the metric, not the headline number

The headline runway figure matters far less than the spread between your base case and your stress case. Two companies can have identical runway numbers and be in completely different situations.

Consider two examples:

• Company A shows a base case of 13 months. Their stress case – two assumptions wrong, one quarter off-plan – lands at 11 months. That is a business with genuine predictability. The range of outcomes is narrow. It almost doesn't matter which version plays out; the company has time to respond.
• Company B also shows a base case of 13 months. But their stress case lands at 3. The headline number suggested one reality. The stress case reveals another entirely. That gap is the real risk. Everything looks fine until it doesn't, and when it doesn't, there's nothing left to work with.

A wide spread between base and stress case is a measure of exposure. It describes how much of a company's future depends on things going roughly to plan. It is not a reason for panic. But it is a reason to act, while acting is still possible.´

What the gap between base and stress case tells you

‍

Which assumptions to stress-test first

Not every assumption carries equal weight. Part of what makes runway scenario planning genuinely useful is that it forces you to find out which assumptions actually drive your outcome – rather than spending all your attention on the ones that feel important.

For some companies, the revenue line is stable and predictable, but burn is the risk. Headcount decisions, quarterly payment cycles, and infrastructure costs that scale faster than expected can all move the needle significantly.

For others, burn is under control. The uncertainty lives entirely in revenue timing: when a large contract closes, whether expansion revenue arrives on schedule, how quickly a new market ramps.

The right way to identify your load-bearing assumptions is to run your stress case multiple times, changing one variable at a time. The assumption that moves your stress case the most is the one that deserves the most attention. Often, it is not the assumption founders spend the most time thinking about.

Common load-bearing assumptions by company type:

• SaaS / subscription: Net revenue retention, enterprise deal timelines, expansion revenue ramp
• Marketplace / transactional: GMV growth rate, take rate stability, seasonality effects on burn
• Deep tech / hardware: Milestone-based funding triggers, unit economics at scale, production cost assumptions
• Services / consulting: Project pipeline conversion, utilization rate, key account concentration
  

When to start the funding conversation (the earlier the better)

One thing becomes obvious once you run your stress case: the right moment to start a financing conversation is almost always earlier than founders expect.

Most founders begin exploring funding when the headline runway number starts to look uncomfortable: somewhere around 9 to 12 months. By then, the stress case may already be showing 4 or 5. And closing a funding round, whether equity or debt, takes time.

Equity rounds typically take 3 to 6 months from first conversation to close. Debt facilities can move faster, but still require due diligence and structuring. Starting when your options are already narrowing means negotiating from weakness.

The stress case is precisely the tool that surfaces this in advance. It shows how thin the actual margin is long before the headline number reflects it. The founder who acts at 13 months base case / 6 months stress case has meaningful leverage. The one who waits until 8 months base case / 3 months stress case does not.

If your stress case shows less than 6 months of runway, you are already late. Start the conversation now.

This is also where non-dilutive funding can play a strategic role. Rather than using runway scenario planning only as a defensive tool (a way to spot problems) you can use it offensively, to identify the right moment to draw on a credit line and extend your runway before it becomes urgent.

The best financing decisions are made when you have leverage; scenario planning tells you exactly when that window is open.

How to build your three-scenario runway model

Building a working scenario model does not require a complex financial model or dedicated FP&A software. The goal is a living document you can update in under an hour when material assumptions change.

Step 1: Start with your base case

Take your current cash balance and your rolling 3-month average burn. This is your base case runway. It is the number you likely already report. Write it down explicitly, along with the three or four assumptions it rests on: revenue forecast, headcount plan, key contract timelines.

Step 2: Identify your top 5 assumptions

List the assumptions that, if wrong, would most materially change your cash position. Rank them by impact. Focus on timing (when does revenue arrive?) and magnitude (how much does burn change if a hire is delayed or brought forward?).

Step 3: Build the stress case

Take your top 2 to 3 assumptions and make them wrong simultaneously. A customer churns early. Revenue comes in 15 to 20% below plan. A hire accelerates by two months. Recalculate your monthly cash flow under these conditions and find the new runway number. Note which assumption moved it the most.

Step 4: Build the best case

Apply the same logic in the upside direction. Key deals close on schedule. Expansion revenue beats plan by 10%. Burn comes in slightly below forecast. This is your upper bound, not a target, but a ceiling for your planning range.

Step 5: Measure the spread and set your trigger

Calculate the gap between your base case and stress case. This is your primary metric. Then set a trigger: at what stress case runway do you start a financing conversation? At what point does the board need to be involved? Make this explicit before you need it.

Step 6: Update when assumptions change

A runway scenario model is only useful if it reflects current reality. Schedule a review whenever a material assumption changes: a large customer churns, a fundraise closes, a hiring plan shifts. Monthly updates are a reasonable cadence for most companies.

Common mistakes in runway scenario planning

Stress case that isn't actually stressful

The most common failure. A stress case where the "worst case" still assumes revenue grows 20% and the key enterprise deal closes on time is not a stress case. If your stress case looks almost identical to your base case, the scenarios are not doing any work.

Only updating after a crisis

Scenario models that only get updated when something has gone wrong have already failed at their primary job. The whole point is to surface problems before they become crises.

Confusing scenarios with forecasts

A forecast is a prediction of what will happen. A scenario is an exploration of what could happen. Your stress case is a deliberately pessimistic model designed to show you where you are fragile.

Treating the base case as the plan

The base case is a useful reference point, not a target. Running a business against a base case is like navigating by looking in the rearview mirror. The scenarios are what you actually manage against.

Ignoring the spread when it widens

A widening gap between base and stress case – even if both numbers still look comfortable – is an early warning signal. If last quarter your spread was 2 months and this quarter it is 5, something structural has changed. That is the conversation to have.

Summary: Runway scenario planning

• Your single runway number is a backward-looking metric. It tells you where you were, not where you're going.
• Replace it with three scenarios: best case (plan works), base case (current trajectory), and stress case (key assumptions fail simultaneously).
• The spread between base and stress case is the real metric. A narrow spread means predictability; a wide spread means exposure.
• Identify which assumptions are load-bearing by running your stress case with one variable changed at a time. Focus your attention there.
• The right time to start a financing conversation is when you still have leverage, not when your headline number forces the issue.
• Update your scenarios whenever a material assumption changes, not just on a fixed schedule.