Financial Scenario Planning SOP

The financial scenario planning SOP turns one forecast into four possible futures and a written plan for each, in two or three days of spreadsheet work. A single forecast is a guess with decimals. Four cases with triggers tell you what you will do, and when, if sales come in slower or the round slips. Founders who make those calls in advance cut costs months earlier than founders who wait for the bank balance to force them.

What is the financial scenario planning SOP and when should you use it?

Financial scenario planning means building several internally consistent versions of your financial future, each with its own story and numbers, and deciding in advance what you will do in each. It grew out of the scenario work Pierre Wack led at Royal Dutch Shell, where planners wrote coherent stories about the future instead of tweaking one number at a time. For a startup, it answers one question: how long does the money last if things go wrong, and what do we cut first?

Use this SOP:

• When you have less than 24 months of runway and a fundraise ahead.
• Before a large commitment: hires, a lease, inventory, a long marketing contract.
• When demand is uncertain, such as a new market or a long B2B sales cycle.
• Before investor meetings, where "what if sales take twice as long?" is a standard question.

This SOP builds on a checked model. Checking the assumptions themselves is the job of financial model validation, and month-by-month cash timing belongs to cash flow validation.

What do you need before you start?

• A validated base model with monthly revenue, costs and cash for at least 24 months.
• Real data on your drivers: conversion rates, sales cycle length, churn, payment terms.
• Your cost list, split into fixed, variable and cuttable.
• A one-hour slot with your co-founder to agree on triggers and actions.

How do you run it, step by step?

1. Freeze your base case

Copy the validated model and label it "base". The base case is your honest expectation, built from current data, not the plan you showed investors. Every scenario starts from this file, so nobody edits it afterwards.

2. Pick the 5 to 7 drivers that matter

List the inputs that move cash: new customers per month, conversion rate, price, churn, customer acquisition cost, hiring dates, payment terms and the date of your next round. Set a realistic range for each from your own data or from comparable companies.

3. Run a one-at-a-time sensitivity test

Move each driver to the edge of its range while holding the rest at base, and record the change in runway months. Sort the results into a tornado chart: the longest bar is the driver that deserves your attention. This step tells you which numbers to watch every week.

4. Build four named scenarios

Combine drivers into coherent stories. Upside: faster sales. Base: current trend. Downside: the sales cycle doubles and conversion falls. Severe: downside plus a lost large customer and a round that slips six months. Drivers that move together (slow sales and slower hiring) change together in the same scenario.

5. Write a trigger for every scenario

For each case, name the leading indicator that tells you it is happening, the threshold, the action and the owner. "If new monthly recurring revenue stays below €1,500 for two months in a row, we cancel the two planned hires." A trigger without an action is a worry, and an action without a trigger never happens.

6. Rank your cuts and price them

List every cost you could reduce, with the monthly cash saved and the damage it does. Cuts that save the most and hurt growth the least go first. Rerun the severe case with the cuts applied and record the new runway.

7. Compare actuals every month

Once a month, put actual revenue and costs next to the four cases. If actuals sit inside the downside-to-upside band, carry on. If they drift toward the severe case, the triggers fire and you act that week.

Template you can copy

SCENARIO SHEET

Cash today: ______   Monthly costs: ______   Monthly revenue: ______

DRIVERS          | Upside | Base | Downside | Severe | Source of range
New MRR/month    |        |      |          |        |
Churn/month      |        |      |          |        |
Price            |        |      |          |        |
Hiring dates     |        |      |          |        |
Next round date  |        |      |          |        |
RUNWAY (months)  |        |      |          |        |

SENSITIVITY (base case, one driver at a time)
Driver | Range tested | Runway change (months) | Rank

TRIGGERS
Scenario | Leading indicator | Threshold | Action | Owner | Cash saved/month

CUT LIST
Cost | Monthly saving | Damage (low/med/high) | Order

MONTHLY CHECK
Month | Actual revenue | Actual costs | Closest scenario | Trigger fired? Y/N

Worked example: a B2B SaaS with €600,000 in the bank

This illustrative case uses invented numbers. A startup has €600,000 in cash, €8,000 in monthly recurring revenue (MRR) and €55,000 in monthly costs, with two engineers planned from month 4 at €14,000 a month combined.

• Upside (new MRR of €3,000 a month): 18 months of runway.
• Base (€2,000 a month): 13 months.
• Downside (€1,000 a month as sales cycles double): 11 months.
• Severe (downside plus a lost €3,000 customer in month 3): 10 months.

The sensitivity test surprises the founders. A 10% rise in fixed costs takes two months off the base runway, while new MRR at plus or minus 20% moves it by one month and a three-month hiring delay adds one. Fixed costs move runway more than growth does at this stage.

Their trigger: if new MRR stays below €1,500 in months 2 and 3, they cancel both hires and cut €6,000 a month of tools and contractors. With those cuts, the severe case runs 16 months instead of 10, which passes the 12-month bar and gives them time to raise.

What should you measure, and when do you stop?

Stop building when the four cases, the cut list and the triggers fit on one page and both founders have agreed to them. From then on, the monthly check is the whole job.

Which mistakes should you avoid?

• Scenarios that are plus or minus 10% of everything. Real bad years come from one or two drivers breaking hard.
• A hopeful base case. If the base case is your pitch deck forecast, the downside becomes your real base.
• Moving linked drivers separately. Slower sales also slow hiring, commissions and support costs.
• Building it once and filing it away. Scenarios earn their keep in the monthly comparison.
• Too many cases. Four named stories beat twelve variations nobody reads.

How can AI speed this up?

AI assistants are good at three jobs here. They write scenario stories from your drivers, so each case reads as a believable sequence of events. They check spreadsheet formulas for broken references and hard-coded numbers. And for founders who want a probability view, they write a short Monte Carlo simulation in Python or Google Sheets that runs your drivers through thousands of random combinations. The human decisions stay with you: which risks are plausible, which cuts you will really make and who owns each trigger.

Where does this SOP fit in your validation plan?

Scenario planning comes after the model is checked and before you raise or commit to large costs:

1. Check assumptions with financial model validation and find your floor with break-even analysis.
2. Sort fixed and variable costs with cost structure validation, which feeds your cut list.
3. Use the severe case to size the round in fundraising validation and the price in the valuation methodology SOP.

See all 10 Financial Validation SOPs. To build the model and the plan with a cohort and deadlines, the F/MS startup course takes you from idea to a working startup in four weeks, and the business plan generator gives you a structure for the written plan.

FAQ

What is the difference between scenario planning and sensitivity analysis?

Sensitivity analysis moves one input at a time to see how much it matters. Scenario planning combines several inputs into coherent stories and attaches decisions to each. You need both, sensitivity first.

How many financial scenarios should a startup build?

Four: upside, base, downside and severe. Fewer hides the bad cases, and more turns into noise.

How much runway should a startup keep?

Many investors and advisers suggest raising enough for 18 to 24 months, because a round takes several months to close. This SOP's pass bar is 12 months in the severe case after cuts.

When should I update financial scenarios?

Compare actuals monthly and rebuild the scenarios after any large change: a round, a big customer, a new market or a missed trigger.