Revenue per employee
Revenue per employee is annual revenue (or ARR) divided by headcount. It shows how much revenue each person on your team supports.
Revenue per employee is a blunt but useful efficiency check. Divide your annual revenue by the number of people on the team and you see how much revenue each person supports. For software companies it matters because the main cost is people, so this ratio decides how much profit is possible.
How to calculate it
Example: your product has $900,000 in ARR and a team of six full-time equivalents, which includes two founders, two engineers, one support person and one part-time marketer counted as one full-time equivalent.
Count part-timers and contractors as fractions of a full-time person, and say which method you used. Here the part-timer counts as a whole position to keep the math plain (2 + 2 + 1 + 1 = 6).
What good looks like
SaaS Capital publishes an annual survey of private SaaS companies. Its 2026 report puts the median ARR per employee at $141,125, up from $129,724 the previous year. By size, the median is $109,644 at $1 to $3 million ARR. At $5 to $10 million ARR, equity-backed companies have a median of $152,295 versus $177,240 for bootstrapped ones.
The same report finds that bootstrapped companies have higher revenue per employee than equity-backed companies at every ARR level, since they spend less on sales, marketing and other functions. Equity-backed companies, in turn, tend to grow faster.
Why it matters
- It caps profit. If a fully loaded employee costs $100,000 and generates $110,000 of revenue, there is little left for hosting, marketing and profit.
- It rises with scale. Software costs little to serve, so revenue per head normally grows as you do.
- It supports hiring decisions. Before adding a person, check whether the ratio can survive them.
Limits
- Business models differ. A product with heavy support or services will look worse than a self-serve tool without being worse run.
- Outsourcing improves the ratio on paper without improving efficiency.
- It does not show growth. A tiny team at $150,000 per head and 0% growth is not necessarily better than a larger team that is growing quickly.
For small and bootstrapped SaaS
This is a metric many bootstrapped founders use as a guard rail. Staying lean keeps margins high and leaves you in control. Aim to compare yourself with companies at the same ARR band and funding type, using a source like the SaaS Capital survey, not the figures from public companies with thousands of staff. Pair it with operating margin and growth to see the whole picture.
How to use it in practice
Track it once a quarter, using current ARR and current headcount. Before you hire, ask what ARR the role should add and by when. A support hire who lets you keep customers and avoid churn may raise the ratio. A second marketer with no clear channel may lower it for a year. Remember that a falling ratio is not always bad, if you are deliberately investing ahead of revenue, but you should know it is happening and have a plan for when it recovers.