Scenario planning models a handful of coherent futures, each driven by named assumptions, and pairs each one with the decisions it would trigger. It differs from budgeting because the point is not accuracy, and from sensitivity analysis because whole assumption sets move together.
What scenario planning is
You pick the uncertainties that would genuinely change your decisions, usually two or three, then build a coherent world around each combination of them. Each scenario carries its own set of assumptions, its own P&L and cash outcome, and its own list of decisions you would take if you found yourself in it. The discipline is in the consistency: a downside where revenue halves but hiring continues untouched is not a scenario, it is a typo.
The reason to do it is control. Finance teams cannot control external factors like tariffs or the weather, but they can control the response, by tightening reporting, stress-testing scenarios and keeping the board aligned with what is really happening.[1] That is the whole argument for the exercise, and it is why it belongs to finance rather than to strategy decks. For the macro half of those uncontrollables, the RBA's Statement on Monetary Policy publishes the current read on conditions, the outlook and the risks to it, which is a better starting point than a guess about rates.
How it differs from budgeting and sensitivity analysis
A budget is one number the business commits to. A sensitivity analysis moves one variable at a time and reports the effect. Scenario planning moves whole assumption sets together, because in real life churn, pricing pressure and hiring pace do not move independently.
| What it produces | What it is for | |
|---|---|---|
| Budget | One committed set of numbers for the year | Accountability. It is the number the business is held to, so it is deliberately singular. |
| Forecast | The current best estimate, updated as things change | Accuracy. It answers where we will actually land, and it gets graded against actuals. |
| Sensitivity analysis | One variable moved, effect reported | Understanding which levers matter most. Useful, but it assumes the rest of the world holds still. |
| Scenario plan | Whole assumption sets moved together | Decisions. Each scenario carries the actions it would trigger and the date by which you would need to take them. |
How many scenarios, and what goes in them
Three is usually the right number: a base case you actually believe, a downside severe enough to be uncomfortable, and an upside that would create its own problems. More than that and nobody reads them. Each one needs the same three things: the assumptions that define it, the cash and runway it produces, and the decisions it triggers with the dates by which you would need to make them.
That last part is what most exercises skip, and it is where the value sits. The downside is only useful if it names the trigger, so the conversation in the room becomes what happens if we are still at this number in March rather than an argument about whether March will be bad. In an early-stage company the downside is also the one that has to hold up under scrutiny, because directors carry obligations around solvency that do not soften when the plan is optimistic; the ASIC guidance on officeholder obligations sets out what a director is on the hook for.
Scenario work sits inside the longer plan, so it is worth reading alongside how far out a five year projection can honestly go.
Where scenario planning goes wrong
The most common failure is that every scenario is optimistic. Founders assume they can scale customers far too quickly, do not appreciate ramp rates, and pitch at top quartile metrics straight out of the gate, which means the base case is already the upside and the downside is really just the plan.[2] A revenue line that goes flat for twelve months and then inflects with no assumption driving the inflection is the same failure wearing a different chart.[3]
The second failure is that the scenarios are never revisited. A set of futures built once and filed is worse than none, because the business believes it has done the work. The most effective finance leaders continually refine board papers, question the assumptions and chase the small details others miss.[4] That is a habit rather than a deliverable, and it is one of the clearer differences between a strong finance leader and a competent reporter.
The feedback loop that keeps scenarios honest is tracking forecast accuracy against actuals once each period closes.
Who owns this, and what it means for who you hire
Scenario planning is not a founder job for long. It requires someone who can hold the model, argue with the assumptions and then stand behind the answer in front of a board, and that is a different person from whoever is closing the month. When the work is genuinely being done, it shows up in how candidates describe themselves: I tell finance professionals to name specific skills such as scenario mining, pricing and unit economics rather than generic phrases like strategic leadership.[5] The specific ones are the ones you can interview against. It is also the difference I listen for when I interview finance leaders on The CFO Track.
Timing depends on the business more than the headcount. A simple single-product tech business can often wait until Series B or later for a first CFO, while a deep tech company carrying inventory, stock and R&D tax needs will need one much sooner.[6] The rule of thumb I use is the number of uncertainties that would actually change your decisions. When there are more than two or three, someone needs to own them full time.
Common questions
What is scenario planning?
It is the practice of building a small number of internally consistent versions of the future and deciding in advance what you would do in each. The output is not a better prediction. It is that the argument about what to do has already been had, in a quiet room, before anybody was under pressure, so the decision takes a day rather than a month.
How is scenario planning different from a budget?
A budget is one committed set of numbers the business is held to. Scenario planning is not trying to be held to anything, which is why the two sit alongside each other rather than compete. The sharper contrast is with sensitivity analysis. Moving one variable at a time tells you which lever is biggest, but it quietly assumes the rest of the world holds still while you pull it, and the world does not. Churn, pricing pressure and hiring pace move together or not at all.
How many scenarios should a startup model?
Three, and the binding constraint is attention rather than modelling effort. A fourth scenario costs an afternoon to build and more or less guarantees that nobody reads any of them properly. The harder discipline is making the upside a real scenario rather than a decoration. An upside that would strain hiring, cash and delivery is worth modelling. One that is the base case with bigger numbers on it is not a scenario, it is a mood.
Who should own scenario planning in a startup?
Someone who can hold the model, argue with the assumptions and defend the answer to a board, which is a different person from whoever closes the month. Those two jobs pull in opposite directions. The close rewards getting to one right answer, and scenario work rewards holding several wrong ones in mind at once. Where the same person does both under deadline pressure, the scenarios are the half that gets skipped, and the board finds out in the quarter it mattered.
References
- How I think about the controllables: finance teams cannot control factors like tariffs or rain, but they can control their response by tightening reporting, stress-testing scenarios, and keeping boards aligned with what is really happening.
- Bryn Leggett, founder of HelloCFO, on unrealistic growth assumptions and ramp rates, in Story Recruitment's panel on what investors look for in founder built financial models.
- Michael Batko, co-founder and CEO of Hourglass, on hockey stick revenue with no assumption driving the inflection. From the same Story Recruitment panel on founder built financial models.
- What I argue on this: they continuously refine board papers, critically question assumptions, and pursue the small details others overlook.
- What I tell candidates: name three to five specific key skills, such as scenario mining or pricing and unit economics, rather than generic terms like strategic leadership.
- What changes as a business scales: it depends on the business model. A simple single-product tech business can often wait until Series B or later, while a deep tech company with substantial inventory, stock and R&D tax needs will require a CFO much sooner.