A sales capacity model works out how much a sales team can really book. It is built from the bottom up, from headcount, ramp and productivity per ramped rep. The result is a bookings number you can defend, plus the quota and pipeline it takes to get there.
The inputs that drive the number
| Input | Definition | Common error |
|---|---|---|
| Productive rep months | Ramped selling months available in the period | Counting headcount instead of ramped months |
| Productivity per ramped rep | Bookings a fully ramped seller delivers per quarter | Using top performer output as the average |
| Ramp curve | Share of full productivity by month of tenure | Assuming a linear ramp |
| Attrition | Expected departures and the gap before backfill | Modeling zero attrition |
| Hiring lag | Time from approved requisition to first productive month | Treating a start date as a productive date |
From capacity to quota to pipeline
The model runs in a chain, and each step carries its own multiplier.
Capacity gives expected bookings. Quota adds an overassignment factor above capacity, since not every seller attains. Required pipeline comes from dividing assigned quota by the win rate. A team with $12M of capacity and 15% overassignment carries $13.8M of quota, and at a 25% win rate that quota needs $55.2M of pipeline across the year.
Overassignment is a judgment call that should be grounded in the attainment distribution, not a habit. If most sellers land between 70% and 90% of quota, the gap between assigned quota and expected bookings has to absorb that. The forecasting side of the same math is covered at sales forecasting and in how to forecast revenue.
Compare bottom-up capacity against the top-down target
The value of the model shows up in the delta. When the board target is $16M and modeled capacity supports $12M, the gap is a specific ask with three possible answers. Hire more sellers earlier, raise productivity per rep, or move the target. Presenting that delta with the inputs behind it turns an argument about ambition into a decision about resourcing.
Capacity models go stale fast. Hire dates slip and sellers leave, so a plan built in November describes a different team by March. Rebuild it monthly on real dates. A higher win rate raises output and lowers the pipeline you need at the same time, so it usually beats adding headcount on cost per dollar of bookings.
Why assigned quota overstates capacity
Most capacity models start from the revenue target and the quota set against it. That skips a step. Between quota and bookings sits productive quota: what the quota is likely to produce. Each dollar of quota has its own odds of turning into revenue.
ORM measures attainment for each rep, then models it by role and region. An AE in the U.S. can sell very differently from an AE in EMEA. An account manager differs again from a new-logo seller.
How should a capacity model handle ramp?
By tenure level, by role and by region. Most models use one blended ramp: something like 25% productive in the first quarter, 50% in the second, 75% in the third, then fully productive. That is almost never true across a whole organization.ORM breaks tenure into levels and measures productivity at each one from the customer's own data:
| Tenure level | Months in seat |
|---|---|
| Level 1 | Roughly the first three months |
| Level 2 | Months four to six |
| Levels 3 to 5 | Roughly three-month steps after that |
| Level 6 | Fully tenured |
How do you decide where to add headcount?
Treat it as a puzzle with real limits. Once you have productivity by role, region and tenure, ask: what is the cheapest mix of people that meets the revenue target? ORM uses an optimization model for this. Its answer reads like a plan: hire two people in one region this quarter and three in another next month.Then add the constraints leadership actually runs the business with:
- a minimum number of sellers in a market, such as never fewer than three - a maximum, such as never more than eight - strategic investments in a region the pure economics would not choose
That turns a headcount sum into a plan that fits how the company wants to run.
Then ask where they go. If the model says hire ten reps in a region, the region needs enough market for them. ORM's rule of thumb is at least three times each rep's quota in addressable market. Only about a third of a market is buying in a given year. See territory planning.
What does a better capacity model return?
Done at the right level of detail, ORM typically sees an opportunity to create 10 to 15% more productive sales capacity from the same investment. The spend and the headcount stay the same. More of that spend turns into selling.
The model does not need to be perfect. Once its inputs are about 80% right and the plan is sound, execution matters more: reps selling, managers coaching and marketing creating demand. See the sales capacity planner to model your own team.
Frequently Asked Questions
Why do most sales capacity models break?
Rarely because the math is wrong. They break because the assumptions are too broad: one ramp curve for the whole company, one productivity figure, and the belief that an AE in one segment or region sells like an AE in another.
How long does a new rep take to reach full capacity?
Longer than most plans assume. In ORM customer data it can take a seller 15 to 18 months to confidently hit quota, and the ramp differs by role and region.
What is the difference between capacity and coverage?
Capacity measures how much a team can sell. Coverage measures how much there is to sell. Both have to clear the plan. A team with enough pipeline and too few ramped reps misses, and so does a fully staffed team with a thin book.
How do you handle ramping reps in a capacity model?
Count productive rep months rather than headcount. A rep hired in month two of a quarter with a six month ramp contributes a fraction of a fully ramped seller in the following periods. Modeling that person as a full head overstates capacity by the entire ramp curve.
How often should a capacity model be refreshed?
Monthly, against actual hire dates, terminations, and attainment. Hiring slips and attrition are the two inputs that move most, and a single hire landing two months late removes capacity that cannot be recovered inside the year.
Put these metrics to work
ORM builds custom revenue forecast models that turn concepts like sales capacity model into prescriptive action for your team.
Schedule a Demo