Revenue per employee as a metric tree

Revenue per employee divides total revenue by the number of full-time equivalents (FTEs) in the organisation. The formula is simple: Total Revenue divided by Total FTEs. The result is a single number that approximates how much economic output each person in the business helps to generate.

The metric has endured because it is easy to calculate, universally available (every company knows its revenue and headcount), and comparable across firms in the same industry. It appears in the financial filings of public companies, in HR analytics dashboards, and in productivity benchmarks published by firms like the American Productivity and Quality Center (APQC). At the median, companies across all industries generate roughly £310,000 per employee. Top-performing organisations at the 75th percentile reach £565,000, while bottom-tier performers sit around £176,000.

But simplicity is also the metric's weakness. Revenue per employee conflates dozens of different factors into a single ratio. A pharmaceutical company with 500 employees and £2 billion in patent-protected revenue will show astronomical revenue per employee, but that figure reflects intellectual property and regulatory moats, not workforce productivity. A consulting firm with £200,000 per employee might be far more operationally efficient on a per-person basis. Without decomposition, the number invites misleading comparisons and poor decisions.

Revenue per employee is a ratio with two components: the numerator (total revenue) and the denominator (total headcount). A metric tree decomposes both sides, revealing the operational levers that actually drive the number up or down. This dual decomposition is what transforms a blunt benchmarking figure into a genuine management tool.

On the revenue side, growth can come from acquiring new customers, expanding revenue from existing customers, improving pricing, or entering new markets. On the headcount side, efficiency gains come from automation, process improvement, organisational design, and decisions about what to build internally versus outsource. The metric tree below shows how these branches connect.

The power of this decomposition is that it separates revenue growth from headcount growth. A company that doubles revenue while tripling headcount has actually become less efficient on a per-employee basis, even though absolute revenue is climbing. Conversely, a company that grows revenue by 30% while holding headcount flat has improved revenue per employee by 30%, a sign of genuine operating leverage.

By breaking the denominator into functional categories, you can also identify where headcount is growing fastest relative to its contribution. If support and operations roles are growing at twice the rate of revenue, that signals a process or tooling problem. If G&A is expanding faster than the business, overhead is creeping in. The tree makes these dynamics visible before they become entrenched.

Revenue per employee varies enormously across industries, which is why cross-industry comparisons are rarely useful. The differences reflect business model fundamentals: capital intensity, labour intensity, regulatory structure, and the role of intellectual property. The table below provides representative benchmarks to help you calibrate where your organisation sits relative to peers.

For SaaS companies specifically, the benchmarks shift with company stage. The median revenue per employee for private SaaS companies is approximately £130,000. At £1-3 million in ARR, the median sits around £100,000 per FTE. By £20 million in ARR, well-run companies approach £150,000. At scale beyond £50 million in ARR, the target rises to £250,000-£300,000, which is roughly the level needed for sustained profitability.

Product-led growth (PLG) companies consistently outperform, with medians around £350,000 per employee. Infrastructure and developer tools companies like Datadog and Cloudflare routinely exceed £400,000, driven by highly scalable products and technical audiences that require less sales support. Bootstrapped companies also tend to show higher revenue per employee than venture-backed peers at every ARR band, likely because the absence of external funding imposes natural discipline on hiring.

Because revenue per employee is a ratio, you can improve it by growing the numerator faster than the denominator, shrinking the denominator relative to the numerator, or both. The metric tree gives you a structured way to identify which lever offers the most headroom in your specific context.

The most effective approach combines revenue growth with headcount discipline. High-performing companies do not simply refuse to hire. They hire deliberately, ensuring that each new role either directly generates revenue or demonstrably enables others to generate more. The metric tree supports this by making the expected impact of each hire visible: if you add a sales rep, what is the expected revenue contribution? If you add an engineer, which revenue driver does their work support?

One practical technique is to set a revenue-per-employee target for each quarter and treat it as a constraint in headcount planning. If the current ratio is £150,000 and the target is £175,000, every proposed hire must be justified against its expected contribution to revenue growth. This does not mean rejecting all hires. It means being explicit about the trade-off between investment in people and efficiency.

Revenue per employee is useful precisely because it is simple, but that simplicity creates genuine blind spots. Understanding when the metric misleads is just as important as knowing how to improve it.

1. 1

   Heavy use of contractors and outsourcing

   Companies that rely on contractors, agencies, or outsourced teams will show artificially high revenue per employee because those workers do not appear in the FTE count. The work still gets done and still costs money, but the metric does not reflect it. Always pair revenue per employee with revenue per total workforce cost for an accurate picture.

2. 2

   Capital-intensive business models

   In industries like energy, mining, or financial services, revenue is driven primarily by capital assets, not by the people who manage them. A hedge fund with 20 employees managing £5 billion in assets will show extraordinary revenue per employee, but the figure reflects capital allocation, not workforce productivity.

3. 3

   Rapid hiring phases

   When a company hires aggressively, revenue per employee drops mechanically because new hires take time to become productive. A declining ratio during a scaling phase is expected and not necessarily a sign of inefficiency. The metric tree helps by showing whether revenue growth is tracking behind headcount growth temporarily or structurally.

4. 4

   Revenue recognition timing

   Companies with lumpy revenue, such as those with large enterprise contracts recognised over time, may show volatile revenue per employee from quarter to quarter. Using annualised or trailing twelve-month revenue smooths this effect.

5. 5

   Ignoring employee wellbeing

   Optimising revenue per employee to the exclusion of other metrics can lead to burnout, understaffing, and high turnover. A company that achieves £500,000 per employee by running a skeleton crew is not efficient; it is fragile. The metric tree should include leading indicators of workforce health alongside the efficiency ratio.

Revenue per employee does not exist in isolation. It is one node in a broader efficiency metric tree that includes profitability ratios, cost metrics, and operational productivity measures. Understanding how these metrics relate to each other prevents you from optimising one at the expense of another.

The most valuable metric trees place revenue per employee alongside these complementary metrics rather than treating it as a standalone KPI. When a board or leadership team reviews revenue per employee, they should simultaneously see gross margin (to ensure revenue quality), profit per employee (to ensure cost discipline), and retention or engagement scores (to ensure sustainability).

This is where a metric tree tool becomes particularly powerful. Rather than tracking these metrics in separate spreadsheets or dashboards, a tree structure shows how they connect. Revenue per employee feeds into operating leverage. Gross margin gates whether revenue growth is profitable. Retention rates determine whether efficiency gains are durable. The tree makes these dependencies explicit, so improving one metric does not inadvertently damage another.