Sales Ops Glossary · Team & Compensation
Sales capacity planning is the process of calculating how many productive sales reps are needed to achieve a revenue target, accounting for quota per rep, ramp time for new hires, expected attrition, and the lag between hire date and full productivity. It connects the revenue plan to the hiring plan and is the primary input for sales headcount budget decisions.
Capacity planning answers one practical question: given our revenue target, how many fully productive reps do we need, and how many do we need to hire — and by when — to reach that number? The answer is almost never 'hire the same number we have now.' Attrition, ramp lag, and rising quotas all erode productive capacity continuously. A team that looks fully staffed in January can be operating at 70% of required capacity by Q3 if two reps leave and replacements are still ramping.
Capacity planning is most valuable as a forward-looking exercise, not a retrospective one. The goal is to surface the headcount gap 6–9 months before it creates a revenue problem, giving recruiting enough lead time to find and hire the right talent. Teams that do capacity planning reactively — after missing a quarter — are perpetually 2–3 quarters behind. The best RevOps teams run capacity models at least quarterly and update them whenever a rep leaves, a territory changes, or the revenue target is revised.
Companies that skip formal capacity planning consistently over-estimate their available revenue capacity and under-estimate their hiring lead time. The result is a revenue forecast built on paper reps who don't exist yet — and a Q4 scramble that no amount of effort can fully recover. A 20% capacity gap entering a quarter translates directly to a 15–20% revenue miss, after accounting for the variance of individual rep performance. For a $50M ARR target, that gap is $7.5M–$10M in missed revenue.
Capacity planning also prevents the opposite failure: over-hiring. Teams that hire reactively — adding reps after missing a quarter — often onboard too many people simultaneously, overwhelming the onboarding infrastructure and diluting manager attention. New hires in overcrowded cohorts take 20–30% longer to ramp and are more likely to churn in their first year. A forward-looking capacity model prevents both under-staffing and the over-correction that follows it.
Evaluating team & compensation tools?
Browse software →Build the capacity model in a shared spreadsheet or planning tool that the VP of Sales, CFO, and Head of Recruiting all own. Each stakeholder needs a different view of the same data: Sales sees productivity and quota coverage; Finance sees cost and cash exposure; Recruiting sees open roles and required start dates. A single source of truth prevents each team from working from different headcount assumptions.
Run two scenarios: a base case and a stress case. The base case uses your expected attrition and on-schedule hiring. The stress case models what happens if attrition runs 5 points higher than expected and three hires land a quarter late. If the stress case creates a catastrophic revenue gap, your base plan doesn't have enough buffer. Most finance teams want to see both scenarios before approving the headcount budget.
Update the model every time something changes — a rep leaves, a hire is delayed, a territory is split, or the revenue target is revised. A capacity model that was accurate in January and hasn't been touched since May is no longer useful. Build a quarterly refresh into the RevOps calendar, timed to coincide with board reporting so leadership always has a current view of their capacity position relative to the year's target.
If your AEs carry $1M quotas but average 80% attainment, using $1M as your capacity number overstates available capacity by 25%. A 10-person team you model at $10M capacity is actually delivering $8M, creating a $2M gap that only appears in the revenue forecast at Q3 pipeline reviews.
A model that plans for 15 AEs without accounting for the fact that 4 will leave during the year is planning on 15 productive reps and will have 11 by September. The 4 replacement hires are still ramping, net capacity drops to 13 equivalents, and the revenue plan is short by the output of 2 productive AEs for the entire second half.
VP of Sales who assumes a 30-day hire-to-start timeline for enterprise AEs will consistently miss their start date commitments. Sourcing, screening, offers, and notice periods for experienced enterprise reps routinely take 60–90 days. Build 90 days of recruiting lead time into the model as the default assumption.
When RevOps runs capacity planning in a silo, finance builds their own headcount assumptions. When the two models diverge — as they always do — the reconciliation happens at the board level, which is the worst place to surface a disagreement about whether you can actually hit the revenue target.
Sales planning software provides structured templates for capacity modeling with built-in ramp, attrition, and quota variables. Revenue operations platforms connect headcount models to CRM pipeline data so that projected capacity is always compared against actual pipeline coverage. Spreadsheets remain common for smaller teams but break down in accuracy and collaboration when headcount exceeds 20–30 reps.
For SaaS mid-market AEs, a standard annual quota is $600K–$1M per rep. Enterprise AEs typically carry $1M–$2M. When you sum up all individual rep quotas, the total should exceed your company revenue target by 15–25% — this buffer is called quota overage or quota cushion, and it accounts for expected attrition, ramp gaps, and the statistical reality that not all reps will hit plan in any given year.
Ramp period determines how quickly a new hire contributes productive capacity. A 6-month ramp means a rep hired January 1 is only fully productive from July 1 onward — effectively 50% of full-year capacity for their hire year. If you need 10 fully productive AEs by July 1 and have a 6-month ramp, you need those hires seated by January 1, which means offers accepted in October of the prior year. Missing this timing chain cascades directly into a mid-year capacity shortfall.
At minimum, quarterly. Many RevOps teams now maintain a rolling 12-month capacity model that is updated monthly with actual attrition, delayed hires, and any quota or territory changes. The model should also be refreshed any time the revenue target changes, a major account is won or lost that affects territory design, or headcount budget assumptions change. A stale capacity model is worse than none — it creates false confidence in a plan that no longer reflects reality.
Headcount planning is a finance-driven exercise that counts bodies and costs. Capacity planning is a revenue-driven exercise that translates bodies into expected output. Headcount planning asks: 'How many people can we afford?' Capacity planning asks: 'How many productive reps do we need to hit the revenue target, and how does ramp and attrition affect when we actually have them?' The two should inform each other — capacity planning feeds the headcount budget; the headcount budget constrains capacity targets.
New product lines and new segments typically require separate capacity models because productivity assumptions differ. A rep selling into a new vertical has no established relationships, a longer ramp, and likely lower attainment in year one. Model new segment reps with a 20–40% productivity discount in their first year relative to established-market reps. If you're launching a new product line alongside an existing one, decide upfront whether existing reps sell both (requires quota modeling for mixed portfolio) or specialized reps are hired (requires a full capacity model for the new motion).