Scenario Analysis
Scenario analysis evaluates the financial implications of coherent alternative assumption or event sets against a shared baseline.
A scenario is conditional, not a prediction. The analysis should make each changed assumption visible and compare outcomes without rewriting recorded facts or the approved plan.
Scenario analysis calculates and compares what follows from Alternative A, B, or C. It differs from sensitivity analysis, which usually varies one input systematically, and from a forecast or budget, which serves a different planning purpose.
Start from one baseline and compare coherent cases
Each case carries its own visible assumptions into a comparable financial outcome.
- 01Shared baseline
The same current facts and starting definitions
- 02Scenario A
One coherent set of alternative assumptions
- 03Scenario B
A second internally consistent alternative
- 04Scenario C
A third case with its own stated events and timing
- 05Comparable outcomes
Cash, burn, runway, timing, or another defined result
What is Scenario Analysis?
Scenario analysis is the calculation and comparison of financial outcomes under two or more coherent alternative cases. Each case begins from a shared baseline, changes a stated set of assumptions or events, and carries those changes through the same calculation framework.
A hiring scenario might combine start dates, salaries, taxes, and recruiting cost. A revenue scenario might combine price, volume, conversion, churn, margin, and receipt timing. The assumptions within a case should make sense together rather than becoming an arbitrary collection of favorable or unfavorable inputs.
The output is conditional. It shows what the model produces if the assumptions hold. It does not establish which case is most likely and should not silently replace recorded actuals, the current baseline, a budget, or an approved operating plan.
Scenario analysis versus sensitivity analysis
Sensitivity analysis usually changes one input, or a small grid of inputs, to show how responsive an output is. Scenario analysis combines a coherent set of related assumptions or events to describe an alternative operating case. Both are conditional, but they answer different questions.
Scenario analysis versus forecast and budget
A forecast represents a current expectation under a defined process. A budget represents approved financial intent or control for a period. Scenario analysis compares alternatives around a baseline. The labels, ownership, and update rules should remain distinct.
What makes cases comparable?
Shared starting point
Use the same baseline date, scope, currency, and metric definitions.
Visible deltas
Show which amounts, dates, recurrence patterns, and events change in each case.
Consistent outputs
Compare the same cash, runway, burn, margin, or other defined measures across cases.
Why it matters
A major decision can affect cash, commitments, revenue, staffing, and timing across several periods. Scenario analysis makes those consequences inspectable before the decision is made and shows which assumptions drive the range of outcomes.
The method is most useful when it improves a decision conversation, not when it creates a large library of cases without ownership, review dates, or a clear baseline.
What goes into it
- A shared supported baseline and review date
- Coherent assumption and event sets for each alternative
- Explicit amount, timing, recurrence, and state changes
- Comparable outputs and a documented interpretation boundary
Illustrative three-case comparison
A company compares its current baseline with three cases: hiring now, hiring after a customer receipt, and pausing the hire. Each Scenario uses the same starting cash and current commitments. Only the hire timing and related costs change, so leadership can compare the runway and cash-path effect without rewriting the baseline.
How RunwayCal helps
RunwayCal Scenarios begins from the supported current runway context, applies visible hypothetical adjustments, and recalculates Scenario cash, burn, runway, cash-out timing, and trajectory. Saved Scenarios preserve their assumptions and computed output without rewriting Treasury, receipts, payroll, tools, commitments, budgets, or current runway.
RunwayCal uses deterministic calculations from user-supplied inputs. It does not predict which Scenario will occur.
Common mistakes
- 1Treating a Scenario as a prediction or current forecast.
- 2Changing assumptions without showing the delta from the baseline.
- 3Comparing cases built from different dates, scopes, or metric definitions.
- 4Mixing hypothetical results into recorded actuals or the approved plan.
- 5Creating many cases without linking them to a decision or review point.
Get the Financial Clarity Newsletter
Practical tips on cash flow, runway, and financial decisions for founders, business owners, CFOs, investors, and board members. Free, weekly, no spam.
Compare the consequence. Keep the baseline intact.
Make every changed assumption visible and compare the resulting cash and runway paths without rewriting current data.
Explore Scenarios