A headcount plan and a capacity plan describe the same sales team and answer different questions. The headcount plan counts seats and their cost by month. The capacity plan converts those seats into revenue the team can actually deliver in the period. Confusing the two is how companies approve a full sales org and still miss the number.
What Each Plan Answers
| Headcount plan | Capacity plan | |
|---|---|---|
| Unit | Seats | Productive rep-months |
| Owner | Finance | Revenue operations |
| Drives | Cost, hiring approval, budget | Quota allocation, territory design, forecast |
| Adjusts for ramp | No | Yes |
| Adjusts for attrition | Usually as a cost line | Yes, as lost productive months |
| Constrained by territory | No | Yes |
| Output | Ending headcount and payroll | Deliverable revenue by period |
Where the Two Diverge
The largest divergence is timing. A headcount plan that ends the year at 24 reps treats a March hire and an October hire identically. The capacity plan does not, because the October hire contributes almost nothing to the plan year while consuming a full seat of cost.
The second divergence is territory supply. Headcount plans have no concept of whether accounts exist for the new reps to work. Capacity plans do, and the constraint bites. Hiring into a map with no unassigned accounts forces a redraw, and ORM names territory change among the shifts that break a forecast. Sellers get distracted and execution suffers while pipeline volume looks unchanged.
The third is attainment. Headcount plans that carry a quota line usually assume full quota per seat. Real teams attain below that, and capacity models that skip the adjustment overstate deliverable revenue every time.
The Forecast Should Run on Capacity
Build the revenue plan from productive rep-months, not from ending headcount. That means applying the ramp curve to every hire, subtracting attrition and the vacancy period before backfills produce, and capping the result at what the territory map can support.
ORM decomposes a quarter into deals already in pipeline on day one, deals created and closed inside the quarter, and deals pulled forward from later periods. Capacity mostly drives the second bucket, and partially ramped reps produce very little there. A plan built on headcount silently assumes create-and-close volume the team cannot generate. Check it against pipeline coverage before signing the number.
Keeping Them Reconciled
Run one reconciliation per planning cycle that maps every approved seat to a territory, a start month, a ramp curve position, and a quota. Anything that cannot be mapped is a seat with no revenue attached, which is a cost decision rather than a capacity decision, and it should be labeled that way in the board materials.
Then measure the gap. Track forecast accuracy against the capacity plan rather than the headcount plan, and rebuild the ramp curve each year from actual cohort data. More on structuring the underlying model in how to forecast revenue.
Frequently Asked Questions
What is the difference between a headcount plan and a capacity plan?
A headcount plan answers how many seats exist and what they cost. A capacity plan answers how much revenue those seats can produce after ramp, attrition, and territory limits are applied. One is a cost document, the other is a revenue document.
Which plan should the revenue forecast use?
The capacity plan. Ending headcount overstates deliverable revenue because it counts a rep hired in the last quarter the same as a rep who was fully ramped all year.
Can a headcount plan be approved and the capacity plan still fail?
Yes, and it happens often. Finance can approve every seat while the territories to put those reps into do not exist, or while ramp timing means the hires produce after the revenue is due. Approval of cost is not delivery of capacity.
Who owns each plan?
Finance owns the headcount plan because it drives cost and hiring approval. Revenue operations owns the capacity plan because it drives quota allocation, territory design, and the forecast. The two need a shared reconciliation each planning cycle.
Put these metrics to work
ORM builds custom revenue forecast models that turn concepts like headcount plan vs capacity plan into prescriptive action for your team.
Schedule a Demo