Skip to article
Start here

Base, upside, downside: how to build startup financial scenarios

Build startup financial scenarios by duplicating a base forecast and changing the assumptions tied to a specific operating story. A downside might combine slower acquisition with delayed hiring; an upside might require more delivery capacity. Compare monthly cash, revenue, costs, and funding needs. Document why each assumption changes instead of scaling every line by the same percentage.

In this guide

Give the base case a job

Use the base case as the plan you intend to operate against with the evidence you have today. It does not need to be the midpoint between your best and worst imaginable outcomes. It needs an acquisition plan, a cost schedule, and a cash position you can explain.

Separate commitments from choices. Signed employment offers and noncancelable contracts behave differently from a tentative hire or an optional campaign. Keep a short note identifying which assumptions are uncertain and which costs can actually move. Otherwise, a downside case can appear affordable only because it removes spending you are already obligated to pay.

Write the operating story before changing the inputs

The following matrix is an illustrative setup for a monthly subscription product. The renewal rate refers only to the first monthly renewal; later retention assumptions must also be set. These values are arbitrary examples, not benchmarks or estimates of likelihood.

Illustrative scenario assumptions
DriverBaseDownsideUpside
New subscriptions per month201030
First monthly renewal retention90%80%90%
Monthly price$50$50$50
Planned hire startsJulyOctoberJune
Operating storyCurrent acquisition planSlower sales and weaker early retentionFaster sales require earlier capacity

Create these alternatives in Startup Model Builder using Scenarios and Duplicate as scenario. Rename each copy before changing its assumptions.

Check what has to move together

More customers may create more onboarding work, support time, or processing expense. If a cost is driven by customer counts or collections, use that relationship in the model. Review fixed costs separately: a larger account base does not automatically change every rent or software payment.

The upside hire moves earlier because the example assumes more delivery capacity is needed. The downside hire moves later only if the role can actually wait. If delaying the person reduces acquisition or service capacity, reflect that effect too. A lower payroll line alone is not the whole decision.

Pricing stays unchanged in the matrix because the operating stories do not include a pricing change. Avoid lowering every assumption just to make a scenario look pessimistic. Every changed input should have a reason you could explain to someone reviewing the model.

Compare cash timing before celebrating revenue

Review the monthly cash curve and its lowest balance in each scenario. Then inspect recurring revenue, gross profit, operating expenses, and any required financing. The high-revenue scenario can require earlier spending, so it is worth checking whether the business can fund the path to that outcome.

Do not hide the shortfall by placing an unspecified funding round wherever cash turns negative. First identify the operating cash need, then add an explicit funding amount and receipt month if financing is part of the plan. Test a delayed receipt separately.

The runway guide shows why month-end balances need careful interpretation. For a close cash call, examine actual payment dates outside the monthly model rather than assuming a positive closing balance guarantees liquidity all month.

Use a one-driver test when you need to isolate a cause

A scenario combines assumptions into a possible operating plan. A one-driver sensitivity test asks a narrower question: what changes if acquisition slows while other assumptions stay fixed? Both are useful, but they answer different questions.

Start with the isolated test if you cannot explain a result. Then build the operating scenario with the linked decisions included. For example, first test a later hire's cost effect, then consider whether that delay changes customer delivery or sales. See the hiring-plan guide for the salary timing calculation.

End with a decision and a revisit trigger

For each scenario, record the action you would take and the evidence that would justify it. That might be a sustained change in signed customers, a postponed financing receipt, or a capacity constraint. Choose thresholds from your situation rather than copying an arbitrary percentage from a template.

Keep the previous forecast when you update the plan. Comparing what you expected with what happened is more useful than silently rewriting the assumptions until the chart looks comfortable.

Related questions

Do I need exactly three scenarios?

No. Base, upside, and downside are useful labels, not a requirement. Add a separate case when it tests a distinct decision, such as a funding delay. Avoid creating copies that do not lead to a different action.

Is the downside case the worst possible outcome?

Only if you deliberately define it that way. Describe the assumptions it contains and the risks it excludes. A scenario does not establish a probability or prove the business can survive every adverse event.

Test the decisions behind your plan.

Duplicate the base case, change the assumptions behind one operating decision, and compare the results side by side.

Build your scenarios