Scenario Planning

The standard scenario planning exercise produces three projections: optimistic, base, and pessimistic. The problem: these scenarios are often built with arbitrary assumptions, disconnected from business reality, and never connected to specific decisions.

When scenario planning fails, it fails in predictable ways. Assumptions are not grounded in driver analysis—growth rates are picked rather than derived from pipeline, market size, or capacity. Scenarios are built once and never updated, so they become irrelevant as conditions change. The scenarios are not connected to decisions, so they generate no action.

According to Deloitte's FP&A research, companies with mature scenario planning capabilities are 2.3x more likely to report accurate forecasts. The difference: mature scenario planning is a decision framework, not a projection exercise.

Effective scenario planning requires identifying the specific drivers that create variance between scenarios, quantifying the financial impact of each driver, pre-defining triggers that indicate which scenario is unfolding, and establishing specific actions for each scenario.

The base-bull-bear framework works when each scenario represents a plausible future, not an extreme. The key is defining the drivers that create variance between scenarios.

Base Case: Reflects current operating plans and assumptions. This is your most likely outcome assuming existing trajectory continues. It should be grounded in actual sales pipeline, known cost structures, and specific initiatives planned.

Bull Case: What happens if conditions exceed expectations. This requires identifying which assumptions could be wrong in a favorable direction. Better sales conversion? Faster hiring? Higher pricing power? Market tailwinds?

Bear Case: What happens if conditions underperform. Identify which assumptions are most at risk. Customer concentration? Market share pressure? Execution challenges? Cost structure inflexibility?

Each scenario should include the same financial statements—income statement, cash flow, balance sheet—so leadership can compare outcomes across scenarios.

The drivers that create variance differ by business type and stage. Identifying your key drivers is the most important step in scenario planning.

For established product businesses ($5M-$50M): Revenue drivers include market demand (units sold), pricing power (price per unit), and product mix (margin by category). Expense drivers include raw material costs, labor costs, and capacity utilization.

For service businesses: Revenue drivers include billable headcount, utilization rate, and billing rates. Expense drivers include labor costs (typically 60-80% of expenses), overhead, and technology investments.

For subscription/SaaS businesses: Revenue drivers include new customer acquisition, churn rate, expansion revenue, and pricing. Expense drivers include customer acquisition cost (CAC), hosting costs, and headcount.

For PE-backed or investor-backed businesses: Capital market conditions affect ability to raise and cost of capital. Exit environment affects valuation multiples. Operating leverage (fixed vs. variable cost structure) affects sensitivity to volume changes.

The goal: identify 3-5 drivers that explain 80%+ of variance between your best and worst cases.

For each driver, define the range between bear and bull case. Use historical data, industry benchmarks, and management judgment to set reasonable bounds.

Step 1: Set Base Case Driver Assumptions
Document the specific assumptions underlying your base case. These should come from operational plans, not arbitrary percentages.

Step 2: Define Bull Case Assumptions
Identify which base case assumptions could be optimistic. Typically bull case is 20-40% better than base on key drivers.

Step 3: Define Bear Case Assumptions
Identify which base case assumptions are at risk. Typically bear case is 20-40% worse than base on key drivers.

Step 4: Calculate Financial Impact
For each scenario, run the full financial model with driver assumptions. The output should be complete income statement, cash flow projection, and runway calculation.

Step 5: Validate Plausibility
Is it plausible that conditions could produce the bull case? Is it plausible that conditions could produce the bear case? If extreme assumptions are required, adjust.

The output should include runway under each scenario—this is typically what boards and investors want to understand.

Scenario planning only creates value if it informs decisions. This requires pre-defining triggers—what signals indicate which scenario is unfolding—and actions—what you will do in each case.

Trigger Definition: What leading indicators signal which scenario is materializing? For a service business: utilization rate below 60% for two consecutive quarters signals bear case. For a product business: inventory building faster than plan signals demand weakness. For any business: a key customer cancellation or delayed expansion signals underperformance.

Action Pre-Definition: What specific actions would you take if each scenario materializes? In bear case: which hires are deferred? Which expenses are cut? Is the marketing budget reduced? In bull case: which investments accelerate? Is headcount expanded? Are new markets entered?

The Value of Pre-Definition: When you pre-define responses, you remove emotion from difficult decisions. The board or leadership has already agreed—if X happens, we do Y. This enables fast action when conditions change.

Without pre-defined triggers and actions, scenario planning becomes a reporting exercise rather than a management tool.

Scenario presentations require different emphasis than internal planning. The goal is demonstrating preparedness and enabling informed decision-making.

For Board Presentations: Lead with runway implications. Boards want to understand how long the company lasts under each scenario. Present scenario parameters clearly—what assumptions drive each case. Focus on pre-defined triggers and actions. Show the company is prepared, not just projecting. Reserve time for strategic discussion rather than detailed line-item review.

For Leadership Team: Emphasize operational implications. What does each scenario mean for specific functions? Sales teams need to understand pipeline requirements. Operations needs capacity implications. Connect to specific decisions already made or pending.

Common Mistakes in Scenario Presentations: Presenting scenarios as forecasts rather than planning tools—confuses the audience. Too much detail on assumptions—loses the audience in the weeds. Not connecting to specific decisions—makes scenarios feel academic. Updating scenarios but not communicating—creates credibility gaps when old scenarios surface.

Best Practice: Present scenarios quarterly with formal updates when material changes occur. Include scenario status: which scenario are you currently tracking toward?

Beyond three-scenario planning, sensitivity analysis helps prioritize attention by understanding which drivers matter most.

How to Conduct Sensitivity Analysis: Start with your base case. For each key driver, change the assumption by 10% while holding others constant. Record the impact on key outputs (revenue, EBITDA, runway). The driver that creates the biggest output change is where management attention should focus.

Example: Revenue model shows MRR growth rate impact of +4 months runway per 10% improvement. CAC impact of -2 months runway per 10% increase. Churn impact of -1 month per 10% increase.

Interpretation: MRR growth is the highest-impact driver. Management should prioritize revenue growth initiatives over cost reduction when the difference between 10% improvement in each area is equivalent.

Sensitivity analysis is particularly valuable when resources are constrained—helping prioritize where to focus organizational energy.