Revenue per rep by segment reports new and expansion ARR per ramped quota-carrying seller inside each selling motion, instead of averaging them into one company number. The company average is the least useful version of this metric, because it hides the two facts leaders need: which segment produces revenue above its cost, and which one is absorbing headcount without returning it.
Deal count and deal size pull in opposite directions
Segment productivity is the product of throughput and price. An SMB seller closing sixty deals a year at $12,000 and an enterprise seller closing four at $180,000 both land on $720,000, but the paths have nothing in common. Compressing them into an average destroys the only information the metric carries.
Break each segment into its own inputs before comparing. Deal count, average selling price, and cycle length explain almost all of the variance between books, and each responds to a different intervention. Pricing changes move ASP. Enablement moves close rate. Neither moves the other.
Cost per seat differs as much as output does
Enterprise seats cost more. They carry sales engineering, longer ramp, deeper executive involvement, and a higher share of non-selling time. Comparing an enterprise seller's $1.2M against a mid-market seller's $700,000 without adjusting for that cost gap makes the wrong segment look like the growth engine.
Divide each segment's ARR by that segment's fully loaded cost. A mid-market book returning 3.5x its cost is outperforming an enterprise book returning 2.4x, no matter which one wins the raw dollar comparison.
Segment views change how you forecast the quarter
Segment productivity is also a forecasting input. Cycle length differs enough between books that a single close-rate assumption applied company-wide will be wrong in both directions at once. ORM builds close-time curves that range from one week to eighty weeks depending on the deal group, with most of the expected closes landing before week twelve. Applying a mid-market close curve to an enterprise book pulls revenue into a quarter it was never going to arrive in.
Segment-level productivity also changes what pipeline coverage means. A ratio that looks safe for a transactional book is thin for an enterprise one, which is part of why a single coverage target across segments fails so often. That argument is worked through in why the 3x pipeline coverage rule is wrong, and it feeds directly into forecast accuracy.
What to do with the split
Use it for capacity decisions. If one segment returns more per dollar and still has unworked accounts, that is where the next hire goes. If the segment with the highest revenue per rep has no addressable market left, the metric is telling you the segment is done growing, not that it deserves more headcount. Pair it with sales velocity by segment to see whether the gap is a volume problem or a pricing one.
Frequently Asked Questions
Why does a blended revenue per rep number mislead?
A blended average sits between two distributions that share no shape. An enterprise seller closing four deals a year and an SMB seller closing sixty produce a mean that neither book resembles. Decisions made on that mean, like moving quota or headcount, land on the wrong segment.
How should I segment the metric?
Split by the boundary your comp plan and quota already use, usually customer employee count or contract value band. Adding a segment your plan does not recognize creates a number nobody owns. If a rep carries accounts across two segments, allocate the seat by pipeline value rather than by account count.
Which segment should have the highest revenue per rep?
Enterprise usually does in absolute dollars, because deal size dominates. That does not make it the most efficient segment. Enterprise carries longer cycles, heavier sales engineering support, and higher fully loaded cost per seat, so compare each segment against its own cost base before ranking them.
How often should this be reviewed?
Quarterly, on a rolling four-quarter basis. Single quarters in enterprise contain too few closed deals to be stable, and one large win can move the segment average by a wide margin. The rolling view separates a trend from a lucky quarter.
Put these metrics to work
ORM builds custom revenue forecast models that turn concepts like revenue per rep by segment into prescriptive action for your team.
Schedule a Demo