Operating outflows
Payroll, tools, commitments, a one-time cost, and burn sensitivity
Hypothetical changes to the monthly outflow pathScenarios
Change an assumption. See the consequence without changing the plan.
Build a named hypothetical case from the current runway baseline, adjust the supported inputs, and compare the resulting cash path. The alternative remains separate from recorded reality and from the operating plan.
- Baseline
- Current runway context
- Input
- Explicit assumptions
- Output
- Separate calculated path
Conceptual mechanicsBaseline and alternative
CurrentSupported baseline
Explicit assumption
Current pathPreserved
Scenario pathRecalculated
Product evidence
Show the assumption beside the impact it creates.
The existing legacy screenshot shows an earlier slider interface and is not suitable as current proof. A verified capture is reserved for the product-evidence contract below.
Current capture required
Scenarios: assumption and impact
Capture the current two-column comparison with the confirmed baseline, a visibly edited Scenario assumption, and its recalculated runway or cash-path impact.
public/product/scenarios-assumption-impact.pngScenario mechanics
One baseline. One visible change. Two paths to compare.
A Scenario is useful because its difference is inspectable. The current column remains read-only while the alternative column holds the assumptions that change the monthly calculation.
- 01
Begin with the current baseline
The comparison begins from the available cash, monthly cash-flow timeline, burn, and runway context resolved for the organization.
- 02
Make an explicit change
Adjust a supported dimension or add a timed hypothetical event. The changed assumption remains visible in the Scenario column.
- 03
Recalculate the alternative
The backend applies the adjustment to the monthly path and returns scenario cash, burn, runway, cash-out timing, and trajectory.
- 04
Compare without replacing reality
Current and Scenario stay side by side. Saving the Scenario persists its assumptions and computed output, not a rewrite of the source records.
Supported changes
Adjust the drivers that belong in the hypothetical case.
The interface exposes specific financial dimensions. It does not invent a recommendation, approve a decision, or turn a suggested starting point into advice.
Cash and timing
Treasury starting balances, timed cash inflow, and tax payment month
Explicit changes to position or the month an event landsForward inflows
Deals, funding, and revenue-growth assumptions
Marked hypothetical when unlanded money enters the alternativeEntity-level edits can carry timing. When unlanded forward inflow is added, the backend flags the result as projected so the interface can label the case hypothetical.
Saved Scenario lifecycle
Save the assumptions. Recheck them against the current baseline.
A saved Scenario stores its name, description, assumptions, and server-calculated output. If current cash or burn later moves, the Scenario can be marked stale rather than silently presented as current.
Recalculate updates the stored output. Replay applies the saved assumptions to today's baseline and can skip removed payroll, tool, commitment, deal, or funding references. Rename and delete affect the Scenario record itself.
- 01SaveNamed assumptions and computed output
- 02Baseline movesScenario may be marked stale
- 03Replay or recalculateAssumptions meet the current baseline
Mutation boundary
The hypothetical case changes its own record, not the financial source.
Creating or updating a Scenario persists the assumption set and its computed output in the Scenario library. It does not rewrite Treasury balances, receipts, payroll, tools, commitments, budgets, or the canonical runway.
Scenario stateEditable and discardableCanonical stateUnchanged by the Scenario
Scenarios
Test the alternative. Keep the baseline intact.
Make the changed assumption visible, compare the resulting path, and preserve the distinction between what is current and what is hypothetical.
Start free