Planning need · Scenario planning

Test the decision before it becomes reality.

Change a hiring, revenue, cost, funding or timing assumption and see what it could do to cash and runway before you commit. The scenario stays separate from the financial position you are actually operating from.

Confirmed contextWhat is true today
Decision pointChange one assumption
Keep the current pathBaseline
Change the timingAlternate path A
Change the commitmentAlternate path B
CompareCash · Burn · Runway · Timing
Conceptual decision model, not product UI. Hypothetical paths branch from current context and remain distinct until a person decides what to do.

01 · Current reality

Start from the financial position you already have.

A useful scenario needs an anchor. RunwayCal's Baseline is a scenario construct aligned with the current confirmed position in Runway Overview. It is the comparison point, not a license to treat every future assumption as recorded fact.

Confirmed positionAnchors the questionHypothetical pathTests the consequence

02 · Assumption

Change the assumption, not the actuals.

Ask a concrete question. What happens if we hire now? What if revenue grows more slowly? What if funding or collections arrive later? Each change belongs inside the scenario until the business confirms something different.

01

Hiring

Add a role, change its start month, or remove a planned hire.

02

Revenue

Change a deal or revenue assumption without recording a receipt.

03

Spend

Test tools, commitments, payroll, or a one-time expense.

04

Funding

Move a possible cash inflow or change when it may arrive.

05

Timing

Shift when an inflow or outflow enters the cash path.

03 · Consequence

See the consequence move through the plan.

The changed assumption is only the input. The decision becomes clearer when you can see how it changes cash, monthly burn, runway, and the timing of a possible cash-out point.

Changed assumptionHire starts in JulyIllustrative question
Cash pathMoves
Monthly burnChanges
RunwayRecomputes
TimingShifts
Conceptual causal model. It shows the reasoning relationship, not a product screen or a customer result.

04 · Product proof

Build the possible path in Scenarios.

Begin with Baseline or use Conservative, Growth, and Expansion as editable starting points. Save the scenario, reopen it against the current baseline, and compare the supported consequences without changing confirmed records.

RunwayCal Scenarios showing the current baseline, editable assumptions, and a hypothetical scenario output
Inside RunwayCal · Scenarios. Change supported assumptions, review the resulting cash and runway path, and save the question without changing actual financial records.

Presets are seeded from organization data and expose their assumptions. They are not predictions or recommendations.

Current comparison can place Baseline beside selected saved scenarios. CSV export preserves the baseline, scenario, delta, and whether the path is hypothetical.

05 · Compare

A scenario is useful when you can compare it.

The question is not whether a path looks optimistic or cautious. It is how each explicit assumption changes the financial path relative to the same anchor.

BaselineSaved scenario
Baseline compared with a saved scenarioTwo cash paths begin at the same confirmed point, then separate after an assumption changes and end at different consequence states.Assumption changes
Same anchorDifferent consequenceHuman decision
Conceptual comparison, not product UI. The lines show how one explicit assumption can create a different path from the same anchor.

06 · Trust boundary

Save the question, not a new reality.

Saved scenarioA reusable set of hypothetical assumptions

It can be reopened and recomputed against the current baseline.

≠
Confirmed realityRecorded financial events and current context

It changes only when the underlying real-world state changes.

Saving a scenario preserves the question. It does not post a transaction, confirm revenue, hire a person, or rewrite actuals.

07 · Decide

Compare the paths. Then decide what becomes real.

Bring the scenario back to the operating question. Review the current runway, the numbers behind it, and the planning assumptions before committing. RunwayCal shows the consequence; the business chooses the action.

Before the commitment

See the consequence before you make the move.

Test the assumption against your current financial context while keeping the hypothetical path clearly separate from what is true today.