Most headcount plans start with a division problem. Take the revenue target, divide by quota, and hire that many reps. The math is clean and the result is wrong. Dividing a target by quota understates the roster the plan requires, and the gap shows up in Q3 when the number is short and there is no time left to hire into it.
The correct model works backward from productive capacity, which is what a roster actually delivers after quota attainment, ramp time, and attrition are applied.
How many sales reps do you need to hit a revenue target?
Divide the target by productive capacity per rep, not by quota per rep. Quota is an incentive number. Productive capacity is a forecast input, and it lands well below quota once attainment, ramp, and attrition are applied.Productive capacity per rep is quota multiplied by expected attainment multiplied by the fraction of the year the rep is both employed and fully ramped. Work through it with a $20M new business target:
- Quota per AE: $800,000 - Expected attainment across the roster: 75 percent - Effective productive-year fraction after ramp and attrition: 0.80
Productive capacity per rep-year is $800,000 x 0.75 x 0.80, or $480,000. A $20M target needs about 42 rep-years of capacity. The naive quota division said 25 reps. The gap is 17 rep-years of hiring, recruiting spend, and territory design work that never got planned.
What is productive capacity and why is it different from headcount?
Headcount counts bodies in seats. Productive capacity counts selling months that can actually carry quota. A rep hired in April with a six-month ramp contributes roughly one productive quarter to the calendar year, not three.Four deductions separate the two numbers:
| Deduction | Direction of the effect | Where it hides |
|---|---|---|
| Attainment below 100 percent | Cuts assigned quota down to whatever your roster-level attainment actually was | Assumed away in the model |
| Ramp time on new hires | Removes the selling months before a hire reaches full productivity | Counted from start date, not full productivity |
| Open territories after departures | Zero coverage for however long the seat stays empty | Treated as continuous coverage |
| Backfill ramp restart | Another full ramp curve | Counted as a replacement, not a new hire |
How do you build the ramp-adjusted headcount model?
Model each hire cohort as a quarterly capacity curve, then sum the curves across the year. A single average productivity number cannot represent a roster where reps started in four different quarters.Take a team hiring six AEs per quarter with a three-quarter ramp at 25 percent, 60 percent, and 100 percent of full capacity:
| Hire cohort | Q1 capacity | Q2 capacity | Q3 capacity | Q4 capacity |
|---|---|---|---|---|
| Tenured (10 reps) | 10.0 | 10.0 | 10.0 | 10.0 |
| Q1 hires (6) | 1.5 | 3.6 | 6.0 | 6.0 |
| Q2 hires (6) | 0.0 | 1.5 | 3.6 | 6.0 |
| Q3 hires (6) | 0.0 | 0.0 | 1.5 | 3.6 |
| Q4 hires (6) | 0.0 | 0.0 | 0.0 | 1.5 |
| Total rep-quarters | 11.5 | 15.1 | 21.1 | 27.1 |
How does hiring timing change the number you need?
Front-load hiring, because capacity delivered is a function of start date, not of budget approval date. A rep who starts in Q4 delivers one ramping quarter inside the plan year and consumes a full year of salary in the next.This interacts with seasonality. Q2 and Q4 typically run stronger than Q1 and Q3, and the third month of a quarter runs stronger than the first two. A rep who reaches full productivity going into Q4 sells through one of the two stronger quarters. The same hire delayed by one quarter comes online in Q1, one of the two weaker ones.
Two practical rules follow. Hires meant to carry the current fiscal year need to be in seat by the end of Q1. Hires approved after Q2 are next-year capacity with a current-year cost, and should be justified on that basis.
What pipeline does that headcount actually require?
Every rep you add creates a demand-generation liability equal to their quota multiplied by your coverage ratio. Hiring without funding the pipeline in front of the new territories produces expensive, idle capacity.ORM sees pipeline coverage between 3x and 5x across its customers, with most companies clustered near 3.5x and outliers as low as 1.4x. At 3.5x, twelve new AEs carrying $800K quotas require $33.6M of incremental pipeline. That is a marketing budget decision and an SDR staffing decision, and it needs to be approved in the same cycle as the hiring plan.
Coverage alone does not settle it. A plan can hit its pipeline coverage ratio and still miss, because coverage says nothing about stage composition, deal age, or which segment holds the volume. ORM data shows 10 percent or more of a typical pipeline has gone untouched for twelve months, and only about 20 percent of the value carrying in-quarter close dates on day one of the quarter actually closes in that quarter. Feed new reps from that pool and the capacity plan fails on quality rather than on quantity. The reasoning behind that is covered in why the 3x pipeline coverage rule is wrong.
How do you validate the headcount plan before committing to it?
Backtest it against last year's actuals using the same formula. Run the model on the prior fiscal year, with the roster and ramp curves you actually had, and check whether it predicts the revenue you actually booked.If the model reproduces last year within a few percent, the attainment and ramp assumptions are calibrated and the forward plan inherits that credibility. If it overshoots, one of three inputs is inflated: expected attainment, ramp speed, or the number of selling days you credited to reps who left. Fix the input that broke, not the target.
Three checks worth running before the plan goes to the board:
1. Does the sum of individual territory plans equal the company target, or does the roll-up quietly exceed it? Some over-assignment is intentional. A roll-up far above the company target means the model is padding for a problem no one has named. 2. Does the ramp assumption match observed data from the last two hiring cohorts, or is it the number from the original comp plan? 3. Does the implied pipeline requirement match what demand generation has committed to deliver, by segment and by quarter?
A headcount plan built this way survives a board meeting, because every number in it traces to an observed rate rather than to an assumption. Connecting it to your sales forecasting process is what keeps it honest through the year, since capacity that fails to materialize should move the forecast the month it happens rather than in the last week of the quarter. For the revenue-side companion to this model, see how to forecast revenue.
Frequently Asked Questions
How many sales reps do I need to hit a $20M target?
Divide the target by productive capacity per rep, not by quota. If quota is $800K, expected attainment is 75 percent, and reps average 80 percent of a full productive year after ramp and attrition, each rep contributes about $480K. A $20M target needs roughly 42 rep-years of capacity, not 25 reps.
Should I plan headcount off quota or off expected attainment?
Plan off expected attainment. Quota is an incentive number that is deliberately set above plan through over-assignment. Building a headcount model on full quota assumes every rep hits 100 percent, which almost no team achieves across a full roster.
When in the year should headcount planning start?
Start at least two quarters before the fiscal year begins. A rep hired in month one of the year does not produce a full year of revenue, so any hire meant to carry the second half needs to be in seat by roughly the end of Q1.
How do I account for reps who leave mid-year?
Apply a planned attrition rate to the roster and add backfill hires with their own ramp curves. An open territory costs the capacity of every month the seat stays empty, and the backfill then repeats the full ramp curve, so backfills need to be modeled as new hires rather than as continuous coverage.
What pipeline does the headcount plan imply?
Multiply the capacity-adjusted revenue plan by your coverage ratio. ORM sees 3x to 5x as the standard range across its customer base, with most companies near 3.5x. That coverage requirement is a demand-generation commitment that has to be funded alongside the hiring plan.
See how ORM turns these insights into action
ORM builds custom revenue forecast models for B2B SaaS companies. Not dashboards. Prescriptive analytics that tell you what to do next.
Schedule a Demo