Revenue Per Sales Rep

Revenue per sales rep is the total recognized revenue in a period divided by the number of quota-carrying sales reps employed during that period. It is the bluntest productivity instrument in the RevOps toolkit, and it is also the one that boards and investors quote most often. The number answers one question: for every rep you pay, how much revenue actually shows up on the income statement? It is not the same as quota attainment, because quota attainment measures against a target while revenue per rep measures against the actual result. A rep at 80% of a $1M quota generates $800k of revenue. The org with ten such reps has $8M of revenue and a revenue per rep of $800k. The org with ten reps at 120% of a $500k quota has $6M of revenue and a revenue per rep of $600k. The second org has happier reps and a worse productivity number.

The calculation is straightforward: Revenue per Sales Rep = Total Recognized Revenue ÷ Average Number of Quota-Carrying Reps. The denominator should include account-executives, enterprise-sales reps, and field-sales reps. It should exclude sales-development-representatives, sales-engineers, and account-managers who do not carry a new-business quota. The numerator should be recognized revenue, not bookings. A company that counts bookings inflates the metric by the difference between signed contracts and delivered services. A company with heavy ramp-time should exclude reps in their first 90 days from the denominator, or the number will punish the org for hiring ahead of revenue.

A worked example: A company has $24M in annual recurring revenue. It employs 30 quota-carrying reps, of whom 5 are in ramp for the full year. The simple revenue per rep is $24M ÷ 30 = $800k. The ramped revenue per rep is $24M ÷ 25 = $960k. The difference is the cost of growth. A board that sees $800k will ask why the number is low. A board that sees $960k will ask how to scale the model. The same company, one denominator, two stories. The vp-of-sales should report the ramped number and the chief-revenue-officer should explain the gap to the board.

Sales orgs use this metric in three moments: annual planning, sales-capacity-planning, and investor updates. In annual planning, it sets the headcount math: if the plan requires $30M of new revenue and the historical revenue per rep is $600k, the org needs 50 new ramped reps. In capacity planning, it determines whether to hire or to invest in sales-enablement. In investor updates, it is a proxy for sales-efficiency-ratio without the cost data. Recruiters use it to benchmark offers: a rep moving from a company with $400k revenue per rep to one with $900k should expect a different comp structure and a different level of scrutiny.

The metric has three known failure modes. First, it conflates rep skill with company brand, pricing power, and total-addressable-market. A rep at a $100k ACV company will never match a rep at a $500k ACV company, regardless of talent. Second, it rewards sandbagging in the denominator: a manager who keeps a low-performing rep on the roster for a full year depresses the denominator and inflates the metric for the remaining reps. Third, it punishes hunter-vs-farmer models that separate new logo acquisition from expansion-revenue. A pure hunter org will show lower revenue per rep than a land-and-expand org, because the farmer's revenue is attributed to the farmer's book, not the hunter's. The fix is to compute the metric separately for new business and expansion, and to always pair it with quota-attainment distribution. Revenue per rep tells you the average. Attainment distribution tells you whether the average is real or the product of two superstars and eight corpses. The average is a lie when the distribution is bimodal. The metric is a starting point, not a verdict. The org that reads it alone is the org that fires its best manager because the team's average was dragged down by a hire that the manager had already flagged as a replacement-level-rep.