Productivity per ramped rep measures output using only sellers who have completed ramp. Bookings, new ARR, or pipeline created goes in the numerator, and the denominator counts fully ramped heads instead of total headcount. The distinction matters because the blended version moves whenever hiring pace changes, which makes it useless for the question most teams are actually asking.
Why the blended number misleads
| Scenario | Blended productivity | Ramped productivity | What is true |
|---|---|---|---|
| Heavy hiring quarter | Falls | Flat | Nothing changed in seller output |
| Hiring freeze | Rises | Flat | Nothing changed in seller output |
| Pricing pressure | Falls | Falls | Output genuinely declined |
| Territory recarve | Falls | Falls | Execution disrupted |
Building the calculation
Set the ramped threshold from your own attainment history rather than a default number of months. Pull attainment by tenure cohort, find the point where the curve flattens, and use that as the cutoff. Reps below it get reported against ramp expectations. Reps above it feed the productivity figure.
Keep the numerator consistent with how the rest of the business measures output. If capacity planning runs on new ARR, use new ARR here. Mixing bookings in one report and ARR in another produces two productivity numbers that disagree and cannot be reconciled without rebuilding both.
Reading a decline correctly
When the ramped figure falls, the cause sits in conditions rather than in headcount mix. ORM has documented the mechanisms that drive this. A new competitor creates pricing pressure and average deal size drops. Market uncertainty slows buyer decisions and cycles stretch from qualified to closed. Territory changes distract sellers, and coverage can hold in the standard 3x to 5x range while execution suffers.
Each of those shows up in ramped productivity before it shows up in a quarterly miss, which is the argument for tracking it monthly rather than at plan time. See win rate and sales velocity for the two measures that usually confirm which mechanism is running.
Feeding it into capacity plans
Capacity models multiply a per-head productivity figure by planned heads. Using the blended number understates ramped seller output and overstates what a new hire contributes in their first two quarters. Running the plan with the ramped figure for existing sellers and a separate ramp curve for new hires produces a bookings plan that survives contact with the hiring calendar.
Frequently Asked Questions
Why exclude ramping reps from the calculation?
Because including them measures hiring pace rather than seller output. A team that doubled headcount last quarter will show falling productivity per rep even if every experienced seller improved, which sends the wrong signal to anyone reading the number.
When does a rep count as ramped?
When they carry full quota under the ramp schedule and have been in territory long enough to have a normal cycle behind them. Set the threshold from your own historical attainment curve rather than a default, since cycle length drives it more than tenure does.
How does this change capacity planning?
It gives the correct per-head number to multiply. Capacity models built on blended productivity understate what ramped sellers deliver and overstate what new hires will deliver, which produces plans that miss in both directions at once.
What if the ramped figure is falling?
That is a real signal rather than a mix effect, so look at conditions rather than people. Competitive pricing pressure lowers average deal size, and buyer indecision stretches cycles from qualified to closed. Both reach this metric before they reach a quarterly miss.
Put these metrics to work
ORM builds custom revenue forecast models that turn concepts like productivity per ramped rep into prescriptive action for your team.
Schedule a Demo