Why single-point forecasts fail
A forecast that says "we will do $15M in revenue next year" is a point estimate. The actual result will almost certainly be different. Maybe $14M, maybe $16M, maybe $12M or $18M. The point estimate gives no sense of the range.
Decisions made on single-point forecasts tend to be brittle. "We hired 10 people because the forecast said $15M" works if revenue comes in at $15M. If it comes in at $12M, the hiring decision looks bad. The decision should have been made knowing the range of possible outcomes.
Scenario planning replaces false precision with honest range. Instead of one forecast, you have three: base case, upside, and downside. The range shows how much the business can absorb and where the fragility lies.
Building scenarios
Base case is what you actually expect. Not the most optimistic, not the most pessimistic - your honest forecast. This is what you would commit to in a board meeting and what you plan operations around.
Upside assumes conditions go meaningfully better than expected. Stronger pipeline conversion, faster new customer growth, better retention, maybe a new large customer. Typically 15-30% above base on revenue, with appropriate expense implications.
Downside assumes conditions go meaningfully worse. Slower conversion, higher churn, delayed deals, market headwinds. Typically 15-30% below base on revenue, with expense implications that reflect how much you would cut in that scenario.
What to do with the scenarios
Test key business decisions across scenarios. If you are considering a major hire, does the decision still make sense in the downside scenario? If not, think about contingent hiring plans or smaller commitments.
Identify the inflection points. At what revenue level does runway become uncomfortable? At what growth rate do you need to raise the next round? These inflection points are where scenario planning has the most value.
Update the scenarios as conditions change. A downside scenario built in January might be the base case by April if the market has shifted. Keeping scenarios current makes them useful; stale scenarios become just historical documents.
Common mistakes
Making scenarios too similar. If the upside and downside are only 5% apart, the exercise is not useful. Real scenarios should show meaningful divergence - 20-40% spread between upside and downside is typical.
Not adjusting expenses in scenarios. Revenue changes but expenses stay the same. This produces implausible scenarios where the company shows huge margins in upside and huge losses in downside. Expenses should flex with revenue based on what you actually would do.
Using scenarios to anchor negotiations instead of decisions. "Here is our downside case, so commit to these metrics" is not the purpose. Scenarios are internal tools for decision quality, not commitment documents. Keep them honest.