Revenue per employee calculator

A growing company reports $12.6 million of revenue, $0.6 million of which is resold hardware, and grew from 44 to 62 full-time employees during the year. Revenue over year-end headcount is $203,226. Net revenue over average full-time headcount is $226,772. Net revenue over average FTE, counting part-timers and contractors, is $193,809. Same company, same year, and a 17% spread depending on how you divide.

The calculator shows revenue per employee on four denominators, then goes past the average: profit and labor cost per FTE, the change on last year, the revenue that each added FTE actually brought in, and the revenue a new hire has to earn to pay for themselves.

Who reaches for this

You enter gross revenue and any pass-through revenue to exclude, the number of full-time employees at the end of each month, part-time employees and their hours, and contractor FTE. The calculator computes net revenue and average FTE, then revenue per employee on four denominators so you can see how much the choice matters. It also calculates profit per FTE, labor cost per FTE and revenue per dollar of labor.

Three further outputs are about decisions and not about description. The change on last year and the marginal revenue per added FTE say whether growth is coming with rising productivity. The hire test says what revenue a new role must bring in. And the headcount needed for a revenue target says what the plan implies at today’s productivity. The true cost of an employee calculator supplies the fully loaded cost that goes into the hire test.

Revenue per employee is net revenue divided by average headcount. It appears under other names: revenue per FTE, sales per employee, revenue per head, the employee productivity ratio and revenue-employee ratio. They are the same idea. The differences are in the definitions of the two inputs, and those differences matter more than the label.

RPE is a company-level measure. It says how much revenue the business generates for each person on staff, and it is shaped by the business model, pricing, capital intensity and growth stage. A software business with high margins and few people, a distributor with large revenue and a thin margin, and a consultancy whose product is people hours will have very different figures, and none is wrong. RPE is not a measure of an individual’s output, and it should not be used to rate one.

The denominator is where most of the variation comes from. Take the running example: $12.6 million of gross revenue, $0.6 million of pass-through revenue, full-time headcount rising from 44 in January to 62 in December, 10 part-time employees working 20 hours a week, and 4 FTE of contractors.

The range is $33,223, or 17% of the lowest figure. The last row is the one to use: it counts everyone who did the work, for the length of time they did it. The first row is what many dashboards show, and it is the least accurate, because it mixes gross revenue with a single date.

Average, not year-end

Revenue is earned across the year by whoever was on the team at the time. A company that grew from 44 to 62 people had 52.9 full-time employees on average, not 62, so dividing by 62 makes it look less productive than it was. The reverse holds for a shrinking company. If the same headcount path ran backward, from 62 to 44, year-end RPE would be $272,727 against $226,772 on the average, and the company would look better than it was. Averaging the monthly headcount fixes both.

Part-timers, contractors and acquisitions

Part-time employees count as fractions: ten people working 20 hours against a 40-hour week are 5 FTE. Contractors are a judgment call. If a contractor fills a role you would otherwise hire for, and you depend on their output, the role is in the workforce that produced the revenue, and it belongs in the denominator. A one-off specialist on a single project usually does not. In the example, adding 5 part-time FTE and 4 contractor FTE takes $33,000 off RPE.

Acquisitions are the case where point-in-time headcount does the most harm. If a company buys another in October and reports year-end headcount, the new people are in the denominator for the whole year while their revenue is in the numerator for three months. RPE drops for reasons unrelated to productivity. Averaging monthly headcount weights the acquired people by the months they were part of the company, and revenue is weighted the same way. For a clean comparison, compute each company’s RPE on its own for the same period.

Seasonal and project businesses

A business with a strong season or a project pipeline can carry very different headcount in different months. Averaging twelve month-end counts handles most of that, but it treats a temporary summer team the same as a permanent one. If seasonal workers are a large share of the team, compute RPE both ways, with and without them, and state which you used. A landscaping firm that hires 40 people for four months has a very different RPE on year-end headcount than on average FTE, and only the average reflects the labor it used.

The numerator has its own choices. Use net revenue from the income statement, and remove items that pass through the business without being earned by its people: hardware or licenses resold at cost, re-billed travel and expenses, and payments collected on behalf of others. In the example, $0.6 million of resold hardware inflates revenue by 5% without any labor behind it. Gross revenue over average FTE would be $203,499. Net revenue over average FTE is $193,809.

Timing matters too. Use the same period for revenue and headcount, and use trailing twelve months for a rolling view. One-off revenue, such as a large non-recurring project or an asset sale, distorts the ratio in the year it lands, and it is worth reporting RPE with and without it. Businesses with recurring revenue may prefer annualized recurring revenue in place of reported revenue when growth is fast, and the choice should be stated.

Search for a benchmark and the answers conflict. One 2026 guide puts the average revenue per employee across U.S. sectors at $111,000. Another puts the 2024 cross-industry average at about $350,000. A third gives ranges: software and technology from $200,000 to $800,000 or more, professional services from $150,000 to $350,000, and manufacturing and retail from $80,000 to $200,000. All three may be reporting real data.

The gaps come from what is being averaged. Public companies have higher RPE than the economy at large, since they are larger and more capital-intensive. A mean is pulled up by a few very high-revenue firms, while a median is not. Some sources count all workers, and others count only full-time employees. Revenue may be gross or net. The year and the mix of industries in the sample vary. A single average across all of them is a statistic without a clear object.

How to benchmark instead

The workbook’s peer sheet does the arithmetic once you have the figures, and shows your ratio to the peer median. It leaves the choice of peers to you, since that is the judgment that decides whether the comparison means anything.

Revenue per employee measures the top line. Two others show what is underneath. Profit per employee is profit divided by average FTE, and it is the figure that says whether the revenue is worth having. In the example, profit is $1.32 million, an 11.0% margin, so profit per FTE is $21,319. Two companies at the same RPE with margins of 5% and 20% would earn $9,690 and $38,762 per FTE.

Labor cost per FTE and revenue per labor dollar connect the ratio to the payroll. With $6.9 million of fully loaded labor cost across 61.9 FTE, each FTE costs $111,440, and every dollar of labor produces $1.74 of revenue. Those two numbers show how much room the business has. Revenue per FTE of $193,809 against a labor cost of $111,440 means labor takes 57.5% of revenue, and the remaining 42.5% pays for everything else and leaves the 11.0% profit.

A rising RPE with a falling margin is a warning. If revenue per person rises because prices were cut to win volume, or because low-margin work was added, the ratio improves and the business does not. Track all three together: revenue per FTE, profit per FTE and labor cost as a share of revenue.

In an agency or a consultancy

For a business that sells people’s time, RPE has a direct structure: available hours per person, times the share of them that is billable, times the effective rate. A person with 1,800 available hours who bills 70% of them at an effective $150 an hour brings in $189,000. Raise utilization by five points and revenue per person rises by 5% × 1,800 × $150 = $13,500, or 7.1%. The same arithmetic shows the cost of a discounted rate or a slow month.

That makes utilization and rate the levers, and headcount the consequence. The agency break-even calculator shows the utilization a team needs to cover its costs, and profit per person is the figure that tells owners whether the RPE is worth the effort of producing it.

The average hides what recent hiring achieved. Marginal revenue per added FTE is the change in net revenue divided by the change in average FTE. In the example, last year’s net revenue was $9.6 million on 42 average FTE, a revenue per FTE of $228,571. This year it is $12.0 million on 61.9. Revenue rose by $2.4 million and average FTE by 19.9, so each added FTE came with $120,502 of revenue.

That is 47% below last year’s average, and it explains why the average fell 15.2%, from $228,571 to $193,809. Growth of 25% in revenue came with growth of 47% in average FTE. The company is adding revenue, but each hire is bringing less than the people already there, and the average will keep falling until either revenue catches up with headcount or hiring slows.

Read it carefully

Marginal revenue is noisy. Revenue lags hiring, because a new salesperson or engineer takes months to reach full productivity. A company that hired heavily in the last quarter of the year will show a poor marginal figure that reverses the next year. Look at two or three periods, and pair the number with what you know about when the hires started. A persistently low marginal figure, well below the average for several periods, is a sign that hiring is running ahead of demand.

Before a hire, ask what revenue they must bring in to pay for themselves. The answer depends on their fully loaded cost and on the margin on the revenue they generate: revenue needed = fully loaded cost ÷ gross margin. A hire costing $95,000 in salary, benefits, taxes and overhead, working on revenue with a 55% gross margin, must bring in $95,000 ÷ 0.55 = $172,727 of revenue a year.

Compare the requirement with what the company has been achieving. The $172,727 the $95,000 hire has to bring in is 1.43 times the $120,502 of revenue that recent hires added on average. It is also below the company average of $193,809, which suggests the role is reasonable at full productivity and hard to justify at the recent pace. The gap is worth understanding before the offer goes out: is the hire meant to serve existing demand, open a new market, or reduce someone else’s load?

Ramp time changes the first year. A hire who takes six months to reach full output brings perhaps half the revenue in year one, so the payback is longer than the annual figure suggests. The contribution margin calculator helps with the margin on a product or service, and the employee vs. contractor calculator compares hiring with contracting for the same work.

The same ratio works in reverse. To reach $18 million of net revenue at today’s $193,809 per FTE, the company needs 92.9 FTE, 31.0 more than the 61.9 it has. That is the headcount plan if nothing improves. If productivity rises by 10%, to $213,190 per FTE, the same target needs 84.4 FTE, 8.4 fewer. At $111,440 of labor cost per FTE, that is about $940,000 a year of payroll the plan does not need to fund.

Treat the result as a range and not a forecast. Productivity differs by role, and a plan that adds sales staff and support staff in proportion will not behave like one that adds only engineers. Use RPE for the shape of the plan, then build it up by function. It is useful as a sanity check: a plan that assumes RPE will jump 30% in a year needs an explanation.

For an early-stage company

Early-stage companies hire before revenue, so RPE starts low and rises as the product finds its market. A startup with $1.2 million of revenue and 14 people has $85,714 per person, and that says little on its own. What matters is the direction and the pace: whether revenue per person climbs as the team grows, and how it compares with the burn. The runway calculator and the burn multiple calculator measure the efficiency of that spend in ways RPE cannot, and investors usually read them together.

How often to review it

Quarterly is enough for most companies. Calculate it on trailing twelve months of revenue and average headcount so that the season does not distort the trend, and review the marginal figure over the last two or three periods. Any change in how headcount or revenue is defined should be noted, since a redefinition can move the ratio more than a year of real change.

Cutting headcount raises the ratio mechanically, and it is the wrong first move. If the people cut were producing revenue, revenue falls with them, and the ratio may not improve at all. The levers that raise RPE and the business together are these.

A caution about targets. When RPE becomes a target, people manage the number: headcount is moved to contractors who are not counted, revenue is pulled forward, and hiring is delayed past the point of useful. Two contractor FTE who produce no revenue are worth cutting: doing so takes RPE from $193,809 to $200,278. But contractors who do produce revenue are worth more than the ratio gain. Use RPE as a diagnostic, and check any change against revenue, margin and customer results.

Work out what a hire really costs with the true cost of an employee calculator, or see how a people business breaks even with the agency break-even calculator.