Every consequential business decision arrives at the same moment: the commitment has to be made before the outcome can be known. Open the second location or hold. Take the large contract at an aggressive price or pass. Buy the competitor, make the senior hire, sign the lease. What separates companies at that moment is not foresight — no one has it — but whether the decision is made on instinct alone or against a model that has already worked through the futures instinct tends to skip.
Scenario planning is that model, and the phrase deserves demystifying, because it sounds like an exercise run by planning departments at much larger companies. In practice it is a disciplined version of the question every owner already asks: what happens if? The undisciplined version stops at revenue. The modeled version follows the decision through the P&L, the balance sheet, and — where decisions most often fail — the cash.
The method, honestly described
The starting point is a driver-based model of the business — the same construction that underpins a rolling forecast — in which results are expressed through their real levers: customers, volumes, rates, and headcount, rather than static line items. A decision is then simply a change to the drivers: the new location adds a rent line, a staffing ramp, and a revenue curve; the large contract adds volume at a price and, critically, the working capital to carry it. This is why driver-based models matter: a line-item budget cannot absorb a hypothetical, but a driver model was built for them.
Then comes the discipline: the change is run through at least three futures, not one. The base case is your honest expectation — not the version used to sell the idea internally. The downside case assumes the location ramps at half the planned speed, the contract’s payment terms stretch to 75 days, the key assumption comes in a third below plan. And the upside case exists for a more serious reason than its name suggests: success carries costs of its own, and a contract that doubles volume can strain a company through the inventory and receivables required to serve it. Growth consumes cash, and the upside case is where you learn how much this particular growth will consume — while there is still time to arrange for it.
For each future, the model answers the questions that matter, in order of consequence. What does cash look like, month by month — not at year-end, because a decision that is profitable in December and insolvent in July is insolvent. What happens to covenants, where there is debt. And how long does the decision take to pay back under each future — because “eventually” is not an answer a lender or a payroll will accept.
The downside case is not pessimism, and the upside case is not optimism. They are the price of making the decision with your eyes open.
What the exercise actually buys you
The first payoff is the obvious one: some decisions fail the modeling and do not get made — the location whose downside case could not be survived, the contract whose upside case required a working capital facility no one had arranged. That outcome alone can repay the exercise many times over.
But the more common payoff is subtler: decisions get made anyway, restructured. The scenario work reveals not just whether to act but how — the location gets opened with a smaller footprint and a staged staffing plan because the downside case demanded it; the contract gets taken with revised payment terms and a pre-arranged line of credit because the upside case exposed the cash gap; the acquisition proceeds with an earnout instead of cash because three futures disagreed about the target’s earnings. The model doesn’t say no. It negotiates.
And the third payoff arrives later: trigger points. Because you modeled the downside before committing, you know in advance what early-underperformance looks like — the leading indicators, the month-four numbers that distinguish a slow ramp from a failing one — and you’ve pre-decided what happens if they appear. Companies without this improvise their retreats, expensively and late. Companies with it treat the downside case as a rehearsed contingency rather than a shock. This, more than prediction, is the point of the whole exercise: scenario planning doesn’t tell you the future. It makes every version of the future one you’ve already walked through once.
The practical bar is lower than owners expect. One competent model, three honest futures, cash followed month by month — a few days of work for a decision that moves six or seven figures. This is the standard analysis inside any established FP&A function, and installing the capability — often in an early quarter of a fractional CFO engagement, once the forecast exists — means every subsequent major decision receives the same treatment as a matter of routine rather than as a special project assembled under deadline.
Chief Perspective builds decision models and scenario analysis as part of its FP&A and Fractional CFO work with middle-market companies. If a big decision is on your table, let’s talk before you commit.
Common questions
How different should the downside case be from the base case?
Uncomfortable but plausible — the disappointment a candid industry peer would call unremarkable. A downside case everyone privately dismisses is decoration; the test is whether you’d genuinely change behavior if it materialized.
We ran scenarios once for the bank. Same thing?
Same skeleton, different purpose. Bank scenarios exist to demonstrate resilience; decision scenarios exist to change the decision. The tell is whether anything about the deal, the structure, or the triggers actually moved after the modeling.
What decisions justify the effort?
A useful threshold: anything that commits more than a month of profit, adds fixed costs, touches debt covenants, or can’t be cheaply reversed. Below that, decide and move. Above it, a few days of modeling is inexpensive insurance on one of the largest commitments the business will make.