Runway Scenario Analysis: Base, Downside and Upside Cases for Startups

What is runway scenario analysis?

Runway scenario analysis is the practice of calculating how many months of cash a startup has under several different assumptions instead of one. Most teams compute a single runway number. Scenario analysis replaces it with a range, usually a base case, a downside case and an upside case, so you can see how fragile or how safe that number really is.

A single number feels precise, but it hides the assumptions behind it. It assumes revenue arrives as planned and costs stay where they are. Neither is guaranteed. Runway is cash divided by net burn, so any change in revenue or spending moves it, and a small slip in one input can remove months.

The goal is not to predict the future. It is to know in advance which events would hurt, how much they would cost in months and what you would do about each one.

Why one runway number is not enough

The standard formula is simple: cash in the bank divided by monthly net burn. It is a good starting point, and our guide to calculating startup runway walks through it. The weakness is that it treats today's burn as permanent. In a real company, revenue grows or shrinks, hires land, a big customer pays late and a contract renews or does not.

Scenarios turn those vague worries into numbers. Instead of feeling that a slow quarter could be dangerous, you can say that a 20% revenue miss costs about 1.3 months. That sentence is easier to act on and easier to explain to a co-founder or an investor.

Scenarios also protect against optimism. Founders tend to plan around the case they hope for. Writing the downside next to it forces an honest conversation before the money is tight.

How to build base, downside and upside cases

Start with the base case: your best honest estimate for the next 12 months of revenue and costs. Use real numbers from the last three months, not the plan from your deck. Calculate net burn as gross burn minus collected revenue, then divide cash by it. If you need a refresher on the two burn measures, read our gross burn vs. net burn guide.

Next, change only the drivers that matter. For the downside, pick two or three risks that are realistic for your business: revenue 20% below plan, a key customer lost, a hire that costs more than expected or a payment that slips by a quarter. For the upside, do the opposite with the same discipline. Do not stack every bad event together, because that is a disaster case, not a downside.

Keep the changes few and visible. If a scenario needs ten tweaks, nobody will trust it. Three clear drivers and one sentence per scenario is enough, and you can extend to a weekly view with a 13-week cash forecast when the downside gets close.

A worked example with simple numbers

Take an illustrative startup with $600,000 in the bank, $80,000 of monthly gross burn and $30,000 of monthly collected revenue. Base case net burn is $80,000 − $30,000 = $50,000, so runway is $600,000 ÷ $50,000 = 12 months.

In the downside, revenue comes in 20% lower, at $24,000. Net burn becomes $80,000 − $24,000 = $56,000 and runway is $600,000 ÷ $56,000 = about 10.7 months. In the upside, revenue is 20% higher, at $36,000. Net burn is $44,000 and runway is $600,000 ÷ $44,000 = about 13.6 months. These are made-up figures to show the mechanics, not a benchmark.

Now add a response. If the team cuts $6,000 of monthly costs once the downside appears, gross burn falls to $74,000, net burn returns to $74,000 − $24,000 = $50,000 and runway is back to 12 months. A scenario is most useful when it ends with an action and a number like this.

Turn scenarios into trigger points and decision dates

The most valuable output of scenario analysis is a date, not a number of months. Work backwards from the day cash would run out in the downside case. If a fundraise or a bridge conversation takes you around six months in your own experience, a 10.7-month downside means you must start by about month 4 to 5. That is an assumption to replace with your own timeline, not a rule.

Then define trigger points: specific, measurable events that tell you which scenario you are living in. Examples are two months in a row of revenue under 85% of plan, a customer payment more than 30 days late or runway falling below a number you set in advance. Each trigger should be paired with a pre-agreed action such as pausing a hire, cutting a cost line or starting investor conversations.

Writing the actions down before you need them removes emotion from the decision. When the trigger fires, you are following your own plan instead of debating whether the situation is bad enough.

Common mistakes in runway scenarios

The first mistake is making the downside too mild. A scenario where revenue drops 2% teaches nothing. Choose a miss that would genuinely hurt, such as a lost top customer, and see how many months it costs. The second mistake is treating revenue as booked when it is only invoiced; cash timing can turn a safe case into a risky one, which is why days sales outstanding matters.

Another mistake is ignoring the cost side. Hires, salary raises, annual software renewals and an office lease are often more certain than revenue. Model them as they will leave the account, not as an average. A third mistake is building the scenarios once and never revisiting them. Update them monthly, or whenever cash, hiring plans or the sales pipeline change by a meaningful amount.

Finally, do not confuse scenarios with a forecast you promise to investors. They are internal planning tools. Share them if they help the conversation, but present the base case as an estimate and the others as sensitivity.

Practice scenario thinking in Founder Runway

In Founder Runway, a run lasts 20 turns and every decision has four options. You pick a B2B, B2C or B2G business model and start at Pre-Seed, Seed, Pre-Series A or Series A. It is a learning game, not financial advice, but it lets you feel how a slow customer payment or an early hire changes your cash and runway.

A run can end in failure, a promising outcome, EBITDA positive or high-value exit potential. Replay the same stage with a different business model and compare how much room each choice leaves you.