Revenue Per Employee Calculator
Headcount is the easiest number to grow and the hardest to shrink. Revenue per employee keeps it honest — enter your revenue and your team size to see how much leverage each person actually carries.
Revenue per employee = total revenue ÷ full-time-equivalent (FTE) headcount. It measures how much revenue each person generates, which is a fast proxy for how much leverage your model has. For software, $200K–$400K per employee is a common-to-strong range and above $400K is elite; below $150K usually signals over-hiring, early stage, or a services-heavy model. Compare only within your industry — the benchmark that means ‘elite’ for software means ‘normal’ for high-frequency trading and ‘impossible’ for consulting.
Revenue Per Employee Calculator inputs and result
| Range | What it means |
|---|
How to use this calculator
- Use consistent revenue and headcountMatch the periods: full-year revenue against average full-year headcount. Comparing this year’s revenue to today’s larger team understates productivity.
- Count full-time equivalentsConvert part-time and contractor effort to FTEs — two half-time people are one FTE. Raw headcount overstates your team and distorts the ratio.
- Read against your industryThe bands here are framed for software. Capital-light, high-leverage models run far higher; services and labor-heavy businesses run lower. Only compare like with like.
- Track the trend, not just the levelA rising figure as you scale means revenue is outpacing hiring — the sign of real leverage. A falling figure means headcount is growing faster than revenue.
- Export your numbersCopy a share link, download the CSV, or print a one-page PDF for the planning or board conversation.
RGM Expert Says
Revenue per employee is the metric founders quote when it flatters them and forget when it does not. We bring it into planning because it is the cleanest counterweight to the instinct that every problem is solved by another hire. When a leadership team wants to double the team to chase a revenue target, this ratio asks the uncomfortable question first: is the revenue per head you already have actually being earned?
The number only means something within an industry. A capital-light software business and a field-services company can both be excellent and sit thousands of dollars apart per employee — the model, not the management, sets the floor. So we never let a client benchmark against a press headline from a different category. We pull the comparable set for their model and read the trend inside it.
What we care about most is direction. A revenue-per-employee figure that climbs as you scale is the fingerprint of genuine leverage — pricing power, automation, product-led motions where revenue grows faster than the org chart. A figure that sags as you add people is an early warning that hiring has gotten ahead of the business, usually a quarter or two before it shows up in burn.
How it works
Revenue per employee divides what the business earns by the number of people it takes to earn it.
- Total revenue — revenue for the period, matched to the headcount period.
- FTE headcount — full-time equivalents; convert part-time and contractor effort.
- Result — revenue generated per person; read the trend within your industry.
Benchmarks are industry-specific. Software and capital-light models run high; services, retail and labor-heavy models run far lower. Compare only within your category.
What revenue per employee really tells you
Revenue per employee is a leverage gauge. High and rising means the business earns more without proportionally adding people — through pricing, automation, or a product that sells and serves itself. Low and falling means the org chart is outgrowing the revenue, which eventually shows up as margin pressure and a harder fundraise.
It is also a discipline against the default reflex to hire. Every leadership team feels under-resourced; few ask whether the people already there are fully productive. Used in planning, this ratio forces that question before a headcount request gets approved — and pairs naturally with a hiring plan built from capacity, not vibes.
The caveat is that it is blunt. It says nothing about which roles drive the leverage, and it can be gamed by outsourcing core work to contractors who vanish from the headcount. Read it alongside gross margin and capital efficiency, and treat a sudden jump with the same suspicion as a sudden drop.
One more habit worth keeping: segment the number before you act on it. A blended company-wide figure hides whether the leverage lives in engineering, sales, or support, and an average can look healthy while one function quietly carries far too many people for the revenue it touches. Break revenue per employee out by team, compare each against how that function behaves in efficient peers, and you turn a single headline into an actual decision about where the next hire should — or should not — go. That is the difference between a metric you report and a metric you run the business with.
Revenue per employee by model
Benchmarks vary enormously by industry. These are rough orientation ranges, not targets — the model sets the floor far more than management does.
| Model | Typical range | Note |
|---|---|---|
| Early-stage software | Under $150K | Investing ahead of revenue |
| Growing SaaS | $150K to $300K | Scaling toward leverage |
| Mature, efficient SaaS | $300K to $500K | Strong product and pricing leverage |
| Capital-light / PLG leaders | $500K+ | Revenue compounds faster than headcount |
What operators say about productivity
The best companies grow revenue far faster than headcount; leverage, not bodies, is what separates an efficient business from a busy one.
Durable companies build distribution and product leverage so that each new dollar of revenue does not require a new person to earn it.