GTM Operating Plan
When headcount changes, does planned capacity move while bookings stay still?
The problem
Territory potential and AE headcount get narrated as revenue before anyone has booked it.
The operating model and the revenue model live in different files, so coverage math and capacity math never meet.
Without a repeatable answer: Unassigned potential gets added to the forecast, and a hiring scenario is read as bookings.
My contribution
I built the operating plan in gtm-revenue-os. It is not an employer deployment.
One example
Create a territory, assign an account, read unassigned potential, compare headcount scenarios, and apply the roster to the planner. SDR:AE and SE:AE ratios and partner-sourced pipeline are coverage, not revenue. This version tests: When AE headcount changes, does planned capacity change while bookings stay still?
- Who uses it
- A GTM lead comparing the current synthetic roster with an illustrative path from $10M to $25M ARR.
- Decision it enables
- Whether the plan is a coverage plan or a capacity plan.
- What it produces
- Coverage, unassigned potential, and a roster copy into the planner. Potential is not pipeline. Headcount is not bookings.
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.
Explore the project: PlanningCoverage and capacity
See whether a hiring change moves planned capacity while bookings stay still.
You are on this workflow.
Pipeline 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
- ICP criteria → territory assignment → coverage and ratios → roster copied into the revenue plan. Bookings stay still.
- Planned next
- Reviewed accounts with a source note. Live signal polling stays on the Account Intelligence design.
- Technologies in this repo or a linked project
- Next.js and PostgreSQL in gtm-revenue-os. Same capacity formulas as the revenue planner.
Metric to test
The $25M case is capacity math, not an outcome. Account potential stays an estimate.
Links
Explore the workflow and supporting detail below.
How it works
Project overview
A separate application for account review. Accepting a synthetic review creates an unassigned account and no opportunity.
A Next.js and Postgres application in gtm-revenue-os, documented here through its workflow and source.
What I was working from
Same fictional company. Seeded ICP criteria, territories, accounts, and two scenarios: the current synthetic roster, and an illustrative scale case toward $25M ARR. The $25M view is capacity math, not an outcome the company achieved.
Workflow
Set ICP criteria → Assign territory and owner → Read coverage and ratios → Push the roster into the revenue plan → Review the $10M to $25M case
In plain language
ICP → Territory assignment → Capacity → Coverage ratios → Planning bridge
Implementation notes
Proposed architecture. The technology section identifies what each project uses today.
Next.js · PostgreSQL · Same capacity formulas as the revenue planner · Reviewed-account intake at /data
ICP criteria · Territory · Account · Rep · GTM scenario · Planning bridge · Reviewed account submission
Implementation: gtm-revenue-os. Accepting Larkspur Regional Health, a synthetic review, creates an unassigned account with $380,000 potential and does not insert an opportunity.
Goals
- Suggest ICP fit from stored criteria.
- Show territory coverage, unassigned accounts, and potential as an estimate.
- Push AE count, quota, attainment, ramp, and ending target into the revenue planner without creating bookings.
Out of scope
- Assuming territory potential converts to ARR.
- Claiming this company reached $25M.
- CRM writeback.
Metrics I would watch
These are not results unless the section above says they are on record.
- An accepted review creates an unassigned account and no opportunity
- A rejected review leaves the account book unchanged
- Territories assigned
- Roster applied to the planner
- Hypothesis: separating capacity, coverage, and potential stops a hiring plan from being read as a bookings result
Headcount changes capacity. It does not create bookings. Potential on an account stays an estimate.
Tradeoffs
- Suggested ICP fit is a rule on stored criteria, not a model score.
- Human assignment stays separate from intake.
- The research feed and this revenue database stay separate so either can be down.
What I would build next
- Receive only reviewed accounts that include a source note.
- Leave live signal polling and sequencer push on the Account Intelligence design.
Explore related work
Revenue Planning Simulator
An editable planning year for a fictional company. Retention, expansion, and the new-ARR residual are formulas. The dollars are fixtures.
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