Planner
Create persisted revenue models and budgets, inspect the calculated outlook, and compare the plan with recorded results. Keep hypothetical alternatives in Scenarios so the current plan stays clear.
Product surface
Planner holds the operating plan and its mechanics. Related products use those outputs, but they do not become part of Planner simply because the numbers connect.
Save a recurring or throughput model, set explicit assumptions, and inspect the server-calculated monthly outlook.
Set period-based line items for payroll, tools, commitments, revenue, or a custom planning line.
Compare the plan with recorded results from the operating modules that supply actual values.
Planned roles live in Team. Their start dates and entered compensation feed a separate Hiring Impact view.
Bring a selected revenue model and planned-hire references into a combined plan readout while preserving the basis of each input.
How it works
Revenue and budget planning begin with explicit inputs. RunwayCal persists the plan, calculates its outlook, and leaves the assumptions available for review.
A recurring model can use current MRR, growth, churn, expansion, contraction, retention, and seasonality. A throughput model uses units, rate, utilization, and applicable operating drivers.
One active model supplies the calculated revenue outlook. Forecast vs actual compares that model with actual MRR from recorded monthly snapshots; it does not recast the model as realized revenue.
Budget lines persist by period and category. Actual values are read from the relevant operating modules, then compared across the same window.
Variance is review context, not a rewrite of cash or accounting history. A custom planning line without an actual source remains plan-only instead of inventing a zero result.
Financial states
A useful plan does not blur what happened, what was intended, what was calculated, and what is only being tested.
Money or operating activity that has been recorded as having happened.
Persisted operating intent, including saved models, budgets, and planned hires.
A calculated outlook produced from explicit assumptions. It is not a realized result.
A hypothetical alternative kept separate from the current plan and canonical reality.
Current operating plan
Edit the assumptions or budget lines when the operating plan itself changes.
Hypothetical alternative
Scenario adjustments and results remain separate from the current plan and recorded financial reality.
Explore ScenariosConnected planning input
A planned hire records a role, department, start date, and entered compensation. Hiring Impact can compare current and adjusted burn, runway, and a twelve-month cash trajectory while respecting the planned start month.
RunwayCal does not infer taxes, benefits, or overhead that were not entered. Filling a role changes its operating status; it does not turn a hypothetical Scenario into the canonical plan.
See the Hiring Planning decision context
Where the output matters
Planner
Build a plan that keeps its inputs, calculated outlook, and observed comparison available for review.
Start free