Short answer: revenue per employee (RPE) = annual revenue ÷ full-time-equivalent headcount. The US cross-industry median sits around $250,000, but the spread is enormous – SaaS clears $400k+, hospitality runs near $95k – so the benchmark that matters is your own trailing trend against same-model peers, not the global average. Used well, RPE isn’t a vanity scoreboard; it’s a hiring governor: if it falls two quarters running while headcount rises, you’re hiring faster than you’re growing. Here are the benchmarks and the decomposition that turns the number into a decision.
The formula and its one trap
RPE = Annual revenue ÷ Total FTE headcount
Profit per employee (PPE) = Net profit ÷ Total FTE headcount
The trap is the denominator. Count full-time equivalents, not just full-time staff: convert contractors and part-timers to FTE (40 hrs/week = 1.0) and include them if they contribute to the revenue you’re dividing. Leaving out a bench of contractors flatters RPE and hides a real cost – the Revenue Per Employee Calculator lets you set the FTE base explicitly.
2026 industry benchmarks (median RPE)
| Industry | Median RPE (USD) | Read |
|---|---|---|
| Financial services | $520,000 | Capital-leveraged, thin headcount |
| Technology / SaaS | $420,000 | Code scales; high leverage |
| Manufacturing | $310,000 | Capital + automation |
| Retail & e-commerce | $260,000 | Volume, thin margins |
| General / all industries | $250,000 | The baseline everyone quotes |
| Professional services | $230,000 | People are the product |
| Healthcare | $210,000 | Labor-intensive, regulated |
| Hospitality | $95,000 | Most labor-intensive |
Two warnings before you compare yourself to a row:
- Only same-model comparisons mean anything. A services firm’s RPE cannot be judged against SaaS – different cost structures, different leverage. Find your row, then mostly ignore the others.
- RPE without margin is half a story. Outsourcing inflates RPE (revenue stays, headcount moves to a vendor’s books) while gross margin may fall. Always read RPE alongside gross margin; a rising RPE with a falling margin is a warning, not a win.
Don’t read the raw number – decompose it
A single RPE figure tells you almost nothing about why. Break it into three lenses:
- Billable ratio (services): revenue-generating heads ÷ total heads. A low RPE with a healthy per-billable-head number means your problem is overhead weight, not delivery efficiency.
- Trend vs headcount growth: plot RPE and headcount together over 4-6 quarters. RPE falling while headcount climbs = hiring ahead of revenue.
- Revenue-to-labor-cost multiple: revenue ÷ total loaded payroll. Services firms generally need 2.0×+ to fund overhead and margin; below that, the model is under water regardless of the headline RPE.
Worked case study: the agency deciding whether to hire
A 22-person digital agency closes the year at $3.85M revenue: RPE = 3,850,000 ÷ 22 = $175,000 – well below the $230k professional-services median. Panic? No – decompose:
- Billable ratio: 14 of 22 are billable (64%). RPE per billable head = 3,850,000 ÷ 14 = $275,000 – healthy. The drag is overhead headcount, not delivery.
- Trend: last year, RPE was $195k on 16 staff. Headcount grew 37% while revenue grew 23% – they hired ahead of demand.
- Cost side: average loaded cost $95k/head → revenue-to-labor multiple = 3.85M ÷ (22 × 95k) = 1.84× – under the 2.0× services floor.
The decision writes itself: pause net-new hiring until revenue catches up to ~$4.4M (which restores $200k+ RPE), and make the next hire billable, not administrative. That’s RPE working as a governor – not a report you file, but a brake you apply. (Model the hiring pause against attrition backfill in the Headcount Planning Calculator.)
Using RPE as a hiring governor – the rule
If RPE declines for two consecutive quarters while headcount rises, freeze net-new growth hiring and audit the billable ratio before adding anyone.
This single rule prevents the most common small-company failure mode: hiring on optimism, watching per-head output sink, then doing painful layoffs 12 months later. It pairs naturally with two other metrics:
- Workforce productivity – the operational cousin of RPE, measured in output/hour rather than revenue/head (Workforce Productivity Calculator). Use RPE for the board, productivity for the team.
- Cost per hire × planned hires – before a hiring wave, check that the end-state headcount still clears your RPE floor, or you’re buying a lower ratio (Cost Per Hire, Headcount Planning).
When RPE misleads
- Mid-year hiring waves deflate it temporarily – new heads land on the denominator months before their revenue lands on the numerator. Compare year-over-year, or exclude sub-90-day employees, for a clean read.
- Business-model shifts (agency → product, in-house → outsourced) break the trend line; reset the baseline when the model changes.
- Seasonality: an annual number is fine; quarterly RPE for a seasonal business swings wildly. Use a trailing-twelve-months figure.
FAQ
Is a low RPE always bad? No – it’s expected in labor-intensive industries (hospitality, healthcare). “Bad” is your RPE trending down against your history, not sitting below a different industry’s median.
RPE or profit per employee? RPE for a quick top-line efficiency read; PPE when you want the bottom-line, cost-controlled picture. High RPE with low PPE means revenue is efficient but costs aren’t – a different problem.
How often should I track it? Quarterly for the trend, annually for benchmarking. Monthly RPE at small headcounts is noise (one big invoice or one hire swings it).
Does remote/contractor-heavy staffing change the calc? Yes – convert contractors to FTE and include them if they drive the revenue counted. Otherwise you’re comparing a lean-looking RPE against peers who staff differently.
Calculators referenced: Revenue Per Employee · Workforce Productivity · Headcount Planning · Cost Per Hire. Benchmarks are directional medians; your own trailing trend against same-model peers is the number that should drive decisions.
