The Three Scenarios Every Board Expects (And How to Build Them Without Losing a Weekend)

You Will Never Be Fully Prepared

You will never be fully prepared for every “what if” question the board throws at you. But you can limit them.

Every board meeting has a moment where someone leans forward and says: “What if the enterprise deal slips?” or “What happens if we lose two more reps?” or “What’s the plan if churn ticks up another point?”

These aren’t gotcha questions. Board members ask them because they need to understand the range of outcomes, not just the plan. They’re testing whether you’ve thought about what could go wrong and what you’d do about it.

The problem is that most CEOs present a single forecast. One number. One plan. One future. And then they spend 40 minutes playing defense against hypotheticals they could have preempted.

CEOs who show up with scenarios talk strategy. Everyone else spends the meeting playing defense.

The Three Scenarios

Call them whatever — Bear / Base / Bull, Downside / Base / Upside. Doesn’t matter. Pick names and stick with them.

Same model, different assumptions on the three to five variables that actually matter.

This isn’t three times the work. It’s the same model with different inputs on the variables that matter most. If you build it right, updating scenarios takes two hours, not a weekend.

Bear (Downside)

The Bear scenario is not a doomsday forecast. It’s a realistic downside. What happens if two or three things don’t break your way?

What it includes:

• Revenue misses plan by 20-30%. Not 80%. Not “everything falls apart.” A plausible miss based on deals slipping, conversion rates dropping, or a key market shift.
• A key hire doesn’t close. That VP of Sales you’ve been courting for two months takes another offer. What’s the impact on pipeline? On the hiring plan below them?
• Churn increases by a point or two. Not catastrophic. Noticeable. Enough to change the shape of the year.
• What changes in response. This is the critical part. Don’t just show the bad numbers — show the adjustment. Burn rate goes down by cutting discretionary spend. Two initiatives get deprioritized. Runway extends by X months because you pull these specific levers.

The Bear scenario proves you’ve thought about failure without expecting it. Board members need to see that you have a plan for the downside. They need to trust you won’t be caught flat-footed.

A common mistake: making Bear too mild. If your downside is 5% below plan, that’s not a scenario — that’s a rounding error. Make it realistic enough to be useful.

Base Case

The base case is your operating plan. The forecast you’re actually running the company against. This should be the most detailed of the three scenarios because it’s the one the board will hold you accountable to.

What makes a strong base case:

• Explicit assumptions. Every number should trace back to a stated assumption. “Assumes 2 new enterprise deals close in Q3.” “Assumes we hire 3 engineers by end of Q2.” “Assumes monthly churn stays at 4.5%.” When assumptions are visible, the board can evaluate the plan’s realism without interrogating you.
• Monthly or quarterly granularity. Annual numbers hide too much. Show the board when revenue ramps, when costs hit, when cash gets tight. The shape of the curve matters as much as the total.
• Leading indicators alongside lagging ones. Revenue is a lagging indicator. Pipeline, conversion rate, new logos in trial — those are the leading indicators that tell the board whether Base is tracking before the revenue shows up.

The base case isn’t optimistic or conservative. It’s your honest best estimate of what you think will happen given what you know today. If it’s too conservative, you’re sandbagging and the board will notice. If it’s too aggressive, you’ll miss it and the board will lose trust. Get it right.

Bull (Upside)

Bull is what happens if a few things break your way. Not everything. A few things.

What it includes:

• Revenue beats plan by 15-25%. A big deal closes early. A new channel outperforms. Conversion rates tick up after a product improvement.
• A strategic partnership materializes. That co-selling agreement you’ve been working on goes live. It opens a new segment or accelerates an existing pipeline.
• What changes in response. Hiring accelerates. You pull forward a roadmap initiative. You raise earlier from a position of strength instead of necessity.

The key constraint on Bull: keep it realistic. A Bull scenario that’s 3x your base case makes you look unserious. If Base is $8M ARR and Bull is $24M, no one on the board will take the scenario exercise seriously. Bull should be ambitious but defensible. The board should nod, not laugh.

Bull also serves a strategic purpose. It forces you to think about what you’d do with outperformance. Most CEOs only plan for the base case. When things go well, they scramble to hire, scramble to scale, scramble to capture the opportunity. Bull gives you a pre-built playbook for success.

How to Build All Three From One Data Set

This is where most CEOs bail out. They think scenarios mean tripling their workload. It doesn’t.

The right approach takes two hours, not a weekend.

Step 1: Start with your base case. This is your operating plan. You already have it. If you don’t, that’s a bigger problem than scenarios.

Step 2: Identify the 3-5 assumptions that drive the biggest variance. Not every assumption matters equally. In most startups, the high-impact variables are:

• New customer acquisition rate
• Average deal size
• Churn rate
• Key hire timing
• One or two product/market-specific variables

These are the dials you turn. Everything else — office costs, existing headcount, infrastructure spend — stays the same across all three scenarios.

Step 3: Flex those assumptions for Bear and Bull. Bear takes the 3-5 key assumptions down 20-30%. Bull takes them up 15-25%. That’s it. You’re not rebuilding the model. You’re changing five cells in a spreadsheet and letting the formulas do the rest.

Step 4: Narrate the deltas. For each scenario, write two to three sentences explaining what’s different and why. “In the Bear case, we assume the enterprise pipeline converts at 15% instead of 25%, reflecting a longer sales cycle if the product launch slips.” The board doesn’t need a novel. They need to understand which assumptions moved and what it means.

The output is one deck with three columns on the key slides. Revenue: Bear / Base / Bull. Cash position at year-end: Bear / Base / Bull. Headcount: Bear / Base / Bull. Same structure, three numbers, clear assumptions driving the differences.

What Actually Changes

The “what if” questions drop by 80%. Not because the board stops thinking critically, but because you’ve already shown them the range. When a board member wonders “what if churn goes up?” they can look at Bear. When they wonder “what if the big deal closes early?” they can look at Bull. You’ve pre-answered the questions by making your assumptions and their consequences visible.

The meeting shifts from interrogation to strategy. Instead of spending 30 minutes defending a single number, you spend that time discussing which scenario is tracking, what the early signals are, and what decisions need to be made now to steer toward Bull or away from Bear.

Your credibility goes up. It signals you’ve done the work. The board sees a CEO who knows where the landmines are.

Where People Screw This Up

Making scenarios too close together. If Bear is -5% and Bull is +5%, you haven’t actually explored the range. The scenarios need enough spread to be meaningfully different. Otherwise you’re presenting one plan with margin of error, not three scenarios.

Updating scenarios inconsistently. If you present scenarios in Q1 and then revert to a single forecast in Q2, the board will notice. Either commit to the framework or don’t start it. Consistency builds trust.

Forgetting the “so what.” Numbers without narrative are just numbers. Each scenario needs a one-paragraph explanation of what would cause it and what you’d do about it. The board needs to know you have a playbook for each future, not just a spreadsheet.

Over-engineering the model. You don’t need Monte Carlo simulations. You don’t need 47 variables. You need 3-5 assumptions, three versions of each, and a clear link between inputs and outputs. A Google Sheet works. Don’t let the tooling become the obstacle.

The Trade

The board doesn’t want to surprise you. They want to know you’ve thought about what could go wrong — and what could go right. Three scenarios from one model. Two hours of work. That’s it.

Do it once, it gets easier. Do it every quarter, the board stops grilling you. That’s the whole game.