Best-Case, Base-Case, Downside: Revenue Plan

Most companies make one forecast. As a fractional CFO, I’d rather run three. That gives me one plan to operate the business, one plan for upside, and one plan for protection if revenue slips.

Here’s the short version:

• Base case = my main plan for budget, hiring, and cash runway
• Best case = what I do if growth beats plan and the numbers hold
• Downside = what I cut or delay if revenue drops 15% to 35% below plan
• I tie each case to clear triggers, like pipeline coverage, churn, bookings, and runway
• I link every revenue path to headcount, spend, margin, and months of cash left

A simple way to think about it:

A three-scenario plan works best when I review it every month, reset assumptions each quarter, and switch plans based on data instead of hope.

Intro to Scenario Analysis for Financial Professionals

sbb-itb-e766981

1. Best-Case Revenue Plan

For a U.S. growth-stage SaaS company, the best case usually means 25%–40% revenue growth over the plan period. It also assumes annual price increases of 5%–10%, gross dollar retention above 95%, net revenue retention of 120%–140%, and win rates reaching about 28%. Those numbers shouldn't sit in a spreadsheet by themselves. Each one needs to connect to a clear operating move.

Assumption Ranges

Set up a three-column table for each driver: downside, base, and best. That makes the plan easy to scan and even easier to pressure-test.

If monthly new customer adds average 50, you might set:

• downside at 40
• base at 60
• best at 80

Average selling price could range from $9,000 in the downside case to $11,000 in the base case to $13,000 in the best case, based on packaging changes and negotiated discounts. Conversion from qualified opportunity to closed-won could move from 18% to 22% to 28%.

Here’s the key part: every assumption should tie back to a source. That could be past performance, pipeline coverage ratios, or market benchmarks. Leadership needs to see what has to go right for the best case to happen. And each assumption should point to a decision on hiring, pricing, or spend.

Operational Triggers

The best-case plan only works when the business starts showing the right signals. Common triggers include a qualified pipeline staying at 4–5x quota for three or more consecutive months, new account executives reaching full quota in 3–4 months instead of the usual 6, and product milestones landing on time so the company can support higher price points or move into new customer segments.

Teams usually watch these signals through weekly or monthly dashboards, sales forecasts, and product roadmaps. If two or more of these triggers hold for two straight quarters, leadership has a solid reason to shift capital allocation toward the best-case plan instead of getting ahead of the numbers. If the triggers don't hold, the base case remains the operating plan. ^[7][5]

Expense and Hiring Choices

When those triggers hold, hiring and spend should increase in phases, not all at once. Start with sales and marketing after the early signals show up. Then add product and support after two quarters of outperformance against base-case metrics and after hitting the stated margin thresholds. Infrastructure comes after that.

Even in an optimistic plan, timing matters. You still need to account for normal time-to-fill and onboarding windows. Marketing dollars should move toward the channels with the best ROI, such as events or referrals. It also helps to track labor cost as a share of revenue so margin pressure shows up early, not after the budget is already stretched. ^[6]

Runway and Margin Impact

A company with 24 months of runway in its base case could see that extend to 30–36 months in the best case if revenue growth comes in 10–15 percentage points higher and gross margins stay in place. Operating margin could move from -20% in the base case toward -5% or break-even. Burn as a share of revenue also drops, which leads to a better burn multiple for investors.

If those thresholds don't hold, keep the base case as the operating plan. ^[8][4]

2. Base-Case Revenue Plan

The base case is the operating plan. It’s the forecast leadership uses for budgets, hiring, and day-to-day planning. This version should reflect normal execution, not lucky breaks. While the best case leans on upside triggers, the base case stays grounded in what the business is doing now.

Assumption Ranges

Start with trailing three-month averages for new customer acquisition and churn. Then make changes only when the history backs them up. The table below ties each driver to current performance.^[12]

Every assumption needs a source. That source can be internal history, cohort data, or benchmarks.^[13]

Once those inputs are locked in, the next step is simple: decide which signals show whether the plan is on track.

Operational Triggers

Leadership should watch leading indicators like MRR growth, pipeline coverage, bookings, renewals, sales productivity, and gross margin. These are the early warning lights. If pipeline coverage falls below the target multiple for two straight months, or if sales cycles move past the modeled range, the business is drifting away from the base case.^[11][1]

When that happens, leadership needs to react. That can mean:

• Holding spend
• Pausing a hire
• Tightening the plan

Expense and Hiring Choices

Fund the teams that keep the engine moving: sales, customer success, core marketing, and product enablement. Push lower-priority spending to later. Add headcount in tranches tied to revenue milestones.

That approach matters. A staged plan gives the company room to move if revenue lands near the low end of the expected range. Big fixed costs can box you in. Variable spending gives you more breathing room.

Runway and Margin Impact

The model should show runway and the minimum cash buffer needed to absorb normal variance. Many venture-backed companies aim for at least 18 months of runway in the base case.^[10]

On margins, define the gross margin path and, when it applies, the EBITDA or operating margin path under normal execution. Be clear about where the gains come from: pricing, mix, scale, or lower acquisition costs. Not best-case bookings.

That runway and margin picture shapes how much hiring and fixed spend the business can carry. If those targets start to slip, the downside case should take over before cash pressure starts building.

Those same drivers also frame the downside case, where the priority shifts from growth to runway protection.

3. Downside Revenue Plan

The downside plan is your realistic, data-backed case for a period when several core drivers miss at the same time. Its role is simple: show runway, show how far milestones may slip, and show what the company will do next. To make that plan useful in the moment, you need clear assumptions, hard triggers, and pre-set actions.

Assumption Ranges

Start with your base-case drivers, then pressure-test only the ones most exposed to demand swings, pricing pressure, or churn. For a typical U.S. growth-stage company, downside assumptions often look like this:^[9][20][21]

These numbers shouldn't come out of thin air. Tie each one to something you can point to: your own past misses, industry data, peer results, or prior downturn periods such as 2020.^[9][19]

Operational Triggers

A downside plan only works if leadership knows exactly when to switch to it. That means setting firm, numeric thresholds ahead of time instead of relying on gut calls when stress is high.

Common triggers include:

• A revenue miss of 15% or more versus the base case for two straight months
• Runway dropping below 12 months
• Cash falling below six weeks of OpEx^[21][16][17]

Track these triggers every week through FP&A dashboards, CRM reports, and revenue reviews.^[11][1]

Expense and Hiring Choices

Once a trigger is hit, the response shouldn't be improvised. It should already be mapped out in tiers so the team can act fast and stay calm.

• Tier 1: Freeze net new hiring in noncritical roles, pause discretionary travel and events, and defer noncritical SaaS spend.
• Tier 2: Move marketing budget toward high-ROI channels, tie sales comp to margin and cash collections, and consolidate tools and infrastructure.
• Tier 3: Cut headcount in underperforming or non-core initiatives while protecting core product and revenue teams.^{[21][22][23][24]}

Each tier should include a dollar impact on monthly cash burn, in USD. That way, leadership can see what each move buys in runway.

Runway and Margin Impact

The downside plan should roll straight into a runway view. Many growth-stage companies aim for 18–24 months of runway even in downside conditions, with 12 months treated as a hard alarm line that calls for immediate action.^{[14][15][16][17]}

You also want to model gross margin and operating margin. Discounts, downgrades, and mix shifts can squeeze margins, while tighter cost control can offset part of that pressure. The point is to show how lower revenue can still protect runway and keep funding options open.^[18][9][2]

Those tradeoffs lead into the side-by-side view of how all three scenarios shape hiring, spend, and runway.

How the Three Scenarios Differ Across Key Decision Areas

Each scenario changes spending, hiring, and runway, not just revenue.

Use the grid below to turn each revenue path into clear calls on hiring, spend, runway, and margin. It lays out the operating tradeoffs side by side.

The main question isn't which forecast looks highest on paper. It's which operating plan matches each outcome.

Best case assumes faster deal closure, stronger pricing realization, and lower churn. Base case assumes execution lands at plan. Downside assumes slower collections, more discounting, and longer sales cycles.^[28][26]

That means hiring should follow scenario triggers, not hope. In the best case, you can add hiring cohorts if the upside keeps showing up. In the base case, sequence hires and stick to critical roles. In the downside case, freeze hiring and discretionary spend.

Runway and margin decide whether a plan can be funded. In the base case, keep at least 12 months of runway before taking on new commitments. In the downside case, growth spend should wait until runway is back to 15 to 18 months.^[27][28][3]

Gross margin compression is often the first warning sign. Discounts and mix shifts can pull margin down by 6 to 10 points before revenue misses show up in the top line.^[25]

These tradeoffs set up the pros and cons of each scenario.

Pros and Cons of Each Revenue Planning Scenario

Once your triggers are set, this side-by-side view makes the next step easier: deciding how each scenario should change day-to-day operating choices. The table below shows what each one is built for and where things can go off track.

The best-case scenario works best as a readiness tool. It gives leadership a way to preapprove moves like hiring more account executives or adding customer success capacity, so the company can act fast if revenue comes in above plan. The danger is simple: treating the upside case like the main plan. If spend ramps before revenue is durable, fixed costs climb and cash gets tight.

The base case is usually the most useful option for day-to-day operations. It gives sales, finance, marketing, and operations one shared plan built on the same assumptions. That kind of alignment matters. Without it, teams can pull in different directions. The weak spot is rigidity. In a fast market, a company can miss upside if it waits too long to act. A practical fix is to set an upside trigger that opens hiring once revenue beats plan by a set percentage.

The downside scenario is about protecting runway and making contingency action faster and less subjective. When cuts are defined ahead of time, the response is faster and less emotional. That said, not every soft patch calls for a hard stop. Freezing revenue-producing roles should be saved for sustained weakness, not a short-term dip.^[28][29][18]

These tradeoffs should feed straight into the conclusion’s operating rule for hiring, spend, and runway.

Conclusion

A three-scenario revenue plan only works when each case is tied to clear triggers, spending rules, hiring thresholds, and runway and margin targets.

The rule is straightforward: the base case runs the business, the best case greenlights upside spend, and the downside case sets cuts and timing. But that only holds up when leadership reviews actuals on a fixed schedule.

Cadence is what turns planning into something useful instead of a static forecast sitting on a slide. Monthly reviews should compare actual results against the base case. Quarterly reviews should reset assumptions and runway for each scenario.

When repeat variance shows that the trend has changed, the plan should change too. If revenue stays above or below plan for two straight quarters, reset the base case. Then update hiring, spend, and triggers to line up with actual performance.

Phoenix Strategy Group helps growth-stage companies build integrated FP&A systems that connect scenario plans to budgets, hiring, and board reporting.

FAQs

How do I choose the right trigger thresholds?

Base trigger thresholds on historical performance and direct business impact, not rough guesses. Start with the metrics that hit hardest when they move: churn, sales cycle length, and close rates are common examples. Then look at how those numbers have shifted over the past 12 to 24 months so you know what “normal” looks like.

Set thresholds around clear risks or clear misses. For example, you might act when runway falls below 12 months or when revenue misses plan for two straight months. Each threshold should also have a preset response attached to it, like freezing discretionary spend or pausing noncritical hiring.

That way, you’re not making tough calls in the heat of the moment. The rule is already there, and so is the next step.

When should I move from base case to downside?

Shift to the downside scenario when performance comes in about 5% to 15% below your base case. Do the same when volatility picks up, problems start piling up, or trigger events hit, like falling revenue or higher costs.

Use it early, not late. If your model shows runway slipping below a key line like 12 months, that's your cue to act. The same goes if you may need backup moves such as:

• pausing hiring
• cutting discretionary spending
• speeding up fundraising

This scenario gives you a way to respond before the pressure gets worse.

How often should I update a three-scenario revenue plan?

Update your three-scenario revenue plan at least once a month so your projections stay in line with how the business is actually performing. A simple way to do this is to use your month-end close to compare actual results with the forecast.

You should also revise the plan after major events, like product launches, pricing changes, or major market shifts. Then, on a quarterly basis, take a deeper look at your long-term assumptions.

Related Blog Posts

• Financial Forecasting: Best Practices for Startups
• Checklist For SaaS Cash Flow Forecasting Accuracy
• ARR Forecasting for Growth-Stage SaaS
• Top-Down Revenue Forecasting: Guide