Revenue Planning Simulator
Is this ending ARR a retention plan, an expansion plan, or a new-logo capacity plan?
The problem
An ending ARR target does not say whether the company gets there by keeping the book, expanding it, or hiring.
Hiring dates and pipeline targets never meet the bridge when retention, expansion, and new business stay in separate plans.
Without a repeatable answer: The team debates a single ending number and cannot see which lever is supposed to produce it.
My contribution
I built the planner in gtm-revenue-os. It is not a plan I ran at Truffle, Rapid7, Forcepoint, or Darktrace.
One example
One editable planning year. Assumptions, ARR bridge, capacity, ramp, pipeline, monthly and quarterly views, saved scenarios, and export to Markdown, CSV, or JSON. This version tests: If required new ARR is already zero, does the plan stop recommending more AEs?
- Who uses it
- A CRO or RevOps lead editing one planning year for the fictional company Northline Security.
- Decision it enables
- Whether the residual is already covered, or the plan still needs capacity and pipeline.
- What it produces
- Required new ARR after retention and expansion, productive ARR per ramped AE, and pipeline dollars shifted back by the sales cycle.
One system
GTM Revenue OS
Planning, coverage, and pipeline review for one fictional company. The figures are planning fixtures. These workflows belong to the same system, and each write-up stays on its own page.
Planning
Separate retention, expansion, and the new-business residual for one planning year.
You are on this workflow.
Coverage and capacity
See whether a hiring change moves planned capacity while bookings stay still.
Explore the project: Coverage and capacityPipeline review
Read win rate from the close, not from the current stage.
Explore the project: Pipeline review
The working planner is a separate app. These pages explain the decisions. They do not save a scenario, export a file, or open that app.
Request a walkthroughWorkflow and next steps
- Inputs → review → output
- Assumptions → validation → ARR bridge → ramped capacity → pipeline shifted by the sales cycle. Formulas only.
- Planned next
- The operating plan can copy AE count, quota, attainment, ramp, and ending target. That copy changes planned capacity only.
- Technologies in this repo or a linked project
- Next.js, TypeScript, and Postgres in gtm-revenue-os. Deterministic formulas with unit tests.
Metric to test
On the default fixture, GRR retains $9.5M and the residual new-business requirement is $9.5M. That is a planning assumption, not a result.
Links
Explore the workflow and supporting detail below.
How it works
Project overview
A separate application with tested planning formulas. This page explains the workflow.
A Next.js and Postgres application in gtm-revenue-os, documented here through its workflow and source.
What I was working from
Synthetic default book: $10M opening ARR, 95% GRR, $1M expansion, $20M ending target. Required new ARR is what remains after retention and expansion. On that fixture, GRR retains $9.5M and the residual new-business requirement is $9.5M. These are planning assumptions, not a result.
Workflow
Enter assumptions → Read the bridge → See ramped capacity and the hiring calendar → Shift pipeline creation back by the sales cycle → Save or compare a scenario
In plain language
Assumptions → Validation → ARR bridge → Capacity and ramp → Pipeline → Monthly plan
Implementation notes
Proposed architecture. The technology section identifies what each project uses today.
Next.js · TypeScript · Deterministic formulas with unit tests · Scenario rows in Postgres
Planning assumptions · Hiring plan · Monthly projection · Saved scenario
Implementation: gtm-revenue-os. In-year new logos do not churn inside the planning year, so December matches the annual bridge. Gross retention above 100% is rejected.
Goals
- Show required new ARR after retention and expansion.
- Convert quota and attainment into productive ARR per ramped AE.
- Turn the new-ARR residual into pipeline dollars from win rate, shifted back by the sales cycle.
Out of scope
- A forecast of a real company.
- Letting capacity or hiring rewrite GRR or expansion.
- Using a language model to calculate the outputs.
Metrics I would watch
These are not results unless the section above says they are on record.
- Every major output recomputes from a named formula
- Scenarios saved and compared
- Hypothesis: the hiring date and the pipeline number come from the same bridge
A plan a person can recompute changes the hiring date and the pipeline number together. No claim that a team performed.
Tradeoffs
- Straight-line monthly churn, so the year reconciles and seasonality is ignored.
- Linear ramp. Real ramps are lumpy.
- Expansion is a dollar input, so the model does not loop.
- Win rate is the rate on opportunities created, not coverage on a live open-pipeline snapshot.
What I would build next
- The operating plan can already copy AE count, quota, attainment, ramp, and ending target into this model. That copy changes planned capacity only.
Explore related work
GTM Operating Plan
Territory coverage and AE capacity for the same fictional company: where to add sellers, and the proven pipeline each hire should be built on. Potential figures are estimates.
Explore the projectRevenue Intelligence
Pipeline health from stage history, then planned new ARR against bookings and what is still required. The book is synthetic.
Explore the projectAccount Intelligence
Help enterprise sellers connect account changes to relevant conversations. Explore a fictional workflow from a signal to a draft, with evidence and assumptions kept separate.
Try the example