← Back to articles

How to Build Three Scenarios That Prove You Have Actually Thought About What Could Go Wrong



Author: Yanni Papoutsi - Fractional VP of Finance and Strategy for early-stage startups - Author, Raise Ready Published: 2025-03-21 - Last updated: 2025-03-21

Reading time: \~9 min

Why Single-Scenario Models Fail

A financial model with one set of numbers makes an implicit claim: "This is what will happen." Every investor in the room knows that is false. Startups operate in conditions of extreme uncertainty. No one knows the exact churn rate, conversion rate, or hiring timeline. A model that pretends to know these things signals either naivety or dishonesty, and neither is a good look in a fundraising meeting.

Across every fundraising process I have worked on, from seed through the the platform exit, the scenario that generated the most investor questions was the conservative case. Not because investors are pessimists, but because the conservative case answers the question they care about most: "What happens when things do not go as planned, and do these founders have a plan for that?"

A founder who presents three scenarios is saying: "I know this could go multiple ways, and I have thought about what I will do in each case." That is what operational readiness looks like, and investors fund it.

The Three Scenarios Defined

Conservative: The Survival Case

This is not a disaster scenario. It is the scenario where things are harder than expected. Growth is slower. Churn is higher. Hiring takes longer. Sales cycles stretch. The question the conservative case answers: can this business survive and hit meaningful milestones without needing an emergency raise?

Specifically: if your conservative case shows you running out of cash before reaching a fundable milestone, your model has a structural problem. Either you need to raise more, spend less, or redefine the milestones.

Base: The Plan Case

This is what you believe will happen given your current trajectory, market conditions, and execution capacity. It should be grounded in real data: historical growth rates, current pipeline, observed churn, known hiring plans. The base case is not optimistic. It is realistic. The distinction matters because investors expect you to hit 70-80% of your base case. If your base case is already aggressive, hitting 70% of it might mean the business is in trouble.

Aggressive: The Upside Case

This is the scenario where things go better than planned. A key partnership accelerates growth. Churn drops faster than expected. A new channel outperforms. The aggressive case should be plausible, not fantastical. If your aggressive case requires capturing 40% of your TAM in 18 months, it is not a scenario; it is a fairy tale.

The aggressive case serves a specific purpose in fundraising: it shows the return potential that justifies the investment. Investors need to see a path to a 10x return in their fund model. The aggressive case is where that path lives.

Revenue growth | 50-60% of base | Current trajectory Churn rate | 1.3-1.5x base | Observed rate CAC | 1.2-1.3x base | Current blended Hiring pace | Delayed 2-3 months | Per plan

Conversion rate | 0.7-0.8x base | Current observed Purpose | Prove survival | Show the plan

How to Build Scenarios That Actually Work

Step 1: Identify your top 5 assumptions by impact

Not all assumptions deserve scenario variation. Focus on the ones that move the output most. For most startups, these are: new customer acquisition rate, churn or retention, average revenue per customer, hiring pace and cost, and one business-specific variable (take rate for marketplaces, expansion revenue for SaaS, utilization rate for services).

Run a quick sensitivity: change each assumption by 20% and see which ones move total revenue or cash most. The top 5 by impact become your scenario variables.

Step 2: Define scenario-specific values for each variable

This is where most founders get lazy. They apply a flat multiplier to revenue instead of varying the underlying drivers. That produces scenarios that look different but are not structurally different. The correct approach: for each of your top 5 assumptions, define a conservative, base, and aggressive value. Monthly lead growth: conservative 4%, base 8%, aggressive 12%. Monthly churn: conservative 6%, base 4%, aggressive 2.5%. ACV: conservative $5,500, base $7,200, aggressive $9,000.

When you vary the inputs, the outputs change in interconnected ways that a flat revenue multiplier would never capture. Lower lead growth means fewer customers, which means less support hiring needed (lower cost), which partially offsets the revenue miss. That interplay is what makes scenario planning useful.

Step 3: Wire the scenario toggle

In your assumptions tab, add three columns next to each assumption: conservative, base, aggressive. Add a single toggle cell at the top (a dropdown or a value of 1, 2, or 3). Use an INDEX or CHOOSE formula so each assumption reads from the correct column based on the toggle. The result: changing one cell switches the entire model between scenarios. Every tab, every calculation, every output updates simultaneously. This is the structure investors want to see because it lets them test assumptions in real time during a meeting.

Step 4: Check each scenario for internal consistency

A common mistake: the conservative revenue scenario still assumes the same hiring plan as the base case. If revenue is 40% lower, you would not hire the same number of salespeople. Adjust headcount and variable costs in each scenario to reflect the operational decisions you would actually make.

Conservative scenarios should include cost cuts or deferrals that a founder would realistically implement if growth stalled. Aggressive scenarios should include the additional investment (marketing, hiring) needed to capture the upside.

Step 5: Identify the decision points

For each scenario, mark the month where a key decision must be made. In the conservative case, which month do you need to start cutting costs? In the aggressive case, which month do you need to accelerate hiring? These decision triggers are more valuable than the financial projections themselves because they turn scenarios into an operating playbook.

*Key insight: The real value of scenario planning is not predicting the future. It is pre-deciding your responses. When an investor asks "what will you do if churn spikes to 7%?", you do not need to think on the spot. You pull up the conservative scenario and walk them through the cost adjustments, hiring deferrals, and revised milestones you have already mapped out.*

What Each Scenario Must Show

Conservative | Runway to a meaningful milestone without emergency raise

Conservative | Which costs get cut first and when Conservative | Revised break-even timeline Base | Clear path to the next funding milestone

Base | Capital efficiency (revenue per dollar raised)

Base | Unit economics improvement trajectory

Aggressive | Return potential for investors (10x path)

Aggressive | What incremental investment captures the upside

Aggressive | Market share implied (is it realistic?)

The Conversation Scenarios Enable

During the the platform fundraising processes, scenarios transformed investor meetings from interrogations into collaborations. Instead of the investor poking holes and the founder defending, the conversation became: "Let us look at what happens if your UK take rate drops 2 points. The model shows that in the conservative case, and here is how it flows through to EBITDA and runway."

That kind of conversation only happens when the model has working scenarios. Without them, the founder says "I will have to get back to you on that," which is the fundraising equivalent of "I have not done the work."

Profounders specifically asked us to run a custom scenario during one meeting: "What if you win the enterprise contract pipeline but it takes 6 months longer than planned?" Because the model was built with scenario infrastructure, we could adjust the sales cycle assumption on the assumptions tab, toggle a modified case, and show them the answer in under two minutes. That moment built more trust than any slide in the deck.

Common Scenario-Building Mistakes

Flat revenue scaling. Conservative = base revenue x 0.7. This tells the investor nothing about what drives the miss or how you would respond. Change the underlying drivers, not the output.

Same cost structure across scenarios. If revenue drops 30%, you would not maintain the same hiring plan. Adjust costs to reflect realistic operational responses.

Aggressive case that implies impossible market share. If your aggressive case requires 20% market share in Year 2 and you are a seed-stage company, it undermines rather than supports the story. No decision triggers. Scenarios without action points are just three sets of numbers. Add decision markers: "In the conservative case, we defer the third engineering hire and reduce marketing spend by 30% starting Month 6."

Too many scenarios. Three is standard. Five is acceptable for specific investor requests. Seven or more suggests you do not know which ones matter.

Summary

Three-scenario planning is not a checkbox exercise. It is the structure that turns a financial model from a static forecast into a decision-making tool. Build scenarios by varying the underlying drivers, not just the revenue line. Ensure cost structures adjust realistically in each case. Mark decision triggers so each scenario becomes an operating playbook. Wire a toggle in the assumptions tab so the entire model switches with one click. The conservative case proves you can survive adversity. The base case shows your plan. The aggressive case shows the return. Together, they tell investors something more valuable than any single projection: that you have thought about what could go wrong and already know what you will do about it.