How to run a scenario plan
One forecast tells you what you expect. Three scenarios tell you what you would do if you were wrong - before you have to find out live.
Why a single forecast is not enough
A single-point forecast answers one question: what happens if everything goes as planned. It says nothing about what to do if a major customer churns, a fundraise slips, or demand outpaces hiring. Scenario planning replaces one number with a small set of coherent futures, each with a pre-agreed response.
Where teams get it wrong
- Building scenarios once a year and never updating them against actuals.
- Making the downside case only mildly worse than base, so it never triggers a real decision.
- No defined trigger for switching from base to downside planning - it just becomes obvious too late.
- Scenarios live in a separate spreadsheet from actuals, so nobody checks which one is unfolding.
- Only modeling revenue, ignoring how each scenario changes cash, hiring, and spend.
The Scenario Planning Framework
- 1Pick the two or three variables that most affect your outcome - usually growth rate, cost of acquisition, or a customer concentration risk.
- 2Build a base case from current trend and known commitments.
- 3Build an upside case around a specific, plausible catalyst - not just "everything goes better."
- 4Build a downside case around a specific, plausible shock - a customer loss, a hiring freeze, a slower fundraise.
- 5Define the trigger for each scenario - the actual metric that tells you which case is unfolding.
- 6Track actuals against all three monthly, and act on the pre-agreed response when a trigger fires.
How Fintra runs scenarios against your actuals
| Step | What Fintra does |
|---|---|
| Pick variables | Scenario planning starts from your driver-based budget, so the same variables drive every case. |
| Base case | Forecasting builds the base case from ledger trend and known commitments. |
| Upside / downside | Base, upside, and downside cases run side by side, each tied to headcount and cash-flow projection. |
| Define triggers | Budget insights flag when an actual metric crosses a scenario boundary. |
| Track monthly | Budget-vs-actuals compares real results to all three cases at once, not just the base plan. |
| Act on triggers | AI drafts the reforecast implied by the triggered scenario; finance approves the response. |
Expected outcome across scenarios
Expected Value = (Base % x Base Outcome) + (Upside % x Upside Outcome) + (Downside % x Downside Outcome)
Weighting each scenario by its estimated probability gives a single planning number that still reflects the spread of outcomes, rather than pretending the base case is certain.
Your scenario planning checklist
Build these into your next planning cycle
- Name the two or three variables that most affect your outcome.
- Build a base case from trend and committed changes.
- Build a specific, plausible upside case tied to a real catalyst.
- Build a specific, plausible downside case tied to a real shock.
- Define the exact metric and threshold that triggers each scenario.
- Pre-agree the response to each trigger before you need it.
- Review actuals against all three scenarios every month.
Frequently asked questions
What is scenario planning in finance?
It is the practice of building multiple coherent versions of the future - typically a base, upside, and downside case - instead of a single forecast, and defining in advance how the business would respond to each. It turns "what if" into a pre-made decision rather than a scramble when conditions change.
How is scenario planning different from a regular forecast?
A forecast is one projected outcome. Scenario planning is a small set of projected outcomes, each anchored to a specific, named driver of change, with a pre-agreed action tied to each. The value is not in predicting which scenario happens - it is in having already decided what to do when one does.
How often should scenarios be updated?
Monthly tracking against actuals is standard practice, so you can see early which scenario the business is trending toward. The scenarios themselves - the base assumptions and trigger thresholds - are usually rebuilt quarterly or whenever a major driver changes materially, such as a large customer win or loss.
Do small businesses need formal scenario planning?
Any business with meaningful uncertainty in growth, customer concentration, or funding timing benefits from at least a base and downside case. It does not need to be elaborate - three scenarios built from your existing driver-based budget, reviewed monthly, gets most of the value without a dedicated FP&A function.
Stay in the loop
One practical finance briefing a week - new guides, checklists, and benchmarks.
Plan three futures, not one
Fintra tracks your base, upside, and downside cases against real actuals every month. Free to start, no card required.
Talk to us