The plan worked backwards from the target into what each team has to produce. New logos and the installed base are planned in separate lanes and meet at one reconcile step.

GTM Operating Model › Revenue Operations › Plan › Demand
From the target to what each team commits to
The plan runs backwards from the target: what has to close, what has to be in pipeline and when, and what each team must produce for it.
Target
net new ARR (annual recurring revenue) from the board and Finance: new logos plus expansion, less churn and contraction
NEW BUSINESS
New-logo bookings
by segment, from the capacity plan
↗
Wins required
bookings ÷ average new deal size
Pipeline required by month
wins ÷ win rate, timed one sales cycle ahead of the close
Source mix
required pipeline split across inbound, outbound, partner and product-led
Marketing
inbound: MQLs and the leads behind them, program budget
↗
Sales Development
outbound: meetings held, SDR headcount
↗
Partnerships
partner: registered deals, active partners
↗
Product
product-led: PQLs and the signups behind them
↗
RETAIN AND GROW
Starting ARR
by segment, from billing
Renewals due
every subscription with a term end in the period
CS coverage
accounts or ARR per CSM, by segment; sets CS headcount
Churn and contraction
expected, from the retention assumptions
Expansion pipeline
the rest of the target plus expected churn and contraction, ÷ win rate
Account Management
renewal and expansion bookings, expansion pipeline created
Customer Success
gross retention on its accounts, CS headcount
Reconcile
does required pipeline fit what each source can produce and what the team can close?
↗
If required is more than producible, change the target, the source mix or the capacity, never the conversion assumptions to make it fit.
owner · RevOps builds it; each team signs its own line; Finance signs the budget. measured by · pipeline created vs. required, by source, weekly
The ARR plan model runs this arithmetic; this page is the process around it. Where companies differ: some plan product-led and partner pipeline as a share of the total rather than bottom-up, and some fold expansion into the Account Management quota instead of a separate lane.
Terms: MQL, marketing-qualified lead. PQL, product-qualified lead (an account past the usage threshold). SDR, sales development rep. CSM, customer success manager. Win rate, the share of opportunities that close won. Sales cycle, the time from opportunity created to close. Source mix, the share of required pipeline each intake motion is asked to produce.
new-logo share
the rest
required pipeline
by source

Boxes marked ↗ open the page for that part of the model.

How to read this

  • New business starts from what has to close and works back: wins, then pipeline, then when that pipeline has to exist. A deal that closes in June has to be created one sales cycle earlier, which is why the pipeline line is set by month and not by year.
  • The source mix turns one pipeline number into four commitments. Each team signs its own line and owns it in the weekly pipeline review.
  • Retain and grow starts from a base that already exists. The planning work is coverage and realistic loss, not lead generation, and expansion pipeline is planned like new business because it re-enters Sell as a new opportunity.
  • The reconcile step is where plans usually get fudged. When required pipeline exceeds what the sources can produce, the honest moves are a lower target, a different mix or more capacity. Raising the conversion rates to close the gap only pushes the miss into the third quarter.

Where it connects

Diagram source: 19-demand-plan.drawio 19-demand-plan.svg