Most financial models are built around a single set of assumptions about how the future will unfold. Revenue grows at X%. The key hire joins in month 3. The product launches in Q2. The enterprise deal closes in November.
That's a plan. It is not a strategy for uncertainty.
Scenario planning is the practice of building multiple, distinct versions of the future — not just optimistic and pessimistic versions of the same plan, but genuinely different trajectories with different assumptions — and understanding what each means for the business. Done well, it is one of the most powerful decision-support tools available to a leadership team.
Done badly — or not done at all — it leaves founders genuinely surprised by outcomes that were entirely foreseeable.
Why most startups don't do it (and why they should)
Scenario planning has a reputation for being a corporate planning exercise — something that belongs in McKinsey decks and strategic planning offsites, not in a 20-person startup. That reputation is wrong.
The argument for scenario planning is actually stronger in a small business than in a large one. A large corporation with diversified revenue streams and deep capital reserves can survive a scenario that materialises unexpectedly. A startup with 14 months of runway and 60% of ARR in three customers has far less margin for error. The cost of being genuinely surprised is higher — which means the value of thinking through scenarios in advance is also higher. External shocks make the point: our note on how tariffs affect margin forecasting runs exactly this kind of three-scenario exercise.
The practical barrier is usually time and model quality. Scenario planning requires a financial model that can be run in different configurations — one where key assumptions change and the outputs update automatically. If the model is a static spreadsheet with hardcoded numbers, running multiple scenarios means building multiple models. That's why model architecture matters, and why the investment in building a properly structured assumption-driven model pays back in the planning process.
The three scenarios every business should model
The instinct when asked to model "best case and worst case" is to add and subtract 10–15% from the base case revenue line. That is not scenario planning. That is sensitivity analysis, and it is considerably less useful.
True scenario planning involves changing the fundamental assumptions about how the business operates, not just adjusting the topline.
Base case: current trajectory maintained
The base case is the plan you're executing. Revenue growth at the rate implied by current pipeline and conversion. Hiring plan as modelled. No major strategic moves. This is the scenario that your budget, your headcount plan, and your board expectations are built around.
The base case should be honest, not optimistic. A base case that requires everything to go right is not a base case — it is a best case with a different label.
Downside case: a realistic adverse scenario
The downside case is not "everything goes wrong simultaneously." That scenario is almost always too extreme to be useful and too depressing to engage with productively. The useful downside scenario is one that is genuinely plausible — perhaps even likely — and examines how the business performs and what options it has.
Good downside scenario triggers:
- Revenue 25–35% below base (a specific cause: a major customer churns, a product launch delays 2 quarters, the competitive environment shifts)
- Key hire delays by 4 months (what is the revenue and operational impact?)
- A macro event reduces new business pipeline by 40% for two quarters
The downside scenario should answer: does the business survive this? If so, with what runway and what compromises? If not, what is the trigger point at which action must be taken, and what is that action?
Upside case: a genuinely better outcome
The upside case is often neglected — not because good outcomes aren't worth planning for, but because the planning implications seem obvious (good things happen, business grows, everyone is happy). But upside cases carry real planning requirements too.
What happens if revenue comes in 30% above plan? Do you have the hiring pipeline to capitalise on it? Do you have the infrastructure to scale customer delivery? Does the upside case actually produce a constraint that isn't visible in the base case — a capacity bottleneck, a cash need to fund accelerated growth, a hiring market that becomes more expensive as you compete for talent?
The upside scenario is where you identify the success bottlenecks before they become the thing that slows you down during your best quarter.
A fourth scenario worth considering: the strategic pivot
Beyond the three standard scenarios, fast-moving businesses often benefit from modelling a specific strategic alternative — not a macro risk, but a deliberate choice about doing something differently.
Examples:
- "What happens if we launch in Germany instead of focusing on the UK market for the next 18 months?"
- "What happens if we move upmarket — doubling ACV and halving new logo volume?"
- "What happens if we raise a bridge round of €800K rather than extending our current runway through cost cuts?"
Each of these is a scenario with specific financial implications that should be modelled before the decision is made, not after. The financial model is the tool for making the tradeoffs visible.
How to structure scenarios in your financial model
Scenario analysis requires a financial model built with a clear assumption architecture. Here is the structure that works:
A dedicated scenario toggle. A single cell in the model that determines which scenario is active (1 = Base, 2 = Downside, 3 = Upside). All assumption cells that vary between scenarios use an INDEX or IF formula referencing the toggle.
A scenario assumptions table. A table with one column per scenario and one row per assumption that varies. Revenue growth rate, key hire timing, customer churn rate, CAC per channel — each assumption has its base, downside, and upside value in this table. The body of the model never has scenario-specific numbers directly in it; it always references the table.
A scenario output summary. A separate section that shows key outputs (revenue, EBITDA, cash, runway) under each scenario simultaneously, regardless of which scenario is toggled active. This allows side-by-side comparison without switching the model back and forth.
This structure means switching between scenarios takes a single cell change. Running the model under all three scenarios takes three seconds. The decision whether to model a fourth scenario takes a few minutes of adding a column.
Using scenario output in practice: four decisions scenarios improve
1. Fundraising timing. The question of when to start a fundraising process should be informed by scenario analysis: under the downside scenario, when does runway drop below the safety threshold that requires action? Working backwards from that date gives you the latest possible moment to start the process. Working backwards from your preferred outcome (raising from a position of strength with 12 months of runway) gives you the target start date.
2. Hiring decisions. A hire that is clearly affordable in the base case but would leave runway dangerously short in the downside case is a hire that requires a more explicit risk conversation before it's approved. The scenario analysis makes that risk visible and quantifies it.
3. Strategic investment decisions. A new market entry, a product expansion, a major marketing campaign — each of these represents a capital allocation decision that should be evaluated in the context of all three scenarios, not just the base case.
4. Board communication. Presenting base, downside, and upside scenarios to the board — rather than just the base case — demonstrates a maturity of financial thinking that institutional investors respect. It also creates the right kind of board conversation: not "are we on track?" but "under what conditions would we need to change course, and do we agree on what that course change would be?"
FAQs
How often should scenarios be updated? The scenario structure should be updated whenever a fundamental assumption changes — a major customer churns, a strategic decision is made, a fundraise closes. The numbers within each scenario should be refreshed as part of the quarterly planning cycle. Full scenario rebuilds are typically done annually as part of the budget process.
Should I share all three scenarios with investors? In board reporting, yes — presenting all three scenarios is good practice and builds credibility. In a fundraising pitch, the convention is to present a base case and show sensitivity to key assumptions, rather than formally presenting a downside scenario that might be read as low conviction in your own plan.
What's the difference between scenario planning and sensitivity analysis? Sensitivity analysis changes one variable at a time and measures the impact on a specific output — it shows how sensitive revenue is to a 10% change in churn rate, for example. Scenario planning changes multiple variables simultaneously to represent a coherent alternative future. Both are useful; scenario planning provides more realistic and actionable output because real-world outcomes are driven by multiple factors changing together, not one at a time.
BB Financial Services Kft builds scenario-ready financial models for startups and SMBs. Get in touch if your current model only tells you what happens when everything goes to plan.