How to build a downside scenario your investors will believe

Most founders build one financial scenario, call it the base case, and quietly hope investors do not ask what happens if things go slightly wrong. This is understandable. Entrepreneurs are optimistic by nature - it is basically a job requirement - and modeling a pessimistic case feels like manifesting failure.

The result is that most investor conversations about downside scenarios are painful and ad hoc. An investor asks "what happens if growth is 30% slower?" and the founder either makes something up on the spot or says they will follow up with updated numbers. Neither answer inspires confidence.

A real downside scenario, built in advance and connected to the model, does the opposite. It signals that you have thought carefully about what can go wrong and that the business survives it. That is a genuinely reassuring thing to show an investor.

Why scenarios matter more than founders expect

The purpose of scenario planning is not to predict which future will happen. It is to understand the range of outcomes your business can tolerate, and to make visible the assumptions that create the most risk.

A model without a downside case forces you to answer questions about risk in real time, with no supporting structure. A model with a downside case lets you say: "In our conservative case, where growth is 40% below base and churn runs at 7% instead of 4%, we still have 11 months of runway post-raise. Here is what breaks first." That is a completely different conversation.

Scenarios also help internally. When reality diverges from your base case - and it will - having a pre-built downside scenario means you know immediately which scenario you are in and what the implications are, rather than spending two weeks rebuilding the model to find out.

The three scenarios you actually need

Base case

This is what you genuinely expect to happen, built from your best current estimates of acquisition, conversion, churn, hiring, and costs. It should be realistic rather than aspirational. If you would be pleasantly surprised to hit it, it is not a base case - it is an upside case with a label change.

The base case is also the scenario connected to your startup financial model as the default. Every other scenario is a variation of this one.

Downside case

The downside case is not "everything goes wrong at once." It is a specific, coherent scenario where a few key assumptions are more pessimistic than base. Good downside cases are specific about what changes and why.

Useful downside levers for SaaS:

• Revenue growth 30-50% below base (slower acquisition, longer sales cycles, lower conversion)
• Monthly churn 2-3 percentage points higher than base
• Hiring delayed by one quarter (or specific hires cut)
• CAC 30-40% higher than expected (channels are more expensive than planned)

The combination should be plausible, not catastrophic. "What if we launched six months later than planned?" is a real question. "What if we get zero customers ever?" is not a useful scenario.

What the downside case should answer: how long does runway last, what milestones slip, and what decision would we make if this scenario materialized? If the downside case shows 5 months of runway instead of 14, the answer to that last question is probably "cut X and start a bridge round." Knowing that in advance is valuable.

Upside case

The upside case shows the potential if key assumptions are more favorable than expected - higher conversion rates, lower churn, a channel that scales better than modeled. This is useful mainly for showing investors the range of outcomes and demonstrating that the business has real upside, not just a base case that barely works.

One practical note: founders tend to make upside cases too extreme, which makes them feel disconnected from reality and therefore useless. An upside case where growth is 25% above base is more credible than one where it is 300% above base.

The 10 common modeling mistakes that make scenarios unreliable

Scenarios are only useful if the underlying model is reliable. The most common issues that undermine this:

1. Revenue projections disconnected from the acquisition assumptions that drive them
2. Costs that do not scale with revenue (headcount that magically stays flat as revenue triples)
3. Churn assumptions that are not grounded in any data or comparable
4. A funding need that appears in the model but is not clearly explained
5. No personnel forecast, or one that significantly underestimates headcount
6. Operational expenses left out or misaligned with strategy
7. Gross margin not modeled explicitly (see gross margin for SaaS founders)
8. Cash timing not modeled separately from P&L (the reason cash flow vs profit always matters)
9. No scenario where a key assumption is stress-tested
10. A model too complex for anyone to maintain or update

Scenarios built on a model with these problems are just wrong numbers in a different column.

How to stress-test your downside case

Once you have a downside scenario, ask yourself: does this pass the smell test? Specifically:

Is the downside coherent? Each assumption change should follow logically. Higher churn usually comes with slower new customer growth (both signal product-market fit issues). Lower conversion usually means higher CAC. Make sure the scenario tells a consistent story.

Does the downside still survive? If your downside scenario shows the company running out of cash in month 6 post-raise, you have either miscalibrated the scenario or discovered that you need a larger raise. Either way, better to know now.

Can you explain what you would do? For every scenario, you should be able to say: if this happens, here is the first decision we make. That is the point of building the scenario in advance.

Do the key metrics reconcile? ARR, MRR, churn, burn, and runway should all be consistent with each other in every scenario. If they do not reconcile, the model has structural issues that need fixing before the scenarios are meaningful. This is exactly the kind of consistency that investor-ready financials requires.

The scenario conversation with investors

When you present scenarios to investors, the goal is not to convince them that the downside will not happen. It is to show that you have thought carefully about what does happen if it does. The most reassuring sentence in a pitch is often: "Even in our conservative case, we have 11 months of runway after this raise and hit the milestones we need for the next round."

That sentence requires a downside model to be credible. Without it, you are just asserting it.

Founder checklist

• You have a base case, downside case, and upside case, all built on the same model
• Your downside case changes specific, plausible assumptions rather than all assumptions at once
• Each scenario shows runway, key milestones, and the first decision you would make
• All three scenarios are maintainable - changing one assumption updates the rest
• You can run the downside scenario for an investor in real time without rebuilding the model

How Binokl helps