Scenario Planning Models
Scenario Planning Models are integrated three-statement financial models (P&L, balance sheet, cash flow) built with switchable assumption sets — typically Base, Bull, and Bear — that let leaders quantify how different plausible futures change cash, runway, hiring decisions, and financing needs. The discipline originated at Royal Dutch Shell in the 1970s, where Pierre Wack's scenario team famously modeled an oil shock scenario before 1973, allowing Shell to act faster than competitors when OPEC tripled prices. In a startup context, scenario models translate qualitative uncertainty (will the new product launch succeed? will enterprise sales close?) into quantified financial paths, each with a probability and a decision trigger. The output isn't a forecast — it's a decision framework.
The Trap
The dominant trap is asymmetric scenario design: building a Base case, a Bull case 20% above Base, and a 'Bear' case that's only 10% below Base. KnowMBA POV: scenario planning that doesn't include downside cases is just optimism with a spreadsheet. A real Bear case should be 30-50% below Base — modeling outcomes like 'top 3 reps quit and pipeline empties,' 'fundraising market freezes for 12 months,' or 'top customer churns and concentration risk surfaces.' A second trap is building scenarios but never DEFINING the trigger that switches behavior — without 'if cash falls below $X by month Y, we lay off Z%' decision rules, the model is theater.
What to Do
Build a single integrated model where assumption inputs (growth rate, churn, hiring pace, ARPU) live on one tab and switch between Base/Bull/Bear via a dropdown. For each scenario, output: (1) Monthly cash position over 24 months, (2) Runway, (3) Funding need by date, (4) Hiring plan, (5) Key SaaS metrics (CAC payback, magic number). Define DECISION TRIGGERS: explicit thresholds at which leadership commits to an action ('if pipeline coverage falls below 3x for 2 consecutive months, freeze hiring'). Review scenarios quarterly with the board, and use the Bear case as the OPERATIONAL plan — manage to it, not the Base.
Formula
In Practice
Microsoft's CFO function under Amy Hood is famous for running rigorous scenario models on every major decision. When evaluating the $26.2B LinkedIn acquisition in 2016, Microsoft modeled three integration scenarios with explicit revenue synergies, cost synergies, and customer churn assumptions — and explicitly modeled a 'no synergies' Bear case to test if the acquisition still made sense purely on standalone LinkedIn growth. That discipline (publicly discussed in earnings calls and shareholder letters) is why Microsoft's M&A track record post-2014 is dramatically better than the prior decade. Compare that to Yahoo's $1.1B Tumblr acquisition, where leaked emails revealed essentially no scenario modeling — the entire $1.1B was written off within 3 years.
Pro Tips
- 01
KnowMBA POV: the Base case is what you tell your board. The Bear case is what you actually plan against. Companies that operate to the Base and treat the Bear as 'unlikely' are the ones that wake up at 6 months runway with no Plan B.
- 02
Use the 'pre-mortem' technique: before finalizing scenarios, the leadership team imagines it's 18 months from now and the company failed — what happened? Those failure modes become the Bear case assumptions. This catches blind spots that pure number-crunching misses.
- 03
Probability-weight your scenarios but disclose the weights. If you say 'Base: 60%, Bull: 20%, Bear: 20%,' boards understand the math. If you only show three numbers without weights, decision-makers default to the middle one.
Myth vs Reality
Myth
“Scenario planning is for big companies — startups should focus on execution”
Reality
Backwards. Startups have less margin for error and benefit MORE from scenario discipline. The 5-person seed-stage company with a 1-page Base/Bull/Bear model on a single Google Sheet outperforms the 20-person Series A company with no scenario thinking. Scenario planning scales down better than most finance practices.
Myth
“Bear scenarios make the team pessimistic and hurt morale”
Reality
Bear scenarios with PRE-COMMITTED responses make the team confident, not pessimistic. Knowing 'if X happens, we do Y' eliminates the panic that destroys morale during downturns. The 2022-2023 layoff cycle showed which companies had pre-committed plans (orderly cuts) and which didn't (chaotic, multiple rounds).
Try it
Run the numbers.
Pressure-test the concept against your own knowledge — answer the challenge or try the live scenario.
Knowledge Check
Your Base case projects 80% YoY revenue growth. What is the BEST Bear case assumption to stress-test against?
Industry benchmarks
Is your number good?
Calibrate against real-world tiers. Use these ranges as targets — not absolutes.
Bear Case Severity (vs. Base)
Series A-C startups; aggressive stress reflects 2008/2020/2022 actual outcomesAggressive Stress
−50% revenue, +20% churn, no funding 12mo
Moderate Stress
−30% revenue, +10% churn, delayed funding 6mo
Light Stress
−15% revenue, hiring freeze
Insufficient
−5% revenue (just optimism with a spreadsheet)
Source: OpenView Partners SaaS Benchmark Reports, McKinsey scenario planning research
Real-world cases
Companies that lived this.
Verified narratives with the numbers that prove (or break) the concept.
Microsoft (LinkedIn acquisition)
2016
When Microsoft evaluated the $26.2B LinkedIn acquisition, the CFO team built explicit Base, Bull, and Bear integration scenarios. The Bear case modeled 'no synergies, integration friction, and 10% LinkedIn user attrition' — and the deal still cleared the IRR hurdle. Satya Nadella publicly cited this rigor as the reason the board approved at the price. Five years later, LinkedIn revenue had more than tripled (Bull case territory), but the Bear-case-cleared decision framework had de-risked the bet.
Acquisition Price
$26.2B
Bear Case Tested
No synergies + 10% attrition
LinkedIn Revenue 2016
$3B
LinkedIn Revenue 2022
$13.8B
Test the deal against the Bear case, not the Base. If the deal works only in the Bull case, you're not investing — you're betting.
Hypothetical: Series A SaaS that ran only Base cases
2022-2023
Hypothetical: A composite case representative of dozens of Series A SaaS companies in 2022-2023. Company raised $20M Series A in early 2022 with 24 months of runway at Base case (planned 100% YoY growth, 5% gross churn). They built no Bear case. When the SaaS market reset hit Q3 2022, growth dropped to 35%, churn rose to 12%, and Series B fundraising froze. By Q1 2023, they were at 8 months runway with no plan. They executed three rounds of layoffs in 6 months (45% headcount reduction total), each round triggered by missing the next month's plan rather than a pre-committed scenario trigger. Eventually closed a flat-round bridge at distressed terms.
Series A Raised
$20M
Base Case Growth
100% YoY
Actual Growth (2022 H2)
35%
Layoff Rounds
3 rounds, 45% total cut
Three small layoff rounds destroy 3x the morale of one larger pre-planned cut. Bear case scenarios with pre-committed triggers prevent the 'death by a thousand cuts' pattern that hollowed out hundreds of startups in 2022-2023.
Decision scenario
The Bear Case Hiring Decision
You're the CFO of a Series A SaaS company. ARR is $8M growing 90% YoY (Base case). Cash is $14M, burn is $700K/month (20 months runway in Base). The CEO wants to hire 12 engineers and 5 sales reps over the next 6 months — pushing burn to $1.1M/month. Your Bear case (50% growth, hiring freeze pressure) shows runway dropping to 11 months if all hires happen.
ARR
$8M
Base Growth
90% YoY
Bear Growth
50% YoY
Cash
$14M
Base Runway
20 months
Bear Runway (post-hires)
11 months
Decision 1
The CEO argues: 'We need to hire ahead of growth or we'll miss the window. The Bear case is just paranoia — we've never grown below 80% YoY.' The board chair texts: 'Trust your CFO instincts.' What do you propose?
Approve all 17 hires now — the Base case is achievable and hiring ahead is how leaders winReveal
Approve 6 engineers and 2 sales reps now (45% of plan) with the remaining 9 hires gated on a Q2 ARR trigger ($11M ARR exits Q2 = green light, otherwise hold)✓ OptimalReveal
Related concepts
Keep connecting.
The concepts that orbit this one — each one sharpens the others.
Beyond the concept
Turn Scenario Planning Models into a live operating decision.
Use this concept as the framing layer, then move into a diagnostic if it maps directly to a current bottleneck.
Typical response time: 24h · No retainer required
Turn Scenario Planning Models into a live operating decision.
Use Scenario Planning Models as the framing layer, then move into diagnostics or advisory if this maps directly to a current business bottleneck.