A ramped rep equivalent converts a partially ramped seller into a fraction of a fully productive one. A rep in month three who produces at 40 percent of a tenured rep counts as 0.4 equivalents. Summing those fractions across the team gives a capacity number that reflects what the team can sell, rather than how many badges it has.
Converting headcount into capacity
Build the conversion from your own history. Pull bookings by tenure month across several hiring cohorts, average them, and express each month as a share of the fully ramped run rate. The result is a curve, not a step, and the shape of it is specific to your sales cycle and average deal size.
The illustrative weights below show the method. Replace every value with one derived from your data.
| Tenure month | Productivity weight | Contribution per rep |
|---|---|---|
| 1 to 2 | 0 | 0.0 |
| 3 to 4 | 0.25 | 0.25 |
| 5 to 6 | 0.60 | 0.60 |
| 7 and beyond | 1.00 | 1.00 |
Why the gap matters most in a growth year
Headcount overstates capacity in exactly the years when the plan depends on it. A team scaling from 10 to 20 reps across a year ends December with 20 people and delivers the year with materially fewer equivalents, depending on when each hire started. Backloaded hiring makes that gap wider, because a rep who starts in month nine contributes almost nothing to the current plan while consuming a full salary line.
Attrition works the same way in reverse. Losing a tenured rep removes a full equivalent immediately and replaces it with zero for the length of the backfill, then a fraction for the ramp. One departure can cost more capacity than two hires add inside the same year.
Where the number enters the plan
Ramped rep equivalents belong in the denominator of any capacity calculation. Multiply equivalents by expected productivity per fully ramped rep to get carryable quota, then compare that to the revenue target. The gap is the hiring requirement, and the timing of the hires determines whether the gap closes this year or the next.
The same number should inform coverage. Required pipeline scales with the revenue a team can actually convert, so a coverage target set against headcount asks a ramping team for opportunity volume it has no capacity to work. Feed equivalents into pipeline coverage planning and into the capacity assumptions behind your sales forecasting model, and check the ramp curve against your team's win rate by tenure, since new reps often lose more of what they work.
Frequently Asked Questions
How do you calculate ramped rep equivalents?
Assign each rep a productivity weight based on tenure month, then sum the weights. A rep at 50 percent of full productivity counts as 0.5. The sum is the team's ramped rep equivalent count, which replaces raw headcount in the capacity model.
Where do the productivity weights come from?
From your own closed-won data by tenure month. Pull bookings per rep against tenure across the last several hiring cohorts, then express each month as a share of the fully ramped average. Weights borrowed from another company encode that company's sales cycle and deal size, not yours.
Why is headcount a poor proxy for capacity?
Headcount and capacity diverge most in the years when hiring is heaviest. A team that doubles from 10 to 20 reps mid-year has 20 people and far fewer than 20 ramped equivalents, so a plan built on headcount books revenue that nobody is positioned to deliver.
Do ramped rep equivalents change the quota you assign?
They change the quota you can credibly assign in total. Individual quotas usually follow a ramp schedule instead. The equivalent count tells you how much of the annual number the current team can actually carry, which determines whether the hiring plan closes the gap in time.
Put these metrics to work
ORM builds custom revenue forecast models that turn concepts like ramped rep equivalent into prescriptive action for your team.
Schedule a Demo