b2KIT

Revenue / Profit Per Employee Calculator

Calculate revenue per employee and profit per employee metrics for organizational efficiency benchmarking and headcount planning.

Tested tool guide Tested browser tools Checked August 16, 2026

What Revenue / Profit Per Employee Calculator does, with a checked example

Revenue per employee and profit per employee are the two questions this answers: how much money does each person generate, and how much of it survives to the bottom line. Enter revenue, a profit figure, and headcount, and the tool divides each by headcount and reports both per-person numbers plus the implied profit margin. The surprise for most users: headcount must be the average number of full-time equivalents during the period, not the count on the last day, or a growing company looks half as productive as it is.

Worked example

A concrete input and expected output from the current implementation.

Input

Revenue: $12,000,000
Net income: $1,800,000
Average employees (FTE): 120

Expected output

Revenue per employee: $100,000
Profit per employee: $15,000
Implied net margin: 15%

Each metric divides its numerator by the same headcount: $12,000,000 / 120 = $100,000, and $1,800,000 / 120 = $15,000. The margin follows: $15,000 is 15% of $100,000, matching $1,800,000 / $12,000,000.

How the result is produced

1

Two divisions, one denominator

Both metrics share one formula shape: numerator divided by headcount. Revenue per employee divides total revenue by the employee count; profit per employee divides the profit figure by the same count. Because the denominators match, the two results are tied together: profit per employee equals revenue per employee multiplied by the profit margin, so the tool can also report margin.

2

The headcount is the load-bearing input

The tool treats headcount as one number, and that number decides everything. For a stable company, period-end headcount is fine; for one that grew or shrank during the year, the average FTE count is the fair denominator, with part-time staff prorated. Comparing your result to another company's only means something if both counts used the same definition.

Good uses

  • Checking whether your headcount is lean: run the ratio for each of your last three fiscal years and hold the result against published revenue-per-employee figures for your industry.
  • Headcount planning: before adding staff, estimate the revenue the new roles must produce to keep revenue per employee at or above its current level.
  • Due diligence on an acquisition target or a division turnaround, where per-employee output is the fastest summary of whether the workforce pays for itself.

Limits and checks

  • The ratios are industry-bound. Capital-intensive businesses such as refineries or telecoms show high revenue per employee because machines, not people, do the work; comparing them to a services company misreads the result.
  • Profit must be defined before you enter it. Net income, operating profit, and EBITDA give very different profit-per-employee figures; the tool computes what you type, so results computed with different profit bases are not comparable.
  • Headcount timing and scope. A period-end count on a growing company understates productivity; contractors and outsourced production raise revenue per employee because the people doing the work never enter the denominator.

Common questions

What is a good revenue per employee?

There is no universal number; the figure ranges from tens of thousands to millions of dollars per person depending on industry, and it reflects capital intensity as much as efficiency. Use the tool for your own number, then compare it with published figures for your industry and revenue size, and with your own previous years.

Should I enter net income or EBITDA as the profit figure?

Either works, but use the same definition every time you run it. Net income includes interest, taxes, and one-off items; EBITDA isolates operating results. If your profit per employee is compared with a figure computed on a different profit base, the gap may be definitional rather than a real difference in performance.

References and verification

The example and behavioral notes were checked against the browser implementation. Standards and primary references below define the relevant format, formula, or platform behavior.

Related Tools