The broad U.S. market average is about $111,000 in revenue per employee (Vena Solutions, 2026) — and that single number hides almost everything that matters. A median B2B SaaS company turns roughly $141,125 of recurring revenue per full-time employee (SaaS Capital, 2026, 1,000+ private firms), while a restaurant can fall below $35,000 per head (Vena, 2026). Same metric, a 4x–10x spread. If you want to know whether your team is the right size, this is the number to read — and the benchmark depends entirely on what business you're in.
Revenue per employee (RPE) is the quiet diagnostic behind every "should I hire?" decision. You take total revenue and divide by headcount. The result tells you how much output flows through each person on payroll. It won't tell you if you're profitable — margins live elsewhere (that's a separate benchmark) — but it tells you how efficiently your model converts labor into top-line. Below are the real ranges by industry, each with its source, and what each number actually means for the person reading it.
The Headline Number — And Why It Lies
Two credible figures circulate, and they disagree by 3x. The discrepancy is the first thing worth understanding.
- ~$111,000 — the broad U.S. all-sector average (Vena Solutions, 2026). This leans toward the full economy, including labor-heavy sectors.
- ~$350,000 — the 2024 cross-industry average reported by HRBench. This skews toward larger, public, capital-intensive companies.
Neither is "wrong." They're different samples. The public-company world (fewer people, more automation, more capital) sits far above the full economy of restaurants, clinics, and shops. The practical takeaway: never benchmark yourself against "the average." Benchmark against your industry, and then against your own trend over time. A number that's rising year over year matters more than any external figure — a point we make when we argue that small teams now outperform funded ones precisely because their RPE is structurally higher.
Revenue Per Employee by Industry (2026)
Here is the metric by sector, from highest to lowest, with the source behind each range. Note these are revenue (top-line) figures, not profit — a high-RPE business can still run thin margins, and a low-RPE business can be beautifully profitable.
| Industry | Revenue per employee | Source |
|---|---|---|
| Software / SaaS | ~$290,000 (rose 27% from $228K in 2023) | CompanySights, 2024 |
| B2B SaaS (recurring) | $141,125 ARR/FTE (median, private) | SaaS Capital, 2026 |
| Digital platforms / entertainment software | High end of the range (scalable models) | BizMiner, 2026 |
| Professional services / legal | Mid range (billable-hour driven) | StackNetwork, 2026 |
| Construction | Mid range (project revenue, lean back office) | StackNetwork, 2026 |
| Manufacturing | Mid range (capital-heavy, moderate headcount) | StackNetwork, 2026 |
| Healthcare / hospitals | Low–mid (high headcount relative to revenue) | Vena, 2026 |
| General retail | Low end (below ~$35K in some cases) | Vena, 2026 |
| Restaurants | Lowest tier (labor-intensive, <$35K) | Vena / BizMiner, 2026 |
Where a source publishes a firm dollar figure, we've used it. Where the published benchmark reports a positional range rather than a single number (StackNetwork's 8-vertical set, BizMiner's industry ranges), we've said so plainly rather than invent a precise digit. That honesty is the point: a benchmark is only useful if you know how firm it is.
Same container, vastly different fill — the same metric, read across industries.
The High End: Software and Scalable Models
Software sits at the top for a structural reason: once the product is built, each new customer costs almost nothing to serve. Headcount grows far slower than revenue. CompanySights measured the software industry average climbing 27% in a single year — from $228,000 (2023) to $290,000 (2024), a jump widely attributed to AI tooling letting the same teams ship more. Recurring-revenue SaaS is measured more conservatively on an ARR-per-FTE basis: $141,125 median for private B2B SaaS (SaaS Capital, 2026, up from $129,724), while The SaaS CFO's 2026 read puts median ARR per employee at $193,000, a 29% jump. The gap between those figures is sampling and definition, not contradiction — venture-backed and larger firms pull the average up.
If you run anything with software-like leverage — a product, a digital asset that sells while you sleep, a lean automated stack — your RPE should run high by design. A low number here is a signal you're carrying people the model doesn't require.
The Low End: Labor-Intensive Service
At the other pole, restaurants, general retail, and hospitals cluster low — sometimes under $35,000 per employee (Vena, 2026). The reason is simple arithmetic: these models need bodies on the floor to produce the revenue. A restaurant can't serve more tables by writing better code; it needs more servers. That's not inefficiency — it's the business model. A busy restaurant with $30K RPE can still be a far better business than a bloated software company at $150K.
The danger for low-RPE operators isn't the number itself; it's mistaking it for a profit problem and cutting the staff that produces the revenue. If you're in a people-heavy trade, the lever is rarely headcount — it's price and mix (the wrong number kills the business) and keeping the customers you already have (retention beats churn every time).
What a "Good" Number Actually Means
There is no universal target. A good RPE is one that beats your industry median and climbs over time. Three ways to read your own figure honestly:
- Against your industry, not the economy. $90K is excellent for a restaurant and alarming for a SaaS company. The all-sector $111,000 (Vena) is a conversation starter, not a target.
- Against your own trend. HRBench's own guidance is blunt: your internal trend matters more than any external figure. Rising RPE means your systems are scaling faster than your payroll — the whole promise of operating leverage.
- Alongside margin, never instead of it. RPE is top-line. Pair it with your margin and your break-even point before you draw any conclusion.
What This Means for You
If you're deciding whether to hire, RPE is the gut-check. Every new person should, over a reasonable ramp, keep your revenue-per-head at or above your industry median — otherwise you're buying capacity you can't fill. The disciplined move isn't "hire when busy"; it's hire when the revenue is already there to keep the ratio healthy. This is the operating discipline behind good decision frameworks and the reason a one-person operation can out-earn a staffed competitor: fewer people, higher leverage, and a number that only has to feed one household.
For founders eyeing a raise or a sale, RPE is also how outsiders judge you. Investors and acquirers read it as a proxy for how well your model scales — a high, rising figure signals you've built a machine, not a job. If you're raising your first round or benchmarking against who survives in your industry, this one ratio tells a sharper story than revenue alone.
The number isn't a verdict on your worth — it's a map of your model. Read it against the right peers, watch its slope, and let it tell you the one thing it's good at telling: whether the next hire makes the machine stronger, or just heavier. For a sharper view of the operating discipline that separates efficient companies from bloated ones, the minds who built enduring businesses all learned the same lesson — leverage per person compounds.
Revenue per employee is really a question about who's on the bus and what they're building. Collins' research on disciplined people and the flywheel is the clearest case for why fewer, better-leveraged hands beat a crowded payroll.
View on Amazon
