Scenario modeling, at most consulting firms, is a performance. The deck is 200 slides. The financial model is a 47-tab Excel monstrosity that only one analyst understands. The output is a recommendation that includes the word "optionality" four times and ends with a steering committee.
That's not scenario modeling. That's theater.
Real scenario modeling fits on one page. It uses three scenarios, not seven. It names five drivers, not thirty. It produces one decision rule per scenario — what the company actually does if the world looks like that — and it's done in a week, not a quarter.
This is the version of scenario modeling that founders actually use. The other version is what consulting firms charge for and what nobody opens after the project ends.
What scenario modeling is actually for
Scenario modeling is a tool for one specific job: making the company's strategic choices robust to uncertainty without paralyzing the decision-making process.
It is not a forecast. It is not a prediction. It is not an attempt to be right about the future. Anyone who tells you they're going to model the future of your market with three-decimal precision is selling you false confidence wrapped in spreadsheets.
What scenario modeling does — when it's done right — is force the leadership team to be honest about the range of futures the business could face, the small number of drivers that actually determine which future shows up, and the decisions the company would make differently if it saw one scenario coming versus another.
That clarity does three things. It surfaces the assumptions the team has been making implicitly, so they can be argued about explicitly. It identifies the leading indicators worth watching, so the team knows what to look at and what to ignore. And it pre-commits the team to a decision rule, so when the scenario starts to show up in the real world, the response is fast instead of debated.
The three scenarios — base, upside, downside
Forget seven scenarios. Three is the right number.
Base case. This is what you actually expect the next twelve to thirty-six months to look like, before you start hedging. Not the "should be" case, not the "we'll work hard and hit numbers" case — the case you would bet your own money on if you had to. Most leadership teams understate their base case because they're afraid to anchor on it. State it honestly.
Upside case. This is what happens if the bets the team is making actually compound and the macro environment cooperates. Not a fantasy — a credible upside, with named conditions. "If our enterprise motion lands and the rate environment loosens, we look like this."
Downside case. This is the case that costs the most discipline to write. Most leadership teams write a soft downside — a 15% miss, a slightly slower fundraising market. That's not a downside. That's a base case with a frown. The real downside names the conditions under which the company genuinely struggles — the major customer churn, the funding round that doesn't close, the technology disruption that lands faster than expected, the regulatory change that closes a market — and asks what the company does if any of those actually happen.
Three scenarios is enough to be useful. More than three is performance. The math gets harder, the conversation gets longer, and nobody remembers the difference between scenario four and scenario five.
The five drivers — not thirty
A good scenario model has five drivers. Not thirty. Not even ten.
The drivers are the variables that actually determine which scenario shows up. They're not the same as KPIs. KPIs measure how the business performs. Drivers determine which version of the future the business is operating in.
For most companies, the drivers fall into a small number of categories:
- One or two demand drivers — how the customer base behaves. New logo growth rate. Expansion rate. Churn cohort behavior.
- One or two competitive or market drivers — how the external environment behaves. A specific competitor's product roadmap. A platform shift. A regulatory event. An incumbent's pricing behavior.
- One macro driver — the part of the world your business actually depends on. Rate environment for capital-intensive businesses. Consumer confidence for discretionary spend. Enterprise IT budgets for B2B SaaS. Most companies have one macro driver that matters and four others that don't.
- One internal capacity driver — what the team can actually deliver. The pace of hiring in a specific function. The shipping velocity of the product team. The ramp time of a new GTM motion.
If your driver list is more than five, you're not modeling — you're cataloging. Force the prioritization. Most founders find that two or three drivers do almost all the work, and the other twenty things they were tracking don't actually move the strategic picture.
The one decision rule per scenario
This is the part most scenario models leave out. It's also the only part that determines whether the model has any value.
A scenario without a decision rule is just a possibility. A scenario with a decision rule is a pre-committed response.
For each scenario, the leadership team has to answer one question: what do we actually do differently if this is the world we're in? Not "we'll think about it." Not "we'll re-evaluate." A specific action, named in advance, that the team has agreed to before the situation arrives.
In the base case, the decision rule is usually about the operating cadence — what gets funded, what gets killed, what milestones the team commits to.
In the upside case, the decision rule is almost always about how aggressively to lean in. Specifically: where additional capital goes when it shows up. Most companies handle upside badly because they didn't decide in advance where to deploy it, so they end up either spraying it across too many initiatives or hesitating long enough that the window closes.
In the downside case, the decision rule is the most important one and the hardest to write. It's the answer to "what do we stop doing, and when?" The companies that survive downsides well are the ones that pre-committed to the trigger — "if we don't have a term sheet by date X, we cut burn by Y" — and executed it without re-litigating in the moment. The companies that don't survive are the ones that spent six weeks debating whether the trigger had actually been hit.
A worked example — the one-page artifact
Here's what this looks like as an actual artifact. Imagine a Series B SaaS company doing $14M in ARR, growing 60% year-over-year, with eighteen months of runway.
Drivers being modeled
- New logo acquisition rate (currently 35 net new logos/quarter)
- Net revenue retention (currently 118%)
- Sales cycle length in the enterprise segment (currently 94 days)
- Engineering throughput on the platform expansion (3 of 5 planned modules this year)
- Late-stage funding market temperature (proxy: number of comparable Series C rounds closing per month)
Base case. New logos hold near 35/quarter. NRR stays at 115-120%. Sales cycle holds at 90-100 days. Engineering ships 3 of 5 modules on plan. Funding market stays slow but functional. The company hits $22M ARR in twelve months and raises a Series C at a reasonable multiple in month fifteen. Decision rule: execute the current plan. No major reallocation.
Upside case. Two of the five enterprise targets named in the pipeline close in the next two quarters. NRR ticks above 125% on platform expansion. The funding market warms. The company hits $28M ARR and raises an upsized Series C in month twelve at a meaningful step-up. Decision rule: deploy 60% of incremental capital into the enterprise motion (named GTM hires and customer success buildout), 30% into the international wedge already in market validation, 10% into accelerating two of the platform modules currently scoped for next year.
Downside case. Enterprise pipeline slips by a quarter. A major mid-market segment cohort starts showing elevated churn. The funding market stays cold. The company tracks toward $17M ARR with thinning runway. Decision rule: by end of month nine, if Series C term sheets haven't materialized at acceptable terms, cut quarterly burn by 30% — specific levers are pre-named (named role reductions, named program kills, contract renegotiations), and the founder is authorized to execute without an additional board vote.
That's the entire scenario model. One page. Five drivers. Three scenarios. Three decision rules. The leadership team aligned on it in two working sessions. The board reviewed it in a thirty-minute slot. The company used it to make four real decisions over the next six months without a single off-site.
That's what scenario modeling looks like when it's actually useful.
What to do this week
If you have a strategy that's robust to one future and silent on the others, sit down for sixty minutes and sketch the three scenarios on a single page. Pick the five drivers that actually matter. Write one decision rule per scenario. Don't worry about polish — worry about whether you'd actually execute the rules.
If you would, you have a scenario model. If you wouldn't, you don't.
If you're carrying a strategy that hasn't been stress-tested against more than one future, that's worth twenty minutes. Book a free alignment call and we'll work through it together. You leave with one specific strategic recommendation, regardless of whether we work together.