Base case discipline is the principle of rigorously validating planning assumptions before alternative scenarios are modelled. The opposite is widespread practice: leadership teams spend six weeks on three scenarios for the next year and only a few hours testing the foundational assumptions of those scenarios. Scenario modelling then stops being a planning tool. It becomes a consensus preservation mechanism. A way to avoid disagreement about the base without resolving it.
Why scenario modelling often imitates sophistication
Presenting three scenarios (base case, upside, downside) looks methodical. It signals caution and awareness of complexity. But in many cases it is something else: an attempt to bridge a lack of agreement on basic assumptions through ranges.
The pattern I see regularly: the leadership team cannot agree on a single revenue plan. Instead of resolving the conflict, they produce three variants and call it "comprehensive planning". In the next meeting, all three scenarios are presented. None is decided.
The problem is not scenario modelling itself. The problem is the order: you first need a valid, internally consistent base case. Sensitivity analysis only becomes meaningful once that base case stands. Modelling scenarios without a valid base case is analytical activity without insight.
The Base Case Validation Framework
The framework runs in three phases. Each phase has a concrete outcome: either valid assumptions or identified gaps that need to be closed before the planning process moves on.
Phase 1: Build up from granular units
The first step is the disaggregation of aggregates. Every revenue assumption has to be broken down into its smallest measurable units:
- Unit economics validation: If the revenue assumption is 20 million EUR, show the composition: 200 customers at 100,000 EUR, or 2,000 customers at 10,000 EUR. Aggregated numbers without component analysis are not validated assumptions.
- Pipeline reality check: Map the current pipeline against the revenue assumptions. If Q3 assumes 5 million EUR but the current pipeline shows 2 million, where do the missing 3 million come from? "We will find it" is not a plan.
- Historical consistency: If the company has never grown faster than 25% per year, the 50% growth assumption needs exceptional evidence. The past is not a ceiling, but it requires explanation when you want to break through it.
Phase 2: Validate against market reality
Internal consistency is necessary but not sufficient. Assumptions also need to hold against external realities:
- Market constraint test: If the growth assumption implies a 40% market share gain, which competitors lose that share? How do they react? Organic growth in saturated markets has different dynamics than growth through market expansion.
- Bottom-up vs. top-down reconciliation: If the customer acquisition model produces 15 million EUR but market analysis shows a 25 million EUR potential, is that strategic underperformance or a wrong market size? The difference determines the action.
- External data points: Signed customer contracts, letters of intent, market research, comparable company financials. Assumptions based only on internal expectations are estimates.
Phase 3: Cross-functional defence
An assumption is valid only after it has withstood structured questioning by the respective other function:
- Sales defends revenue assumptions against finance's cost constraints.
- Operations defends capacity assumptions against sales' growth targets.
- Finance ensures that cost assumptions are compatible with the implicit growth requirements.
When functions cannot defend their numbers with data, you do not have a base case. You have aggregated wish lists formatted as a plan.
The most common comment after a real base case validation is not "Our plan was wrong", but "We knew that assumption was weak, but nobody challenged it directly." Base case discipline is not analytical rigour. It is organisational courage to name weaknesses in the plan explicitly, before they escalate in the next quarter.
When scenario modelling is genuinely useful
Scenarios are not the wrong planning tool. They are a tool for the wrong phase, when they come before the base case.
Used properly, scenarios answer specific strategic questions:
- What happens to our cash flow if the main customer churns? (Customer concentration risk)
- How does our runway change if fundraising is delayed by six months? (Timing risk)
- What does a more aggressive growth target cost us in cash compared to the base scenario? (Investment decision)
Scenarios answer defined questions about known risks. They do not replace the base case. They test it.
| Scenario modelling without base case | Base case discipline plus scenarios | |
|---|---|---|
| Starting point | Three variants in parallel | One validated base case |
| Function | Consensus preservation | Risk analysis of defined questions |
| Outcome | No decision | Clear options for action |
| Resources | High effort, low insight | Focused effort, high decision quality |
| Signal to investors | Uncertainty about own assumptions | Disciplined planning understanding |
How to implement base case discipline
Getting started in practice does not require months of methodology debate. Three concrete changes to the planning process are enough:
- 1Assumptions document before numbers: Before a model is built, every material assumption must be written down, with source, historical basis and validation method. No number without a documented assumption.
- 272-hour rule: Every planning assumption must withstand 72 hours of cross-functional questioning before it enters the model. Sales defends revenue. Operations defends capacity. Finance challenges both.
- 3Explicit gap protocol: Where bottom-up and top-down do not converge, the gap is documented explicitly, with a responsible owner and a closing date. No unresolved inconsistency in the approved plan.