Definition · Workforce planning and analytics
Revenue per Employee
Definition
Revenue per employee is a company's total revenue for a period divided by its average number of employees, usually measured as full-time equivalents. It is a simple workforce productivity ratio that shows how much revenue each person generates, useful for tracking efficiency over time and comparing with close peers in the same industry.
Also called: Revenue per head, Revenue per FTE, Sales per employee, Workforce productivity ratio
Formula
Revenue per employee = Total revenue for the period ÷ Average number of employees (FTE) in the period
- Total revenue
- Revenue for the period, normally the last 12 months, from the income statement.
- Average FTE
- Average full-time equivalent headcount over the same period. Convert part-time employees to FTE, and decide consistently whether to include contractors and agency workers.
Worked example
A specialty distributor reports $240 million in revenue for the year. It had 1,050 employees at the start and 1,150 at the end, including 200 part-timers working an average of 20 hours a week (100 FTE). Average FTE is about 1,000. Revenue per employee = $240,000,000 ÷ 1,000 = $240,000. If it also uses 150 FTE of agency labor, revenue per total workforce FTE is $240,000,000 ÷ 1,150 = about $209,000.
What it tells you
Revenue per employee is a high-level efficiency signal. If it rises over time, the business is generating more revenue for each person, through growth, pricing, automation or better processes. If it falls, headcount is growing faster than revenue, which can be fine during an investment phase but needs explaining.
It is popular with executives and investors because it is easy to calculate from public filings. For HR and workforce planning, it is a useful headline, but only a starting point: it tells you nothing about profit, pay levels or where in the organization productivity sits.
Why use FTE, not headcount
Headcount treats a 15-hour-a-week part-timer the same as a full-time employee. In retail, hospitality, healthcare and contact centers, where part-time work is common, that distorts the ratio badly. Using full-time equivalents fixes it. Decide also how to treat contingent labor. A company that outsources its whole customer service operation will look far more productive per employee than one that runs it in-house, even if the total cost is the same. For internal comparisons over time, the most honest measure counts employees and contingent workers together.
Benchmarks and comparisons
Revenue per employee varies enormously by industry and business model. Software and financial companies often generate several hundred thousand dollars or more per employee; restaurants, retailers and labor-intensive services generate far less, because the work itself needs many people. Comparing a staffing firm with a software company tells you nothing.
Compare only with close peers (same industry, similar size and business model), and focus on your own trend over several years. A change in mix, such as acquiring a lower-margin services business, can move the ratio without any change in efficiency.
Revenue per employee vs related metrics
- Profit per employee shows whether the revenue produced is actually profitable. A business can raise revenue per employee by growing low-margin sales.
- [Labor cost](/glossary/labor-cost/) as a percentage of revenue shows how much of each revenue dollar goes to people. It is often more actionable for HR, because it links pay and staffing decisions directly to the ratio.
- [Human capital ROI](/glossary/human-capital-roi/) compares profit generated against what the company spends on its people.
- Output per labor hour (units per hour, calls per hour) is the operational version and is far more useful for frontline planning.
A good executive workforce dashboard pairs revenue per employee with labor cost percentage and one operational productivity measure.
How HR and workforce planners use it
- [Headcount planning](/glossary/headcount-planning/). If the plan targets 15 percent revenue growth and 5 percent productivity improvement, headcount should grow about 9.5 percent (1.15 / 1.05 = 1.095). Plans that grow headcount in line with revenue assume no productivity gain at all.
- Evaluating automation. Self-service or AI that absorbs volume should show up as rising revenue per employee in the affected function.
- Explaining investment. Hiring ahead of growth temporarily lowers the ratio. Saying so in advance avoids alarm later.
Use it at company or business unit level. Applying it to individual teams, especially support functions with no revenue of their own, produces numbers that mean little.
Common mistakes
- Using year-end headcount rather than average FTE.
- Ignoring contractors and outsourcing, so the ratio improves just by moving work off payroll.
- Comparing across industries or business models.
- Treating a rising ratio as success when it came from cutting staff that customers notice.
Frequently asked questions
What is the revenue per employee formula?
Revenue per employee equals total revenue for a period divided by the average number of employees, ideally full-time equivalents, over the same period. Most companies use the last 12 months of revenue.
What is a good revenue per employee?
There is no universal good number. It depends heavily on industry and business model. Compare with close peers and, more importantly, with your own trend over time.
Is revenue per employee a measure of workforce productivity?
It is a broad, top-level measure of workforce productivity. For operational decisions, pair it with labor cost as a share of revenue and with output measures such as units or contacts per labor hour.
Should contractors be included in revenue per employee?
For public reporting, most companies use employees only. For internal analysis, include contractors and outsourced FTE as well, or the ratio will improve simply by moving work off payroll.