Scenario Planning Guide for Finance Teams

The most common triggers for scenario analysis include: fundraising (investors want to see multiple outcomes), strategic decisions (should we expand into a new market or double down on the current one?), economic uncertainty (what happens if a recession hits?), and operational disruptions (what if a key customer churns, or a critical supplier increases prices by 30%?).

Reserve scenario planning for decisions where the outcome is genuinely uncertain and the financial impact is material. A £5,000 software purchase does not need three scenarios. A decision to hire 15 engineers over the next two quarters, costing £1.2 million fully loaded, absolutely does. The rule of thumb: if the decision represents more than 5% of your annual operating budget or more than one quarter of cash runway, model the scenarios.

The value of scenario planning drops sharply with time. A scenario that takes three weeks to build arrives too late for most decisions. Your goal should be to produce a credible scenario within 24-48 hours of the triggering event. This requires pre-built model structures and clean data — you cannot build scenarios quickly if your base model is a mess.

Every scenario exercise should start with three cases. The **Base Case** represents your current best estimate — this is your working forecast, not an aspiration. The **Upside Case** models what happens if key assumptions break in your favour: higher win rates, faster growth, lower churn. The **Downside Case** models the reverse: lower revenue, higher costs, slower collections.

Add a fourth or fifth scenario only when the core three do not capture a distinct strategic option. Examples: a "Go Big" scenario that models aggressive hiring and marketing spend to capture market share, versus a "Capital Efficient" scenario that prioritises profitability over growth. Or a "Fundraise in Q2" scenario versus a "Extend Runway to Q4" scenario. Each additional scenario should represent a fundamentally different strategic path, not just a slightly tweaked assumption.

Avoid generic names like "Scenario 1" or "Optimistic". Use descriptive names that make the strategic choice clear: "20% Growth + Break-even", "30% Growth + £2M Raise", "Flat Revenue + Cost Cuts". When your CEO asks "what happens if we delay the fundraise?", you should be able to point to a named scenario immediately.

Your base case should reflect reality, not ambition. Use current run rates, pipeline conversion at historical averages, and approved hiring plans. If your trailing three-month revenue growth is 3% month-on-month, your base case should not assume 8%. The base case is the answer to: "If nothing changes and current trends continue, where do we end up?"

The upside case models favourable but plausible outcomes. A useful framework: take each key driver and set it at the 75th percentile of historical performance. If your win rate has ranged from 15% to 30% over the past 12 months, the upside case might use 25%. Apply the same logic to churn, expansion revenue, and hiring speed. The upside should be achievable, not fantastical.

The downside case should make you slightly uncomfortable but not be catastrophic. Use the 25th percentile of historical performance for key drivers. Model the impact of losing your largest customer, a two-month hiring freeze, or a 15% increase in supplier costs. The purpose is not to terrify the board but to demonstrate that you have a plan: "If downside materialises, here are the levers we pull — reduce discretionary spend by £X, defer these hires, renegotiate these contracts."

A sensitivity analysis varies one assumption at a time while holding all others constant. Build a table with your top five drivers across the columns and three to five values for each. For example: revenue growth at 10%, 15%, 20%, 25%, 30% — and for each, show the impact on EBITDA, cash balance, and runway. This reveals which drivers have the greatest leverage. In most businesses, revenue growth and headcount timing dominate.

Stress tests ask: "What is the worst that could plausibly happen, and do we survive?" For a UK tech company, stress scenarios might include: losing 25% of ARR in a single quarter (a major customer churns), a 50% drop in new business for six months (recession), or a 20% increase in all costs (inflation spike plus weak sterling). For each, calculate the impact on cash runway and identify the minimum cash balance you need to maintain.

One particularly useful analysis: for each key driver, calculate the breakeven point. "At what revenue growth rate do we run out of cash?" or "How many months of zero new sales can we survive?" These numbers should be at your CFO's fingertips. In Grove FP, you can build sensitivity tables that recalculate instantly as you adjust drivers.

Every scenario exercise should produce a single page that any executive can understand in two minutes. Include: the three scenario names, the key assumptions that differ between them (no more than five), and the financial outcomes (revenue, EBITDA, cash balance at year-end, runway). Use a simple table format. Avoid charts for the summary — tables are more precise and faster to read.

Scenarios should lead to decisions, not just analysis. Frame your presentation around the decision: "We are deciding whether to accelerate hiring or maintain the current pace. Here are three scenarios showing the financial impact of each option." End with a clear recommendation: "We recommend the base case (maintain pace) because it preserves 12 months of runway while still achieving 20% growth."

Scenarios are not static. As actuals come in, update your scenarios monthly. Retire scenarios that are no longer relevant. The base case should converge with actuals over time — if it consistently diverges, your forecasting process needs recalibration. Keep a log of assumption changes so you can explain to the board why the forecast shifted: "We reduced the revenue growth assumption from 25% to 20% because Q1 pipeline was 15% below target."