We had no backup plan. That wake-up call taught me that scenario planning is about avoiding disaster when your assumptions are wrong.
Here is what works: build three scenarios, not five or seven: best case, most likely, and worst case. Any more, and nobody pays attention. Our worst case assumed losing our two largest clients simultaneously, the most likely case assumed 12% growth with normal churn, and the best case modeled landing two major accounts we were pursuing. Each scenario included revenue targets,
headcount plans, and cash runway calculations.
The revisit cadence matters. We reviewed scenarios monthly but rebuilt them quarterly; monthly reviews helped us spot warning signs such as rising customer concentration or shrinking margins, while quarterly revisions gave us enough data to determine whether the business was moving toward a different scenario.
The biggest mistake is making the scenarios too similar. If your worst case is only 8% below your base case, you are lying to yourself. My worst case always assumed something would break, whether that meant losing a major client, facing a carrier rate increase, or seeing a critical technology platform acquired. A real downside scenario should make you uncomfortable.
Scenarios should create triggers, not paralysis. If revenue fell below a certain level for two consecutive months, we would execute the cost-reduction plan.