What Is Revenue Per Employee? Calculation, Caveats, and What It Misses

Revenue per employee is annual revenue divided by total headcount. It is the simplest available measure of whether a company converts people into output efficiently. The number itself matters less than its direction: whether the ratio rises or falls as you add people is the signal, and comparing your figure to a published benchmark is usually comparing two different calculations.

The two definitions that decide the number

Both inputs are ambiguous, and the ambiguity is where most of the variance between published figures comes from.

Which revenue. Annual recurring revenue and trailing twelve-month revenue give materially different answers for a fast-growing company, because ARR is forward-looking and TTM is backward-looking. Either is defensible. Switching between them quarter to quarter is not, and it is the most common way this metric becomes meaningless inside a company.

Which headcount. Full-time employees only, or contractors too. If contractors are doing ongoing work, count them. Excluding them lets a company move work from payroll to invoice and post an improving ratio while nothing about the business has changed. That is the metric being gamed, usually without anyone intending to.

Pick a convention, write it down, and keep it. The trend is the product; the absolute number is nearly worthless without it.

Why benchmarks disappoint

Published revenue-per-employee figures range across an order of magnitude for companies of similar size, and most of that range is definitional rather than real.

Beyond the revenue and headcount conventions, business model dominates. A self-serve software company and a company with a services component are not comparable on this ratio at any stage, and neither is comparable to one that outsources implementation. Comparing across those categories produces a number that feels like a verdict and contains no information.

Your own trajectory is the useful comparison. If the ratio falls every time you hire, the structure is absorbing the headcount. If it holds or rises, the additions are carrying their weight.

If you want to work through your own numbers rather than the theory, the Revenue per Employee Planner explains how the planning process works before you start.

The three things it cannot tell you

• Whether the revenue is durable. A ratio propped up by a concentrated customer or a one-off contract looks identical to one built on a broad base.
• Whether the team is under strain. High revenue per employee and imminent attrition are entirely compatible. The ratio counts output, not sustainability.
• Whether you are efficient or under-invested. A company starving its roadmap will post an excellent ratio for several quarters, because the cost of not building arrives later than the saving.

That last one is the trap in using the metric as a target. Anything you measure can be improved by cutting the denominator, and the denominator is people.

Why the metric matters more now than it did

For most of software's history, revenue growth required roughly proportional hiring, which made revenue per employee a slow-moving ratio that mostly reflected business model.

That link weakened. Tooling now compresses the work inside a role enough that two companies with identical revenue can differ substantially in headcount, and the difference is structural rather than incidental. The ratio is the simplest available check on which side of that you are on: whether a company is capturing the change, or buying tools while keeping the structure that made the headcount necessary.

It is a lagging measure of a decision made much earlier, in how the work was structured in the first place.

Common questions

How do you calculate revenue per employee?

Annual recurring or trailing twelve-month revenue divided by total headcount. The decisions that matter are which revenue figure and which headcount: use the same definition every quarter, and count contractors doing ongoing work as headcount, because excluding them makes the number improve while nothing changes.

What is a good revenue per employee for a startup?

There is no single threshold, and published figures vary enormously because companies use different revenue and headcount definitions. Your own trend line is far more informative than any external benchmark: whether the ratio is rising or falling as you add people tells you what you need to know.

Should contractors count in revenue per employee?

Yes, if the work is ongoing. Excluding them produces an improving ratio with no change in the underlying business, which is the most common way this metric gets quietly gamed. Exclude genuinely one-off project work, and state which convention you use.

What does revenue per employee not tell you?

Three things: whether the revenue is durable, whether the team is under strain, and whether the ratio is high because you are efficient or because you are under-invested. A company starving its roadmap will post an excellent ratio for several quarters before the consequence arrives.

Why does revenue per employee matter more now?

Because AI tooling changed the relationship between headcount and output, so the historical assumption that revenue growth requires proportional hiring no longer holds. The ratio is the simplest available measure of whether a company is capturing that or just spending on tools.