Revenue Per Employee
The average annual revenue generated per full-time equivalent employee, measuring how productively a company converts payroll into top-line revenue.
◆ Currency
Formula
Built from
What it measures
Total revenue, normalized to a twelve-month run rate, divided by the full-time equivalent headcount carried during the same period. For a recurring-revenue business you can use ARR as the numerator; for blended or non-recurring models, use total annual revenue. The denominator should be a consistent FTE count, with contractors and part-time staff converted to FTE equivalents or excluded — applied the same way every period so the trend stays comparable.
Why it matters
Revenue per employee is the simplest read on operational leverage: how much top line each person on payroll supports. You use it to know whether the business is getting more productive as it scales or whether hiring is outrunning growth. Investors and boards lean on it because it is hard to fake and easy to benchmark — a company that doubles revenue without doubling headcount is building leverage, while one that adds people faster than revenue is heading toward margin compression. It is a fast proxy for product-market fit, automation, and the efficiency of the operating model.
How to read it
Read this as a trend, never a single snapshot. Compare each period to the prior period, to your plan, and to published benchmarks for your stage and vertical. A flat or rising number while headcount grows means revenue is growing faster than the team — you are adding leverage. A falling number while you hire means revenue is stalling relative to payroll, which compresses margins. Segment by function — revenue per sales head, per engineer, per support rep — to find which teams are driving or dragging productivity, but use the company-wide figure for overall health and board reporting.
What good looks like
Good
Revenue per employee growing year over year as revenue scales faster than headcount; the figure sits at or above the median for your stage and vertical, led by high-gross-margin, expansion-driven businesses.
Watch
Revenue per employee flat or declining year over year, or trending below the median for your stage and vertical; hiring is outrunning revenue growth.
Bad
Revenue per employee well below peers in your stage and vertical, or falling sharply while headcount climbs; signals over-hiring relative to revenue and a rising cost structure.
Watch-outs
- Misclassifying headcount. Mixing full-time employees with contractors, part-time, or offshore roles distorts the denominator. Standardize on FTE equivalents and be transparent about who is included, applying the same basis every period.
- Comparing across radically different business models. High-margin B2B SaaS will naturally show higher revenue per employee than consumer apps, e-commerce, or services businesses. Benchmark only against peers in your vertical and stage.
- Using a single month's snapshot. Headcount swings with hiring cycles and departures. Use a consistent period-end or average headcount and always compare like-for-like measurement windows.
- Ignoring the numerator's composition. A flat figure can hide a shift in revenue mix. Segment by revenue type — recurring ARR versus non-recurring services — so improvements and erosion don't cancel out and hide each other.
Worked example
Hypothetical
A SaaS company runs at $50M ARR with 150 employees, so revenue per employee is $50M ÷ 150 = $333K. The next year ARR grows to $65M and the team grows to 170, lifting the figure to $382K — revenue outpaced hiring and productivity improved. Had the company instead hired to 190 employees while ARR reached only $55M, revenue per employee would fall to $289K, a signal that hiring was outrunning revenue.