Scenario-Based Financial Modelling

Purpose

Replace single-point ROI projections with scenario-based analysis that clarifies the range of possible outcomes and the assumptions driving each, supporting risk-aware governance decisions.

Single-point projections (“ROI will be 180%”) create false precision—governance cannot assess what could go wrong, which assumptions matter most, or where the break-even boundary lies. Scenario modelling makes uncertainty explicit, enabling governance to approve with eyes open rather than gambling on a single forecast.

When to Use

Use scenario-based financial modelling when:

• Business case requires financial justification for governance approval (A1.5 Step 1)
• Multiple uncertain variables drive financial outcomes (adoption rate, pricing, cost, timeline)
• Governance body expects ROI, NPV, or payback analysis as part of approval criteria
• Organisation's standard investment evaluation requires scenario or sensitivity analysis
• Need to identify minimum viability threshold—the worst-case outcome governance would still accept

Do NOT use when:

• Initiative is purely strategic / exploratory with no near-term revenue expectation (e.g., research partnership, capability building)—use strategic options framing instead
• Financial outcomes are well-known from direct precedent (annual product refresh with stable margins)—simple budget template sufficient
• Initiative is below financial modelling threshold (50K)—2-line cost estimate sufficient

Sample Size and Duration

Participants: 2–3 people

• Essential: Innovation Manager (assumption ownership), finance analyst or domain expert (model validation)
• Recommended: Executive sponsor (reality check on governance expectations)

Duration:

• Simple model (3 drivers, existing template): 4–5 hours
• Standard model (4–5 drivers, new build): 6–8 hours
• Complex model (multi-year, phased, multiple revenue streams): 10–16 hours (split across 2–3 days)

Prerequisites

• A1.2–A1.4 evidence: Market sizing, adoption benchmarks, willingness-to-pay data, cost estimates, feasibility assessment
• Organisational financial parameters: Standard discount rate, hurdle rate, required payback period, budget cycle timing
• Comparable initiative data: Prior business cases for benchmarking cost ranges, timeline accuracy, adoption curves (if available)
• Participants: Innovation Manager (assumption ownership), finance analyst or domain expert (model validation)
• Time: 4–8 hours (see Sample Size and Duration)

Complete Procedure

Step 1: Identify Key Financial Drivers (30–60 minutes)

Review A1.2–A1.4 outputs to identify 3–5 variables that most influence financial outcomes. Apply reverse income statement logic : work backward from required return to identify which assumptions must hold.

Common driver categories:

Selection criteria: Choose drivers where (a) outcomes are genuinely uncertain (not fixed costs already contracted), (b) variation has material impact on ROI (changing the driver by 30% moves NPV meaningfully), and (c) evidence exists to define plausible ranges (A1.2 data, market benchmarks, team estimates).

Step 2: Define Three Scenarios (30–60 minutes)

For each driver, define three values reflecting courtney1997strategy's alternate futures framework:

• Optimistic: favourable but plausible assumptions—supported by best-case evidence or comparable success stories
• Base: most-likely assumptions supported by A1.2 evidence and market benchmarks—this is the planning case
• Conservative: unfavourable but plausible assumptions (slow adoption, competitive price pressure, cost overruns)—not catastrophic but genuinely challenging

Scenario design rules:

• Scenarios must reflect genuinely different assumption sets—not 5% variations
• Conservative case should be uncomfortable but defensible (“What if adoption is half our base estimate?”)
• Optimistic case should be ambitious but credible (“What if we capture the high end of comparable adoption curves?”)
• Each driver value must have a stated source (A1.2 data, benchmark, team estimate)

Step 3: Build Financial Model (2–4 hours)

For each scenario, model:

1. Revenue projection: 3–5 year forecast based on adoption × price × retention drivers
2. Cost projection: development cost (one-time), operating cost (recurring), cost-to-serve (variable)
3. P&L summary: annual revenue, cost, and margin for each scenario
4. ROI: (net benefit / total investment) × 100
5. NPV: discounted cash flows using organisation's standard rate
6. Payback period: months until cumulative cash flow turns positive

Example—Digital Patient Engagement Platform:

Step 4: Conduct Sensitivity Analysis (1–2 hours)

Vary one driver at a time while holding others at base values to identify which assumptions have the greatest impact on NPV:

1. For each driver, model NPV at conservative, base, and optimistic values (other drivers held at base)
2. Rank drivers by NPV range (largest range = highest sensitivity)
3. Present as tornado chart or ranked table
4. Highlight top 2–3 variables: “NPV is most sensitive to adoption rate and revenue per clinic; development cost has moderate impact”

Step 5: Define Minimum Viability Threshold (30 minutes)

Determine the lowest acceptable outcome governance would tolerate:

• What is the minimum ROI / NPV / payback the organisation requires for this investment class?
• Does the conservative scenario meet this threshold?
• If conservative case falls below threshold, document explicitly: “Conservative case is below viability; A2 must validate adoption assumption before A4 full investment”
• If conservative case is significantly negative, consider recommending Conditional Approval with Phase 1 validation gate

Step 6: Document Assumptions (30–60 minutes)

For every key assumption, record source, confidence, and validation plan :

Quality Criteria

Excellent scenario-based financial model demonstrates:

1. Genuine scenario diversity: Scenarios reflect meaningfully different assumption sets—not 5% variations
2. Plausible conservative case: Uncomfortable but defensible—not unrealistically pessimistic or suspiciously comfortable
3. Assumption transparency: Every assumption documented with source, confidence level, and validation plan
4. Sensitivity clarity: Top 2–3 variables that drive outcomes identified and communicated
5. Minimum viability addressed: Clear statement of whether conservative case meets organisational threshold
6. Appropriate precision: Figures rounded to stage-appropriate accuracy; labelled as estimates
7. Validation linkage: Critical assumptions linked to specific A2–A4 learning activities

Theoretical Foundation

Seminal references:

• : Introduced discovery-driven planning—the foundational argument that innovation investment decisions should be based on assumptions to be tested rather than forecasts to be believed. Proposed the reverse income statement: start with required financial outcome, then work backward to identify the assumptions that must hold for that outcome to materialise. This logic underpins the assumption register and validation linkage in this method.
• : Distinguished four levels of uncertainty (clear enough, alternate futures, range of futures, true ambiguity) and prescribed different analytic responses for each level. Innovation business cases typically face Level 2 (alternate futures) or Level 3 (range)—both requiring scenario analysis rather than single-point forecasting.
• : Seminal Harvard Business Review article establishing that effective investment cases communicate through the lens of people, opportunity, context, and risk / reward. Argued that investors (and governance bodies) need to see the deal in terms of scenarios and assumptions, not false-precision spreadsheets.

Contemporary references:

• : Extended discovery-driven planning to business model innovation, showing that scenario modelling should cover not only financial variables (price, volume) but business model assumptions (willingness to pay, channel viability, cost structure). Directly informs driver selection in Step 1.
• : Operationalised assumption-based planning for corporate innovation, providing practical tools for identifying, prioritising, and testing business case assumptions. Influences the assumption documentation and validation linkage in Step 6.
• : Demonstrated across 400+ firms that business cases with 3-scenario analysis achieve significantly higher governance decision quality and project success rates than single-point cases. Provides empirical justification for the three-scenario standard.

Challenges and Solutions

Challenge 1: Single-Point Projections Disguised as Scenarios

Symptoms:

• Three scenarios with 5% variation (“1.5M / 1.6M / 1.7M”)
• Conservative case is still comfortable—no genuine downside explored

Solutions:

• Conservative case must be genuinely uncomfortable: “What if adoption is half our estimate?”
• Rule of thumb: if conservative NPV is still strongly positive, assumptions aren't being stress-tested
• Ask: “What would have to go wrong for this to lose money?” and model that scenario

Challenge 2: Too Many Drivers—Model Complexity Explosion

Symptoms:

• 10+ drivers with 3 scenarios each = hundreds of combinations
• Model becomes opaque; no one understands which assumptions matter

Solutions:

• Limit to 3–5 key drivers (Step 1 selection criteria)
• Use sensitivity analysis (Step 4) to identify which 2–3 drivers dominate—focus communication on those
• Secondary drivers can use single (base) value with noted assumption

Challenge 3: False Precision in Early-Stage Projections

Symptoms:

• Revenue projected to 1,247,832 for an initiative 18 months from market
• Governance treats projections as commitments rather than estimates

Solutions:

• Round figures to appropriate precision (1.2M, not 1,247,832)
• Label projections explicitly: “Planning estimate—accuracy 30% at this stage”
• Use ranges rather than point values where appropriate (“1.0–1.5M”)
• Emphasise that A2–A4 will refine projections with real data

Relationship to Other Methods

Scenario-Based Financial Modelling receives input from:

• A1.2 User Research: Market sizing, adoption evidence, willingness-to-pay data
• A1.4 Feasibility Assessment: Cost estimates, timeline projections, technical risk factors
• Risk and Assumption Mapping (the referenced method): Risk register informs conservative scenario assumptions
• I1 Portfolio Management: Organisational hurdle rates and investment thresholds

Scenario-Based Financial Modelling provides input to:

• Structured Business Case Development (the referenced method): Financial analysis section (Step 3)
• Portfolio Impact Assessment (the referenced method): Investment size and return range inform capacity and balance assessment
• Governance Presentation Design (the referenced method): Scenario summary is key governance slide
• A2 Ideation: Assumption validation priorities shape A2 learning plan

Tools and Templates

• Financial ROI Model—3-scenario spreadsheet (the referenced method)
• Tornado chart template (sensitivity visualisation)
• Assumption register template (integrated into ROI model)
• Comparable initiative database (benchmarking)

• D. J. Bland & A. Osterwalder (2020). Testing Business Ideas. Wiley.
• H. Courtney, J. Kirkland & P. Viguerie (1997). Strategy Under Uncertainty. Harvard Business Review. 75(6). pp. 67–79.
• R. G. Cooper (2017). Winning at New Products: Creating Value Through Innovation. 4 ed. Basic Books.
• R. G. McGrath (2010). Business Models: A Discovery Driven Approach.
• R. G. McGrath & I. C. MacMillan (1995). Discovery-Driven Planning. Harvard Business Review. 73(4). pp. 44–54.
• W. A. Sahlman (1997). How to Write a Great Business Plan. Harvard Business Review. 75(4). pp. 98–108.