Revenue Per Employee

Revenue per employee is a blunt but useful measure of operational efficiency. Take your ARR, divide it by headcount, and you get a dollar figure that tells investors and operators how productively the business converts people into revenue. Higher is better, up to a point.

Revenue per employee formula

Revenue Per Employee = ARR / Total Full-Time Headcount

If your company generates $5 million in ARR with 25 employees, your revenue per employee is $200,000. Some teams use total revenue instead of ARR, but for SaaS the ARR version gives a cleaner read because it strips out one-time charges and services revenue.

SaaS benchmarks by stage

The number shifts sharply as companies scale. Seed-stage companies typically run $100,000 to $200,000 per employee. They're still building and often over-hiring for the revenue they have. Growth-stage companies (Series B and beyond) target $200,000 to $350,000. Late-stage and public SaaS companies often reach $250,000 to $500,000+. Atlassian, famously, has exceeded $500,000 per employee by running a largely self-serve model with minimal sales headcount.

These benchmarks come with a caveat. Companies with heavy professional services arms will naturally run lower because services revenue per head is much lower than product revenue per head.

What drives revenue per employee

There are two ways to move the number: grow ARR or reduce headcount. The healthy version focuses on the numerator.

Retaining existing revenue is the most overlooked lever here. Every dollar of revenue churn you prevent increases ARR without adding a single person to payroll. If you recover $50,000 in annual revenue from failed payments through better dunning, that's $50,000 added to ARR with zero incremental headcount. Your revenue per employee goes up purely from plugging a leak.

Product-led growth also helps. Self-serve acquisition and expansion require fewer salespeople per dollar of revenue than traditional enterprise sales. In practice, the companies with the highest revenue per employee tend to combine strong retention with efficient, product-driven go-to-market.

Limitations

This metric is easy to game. Outsource your support team to contractors and headcount drops while the work stays the same. Hire an army of part-time workers and they might not count as full-time equivalents. Revenue per employee also doesn't tell you about employee satisfaction, product quality, or sustainability of the pace.

It also penalises companies that invest early in building teams for scale. A business that hires ahead of growth will look inefficient on this metric even if the strategy is sound. Use it as one signal among many, not as the single measure of operational health. Pair it with subscription revenue trends and retention metrics for a fuller picture.