AmCFOVisit Website →
← Back to blog

Revenue per Employee Benchmarks: Why One Average Misleads

October 11, 2026
Revenue per Employee Benchmarks: Why One Average Misleads

Revenue per employee (RPE) is the average revenue your organization generates per employee, and it works as a practical efficiency benchmark for comparing headcount productivity. The metric is most useful when you measure it consistently over time and compare it against peers in your own industry, using references like the NYU Stern employee metrics table rather than a single average across industries.

TL;DR:

  • Calculate RPE by dividing period revenue by average beginning and ending headcount, converting part time staff to full time equivalents and matching periods exactly.
  • The broad dataset average is about $111,028, but software, hospitals, and hospitality businesses differ structurally, so compare against sector peers rather than that aggregate.
  • Layoffs can raise RPE when headcount falls faster than revenue, while contractor reliance can inflate it because contractors usually sit outside employee counts.
  • Pair RPE with profit per employee and revenue growth before acting; pricing, cross selling, and automation can lift the ratio without relying on headcount cuts.
Amcfo
Make Revenue Benchmarks More Useful
AmCFO provides financial reporting and analysis to help businesses understand profitability, cash flow, and make confident decisions.
Explore financial guidance

Table of Contents

What revenue per employee measures and when it's informative

RPE divides total revenue by headcount, but the quality of the number depends entirely on what goes into each side of that fraction. Revenue should reflect the operating activity you actually want to measure, and "employee" needs a consistent definition before you compare one period to the next or one company to another.

Context matters more than the raw figure. A five-year-old software company and a century-old manufacturer will post wildly different RPE values even if both run efficient operations, because business model and lifecycle stage drive most of the variation.

Watch for a few common misreads:

  • A round of layoffs can spike RPE temporarily because the denominator shrinks faster than revenue, not because remaining staff became more productive.
  • Heavy reliance on contractors instead of employees can inflate RPE artificially, since contractor costs rarely appear in the headcount denominator.
  • Comparing RPE across industries without adjusting for capital intensity or business model produces conclusions that don't hold up.

Used carefully, within a single industry and tracked over consistent periods, RPE gives you an early signal on whether growth is outpacing headcount or the reverse.

How to calculate revenue per employee: formula and worked example

The core formula is simple:

RPE = Total Revenue ÷ Average Number of Employees

The denominator is where most of the judgment calls happen. Wall Street Prep's guidance recommends averaging beginning and ending headcount for the period rather than using a single point-in-time count, since that smooths out seasonal hiring swings and makes year-over-year comparisons more reliable.

Follow these steps to calculate it for your own organization:

  1. Pull total revenue for a full fiscal year or trailing twelve months, matched to the same period as your headcount data.
  2. Gather beginning and ending headcount for that period, counting full-time employees and converting part-timers to full-time equivalents.
  3. Average the beginning and ending counts: (beginning headcount + ending headcount) ÷ 2.
  4. Divide total revenue by that average headcount figure.
  5. Document which revenue line and which headcount definition you used, so next year's calculation stays consistent.

Here's a worked example. Say a company reports $12,000,000 in annual revenue, with 48 employees at the start of the year and 52 at the end. The average headcount is (48 + 52) ÷ 2 = 50. Dividing $12,000,000 by 50 gives an RPE of $240,000.

That $240,000 figure only becomes meaningful when set against a peer benchmark, such as the sector averages in the NYU Stern dataset, which shows broad cross-industry revenue per employee figures averaging around $111,028, with wide variation by sector.

What data you need and how to clean it before calculating

A defensible RPE calculation starts with clear rules on what counts as revenue and who counts as an employee, applied the same way every period.

On the revenue side, decide upfront whether you're using consolidated revenue (including subsidiaries) or operating revenue from a single business unit, and make sure the period matches your headcount snapshot exactly. Mixing a calendar-year revenue figure with a fiscal-year headcount count distorts the ratio without you noticing.

On the headcount side, you'll need rules for:

  • Part-time and seasonal workers, typically converted to full-time equivalents rather than counted as whole employees.
  • Contractors and freelancers, generally excluded from headcount since their cost structure differs from payroll employees.
  • Mid-year acquisitions or divestitures, which can distort both revenue and headcount if not adjusted to reflect only the period both entities were under common ownership.

One-off revenue events, like a large asset sale or a one-time grant, should be flagged and either excluded or footnoted, since they inflate RPE without reflecting ongoing operating performance. Payroll timing mismatches, such as counting employees who started after the revenue period closed, create similar distortions.

Pro Tip: Keep a one-page calculation log each year noting your revenue source, headcount method, and any adjustments, so comparisons five years from now still mean the same thing they mean today.

Revenue per employee benchmarks by industry

RPE varies enormously by sector, which is why a single average figure is nearly useless on its own. The NYU Stern employee metrics table remains the most widely cited source for building industry-specific peer cohorts, and it shows an aggregate figure near $111,028 across the full dataset, with individual sectors landing far above or below that line.

Several patterns show up consistently in benchmark data and industry commentary:

  • Software and technology firms tend to post some of the highest RPE figures in the economy, since code and platforms scale revenue without proportional headcount growth.
  • Capital-heavy, asset-management structures like certain real estate investment trusts can report extremely high RPE because a small team manages large portfolios of assets, a pattern highlighted in industry rankings of top RPE companies.
  • Labor-intensive sectors such as healthcare, retail, and hospitality typically post much lower RPE, since service delivery requires proportionally more staff per dollar of revenue.
  • Manufacturing sits in a middle range that depends heavily on automation levels and whether the business is assembly-driven or capital-equipment-driven.
  • Financial services vary widely depending on whether the firm is a high-volume retail bank or a lean asset-management shop.

The gap between software and hospitality isn't a productivity gap in the everyday sense. It reflects how much revenue each business model can generate without adding headcount, which is a structural feature of the industry rather than a management choice.

When you interpret your own number, two comparisons matter more than the absolute figure: how your RPE trend moves year over year within your own company, and how you stack up against a peer cohort built from the same sector table, not the economy-wide average. A software company comparing itself to the $111,028 aggregate will almost always look artificially strong, while a hospital comparing itself to that same number will look artificially weak.

How finance and HR teams use RPE in planning and reporting

RPE earns its place in a reporting pack when it's paired with context, not presented as a standalone score.

Finance and HR teams typically use it in a few recurring ways:

  • Headcount planning: modeling how many new hires a revenue target can support while holding RPE roughly flat, which helps set hiring budgets before the fiscal year starts.
  • Scenario modeling: testing what RPE looks like under different growth and attrition assumptions, useful when deciding whether to backfill a departing role or redistribute the work.
  • Dashboard reporting: showing RPE trend lines alongside complementary metrics like profit per employee and revenue growth rate, so a reader sees efficiency and profitability together rather than one number in isolation.
  • Investor and board narratives: using RPE as a quick proxy for operating leverage, especially in growth-stage companies where headcount is a major cost driver.

The caveat that matters most in investor conversations is that RPE can be gamed. APQC's research on productivity measurement notes that layoffs and staffing changes can push RPE up without any real gain in productivity, since the denominator shrinks while revenue holds steady in the short term. A board or investor relying on RPE alone after a restructuring announcement should ask whether the improvement reflects genuine output per worker or simply fewer workers.

The fix is to never present RPE as a solo metric in a diligence narrative. Pairing it with profit per employee and a short explanation of any headcount changes during the period gives a reader the full picture instead of a number that looks better than the underlying operation actually is.

Practical ways to improve revenue per employee

Raising RPE responsibly means growing revenue faster than headcount, not simply cutting headcount faster than revenue falls. A few levers tend to produce durable gains rather than a one-time spike:

  1. Optimize pricing and packaging so existing staff capacity generates more revenue per transaction, which is often the fastest lever available without adding a single hire.
  2. Build cross-sell and upsell motions into existing customer relationships, since expanding wallet share from current accounts rarely requires proportional headcount growth.
  3. Automate repetitive steps in the sales and fulfillment flow, from lead qualification to invoicing, freeing staff time for higher-value work instead of manual tasks.
  4. Redesign roles around billable or revenue-generating activity, shifting administrative work to shared services or software so client-facing staff spend more hours on work that drives revenue.
  5. Upskill existing teams so they can handle more complex, higher-margin work without adding headcount, which raises both RPE and the skill ceiling of the organization.
  6. Outsource non-core functions like bookkeeping, payroll processing, or compliance filings to specialized HR consulting providers, keeping internal headcount focused on revenue-generating roles.

Structural changes carry more risk and more upside than tactical ones. Engaging a fractional CFO to model different headcount and revenue scenarios before you commit to a reorganization helps you see which lever actually moves the number, rather than guessing based on what worked at a different company.

Pro Tip: Test one lever at a time for a full quarter before layering on the next one, so you can attribute the RPE change to a specific decision instead of a mix of overlapping changes.

How a fractional CFO audits and acts on revenue per employee

A structured audit typically starts with Efficiency & Cost Analysis to establish a clean baseline RPE figure, followed by an Operational Efficiency Audit that maps where headcount time actually goes versus where it generates revenue.

Employee time split by revenue contribution

From there, the diagnostic usually separates short-term fixes, like reassigning administrative work or renegotiating a vendor contract, from medium-term structural moves, like role redesign or a pricing overhaul. A fractional CFO engagement then models each option against your specific revenue and cost structure before you commit resources to any single change.

If your RPE number has been flat or declining and you want a clear read on which lever to pull first, a structured audit is the logical next step.

When revenue per employee is the right metric to prioritize

RPE earns its keep as a quick efficiency signal, especially for comparing headcount scaling within a single industry. But revenue without cost context can mask a business that's growing top line while margins erode underneath it.

When profitability is the real question, profit per employee or contribution margin per employee tells you more than RPE ever will. Use RPE to spot trends worth investigating, then confirm the story with a profitability metric before acting on it.

— Angelica

How AmCFO helps you measure and improve revenue per employee

We build RPE analysis into our Efficiency & Cost Analysis and fractional CFO engagements, pairing your efficiency numbers with forecasting and a plan you can act on within a quarter, not a year.

Amcfo

If flat or falling RPE has you questioning headcount decisions, our fractional CFO services give you a structured audit and a modular engagement scoped to what your business actually needs. Request an audit and get a clear read on where your efficiency stands before your next hiring decision.

FAQ

What is a good revenue per employee ratio?

A "good" ratio depends entirely on your industry: software firms often post RPE figures far above the broad cross-industry aggregate of roughly $111,028, while labor-intensive sectors like healthcare and retail sit well below it. Compare your number against peers in your own sector rather than the economy-wide average.

How do you calculate revenue per employee?

Divide total revenue for a period by your average headcount for that same period, typically calculated as (beginning headcount plus ending headcount) divided by two, as recommended in Wall Street Prep's calculation guide. Match the revenue period and headcount period exactly to avoid distorting the result.

What is the meaning of revenue per employee?

Revenue per employee measures how much revenue your organization generates for each employee on staff, and it works best as a comparison tool within a single industry rather than a standalone score. A rising trend can signal improving efficiency, but it should be checked against headcount changes before drawing conclusions.

What company has the most revenue per employee?

Rankings of top RPE performers tend to highlight specialized investment structures and real estate investment trusts, where a small team manages large pools of assets, as noted in industry rankings of RPE leaders. These extreme figures reflect asset-heavy, labor-light business models rather than a universal standard of productivity.

Sources