Revenue Per Employee for Startups: Formula, Examples and How to Use It

What revenue per employee means

Revenue per employee is a startup efficiency metric that divides annual revenue, or annual recurring revenue (ARR), by the number of full-time-equivalent people on the team. A company with $1.2 million of ARR and 12 people earns $100,000 per employee. It tells you how much revenue each person supports, which makes it one of the fastest ways to see whether headcount is keeping up with the business.

Why does it matter? Payroll is usually the largest cost in a software startup, so headcount drives your burn rate more than any other line. If you hire faster than revenue grows, the ratio falls and your runway shrinks. If revenue grows faster than the team, the ratio rises and every new dollar is cheaper to earn.

The formula and a worked example

The formula is simple: revenue per employee = annual revenue (or ARR) divided by full-time-equivalent headcount. Count founders, because they draw on the same time and cost. Count part-time people and regular contractors as fractions, for example ten full-time people plus four half-time contractors is 12 FTE.

Take a company with $3.0 million of ARR and 20 FTE. Revenue per employee is 3,000,000 divided by 20, which is $150,000. Now compare it with a second company at $1.2 million of ARR and 12 FTE, which sits at $100,000. The first team is converting people into revenue more efficiently, though it may also be at a later stage.

Repeat the calculation every quarter with the same definition. One measurement is a snapshot, but three in a row show a trend: whether the team is outgrowing revenue or revenue is outgrowing the team. Keeping the figure in your own dashboard also prepares you for investor questions about efficiency.

Why the ratio changes as you hire

Hiring changes both sides of the fraction. Suppose the $3.0 million company adds four people at a fully loaded cost of $90,000 each. That is $360,000 per year, or $30,000 more burn every month, before any of them has produced revenue.

To keep the same $150,000 per employee, 24 people need to support $3.6 million of ARR. The company therefore has to grow ARR by $600,000, or 20 percent, to justify the four hires. If it cannot see that growth coming, the hires lower the ratio and cut runway.

How to read the number without false benchmarks

It is tempting to ask what a good number is. The honest answer is that it depends on your model, stage and market, and public figures for startups are rarely audited. A B2B software company with a lean team will look very different from a service-heavy business or a company that sells to governments with long sales cycles.

Use the number against your own history and against companies that sell the way you do. A rising trend quarter over quarter is a better signal than any single comparison. A sudden drop usually means you hired ahead of revenue, which can be fine if you can name the revenue the hire is meant to unlock.

What revenue per employee does not tell you

The metric ignores profitability. A team can show high revenue per employee while selling at a loss, because the ratio says nothing about margin or customer acquisition cost. Pair it with gross margin, burn multiple and unit economics before drawing conclusions.

It is also lumpy at small sizes. With five people, one hire moves the ratio by 20 percent, so a single quarter means little. And it can reward the wrong behaviour: cutting support or engineering to lift the number can raise churn and damage the revenue you are trying to protect.

Common mistakes when measuring it

The first mistake is counting the wrong headcount. Leaving out founders or contractors makes the ratio look better than it is, while counting people who left mid-year makes it look worse. Use the average FTE over the period, or the current team against annualised current ARR, and say which one you chose.

The second is mixing revenue definitions. One-off project fees, usage spikes and services income do not recur, so putting them in ARR inflates the figure. See how ARR is counted before you compare quarters, and keep the definition fixed so the trend means something.

The third is comparing across very different companies. A marketplace, a hardware maker and a subscription tool earn revenue in different ways, so their ratios are not comparable. Compare like with like, and treat outside numbers as context, never as a target.

Using it as a hiring check

Before opening a role, write down the revenue or cost saving you expect the person to enable and by when. Divide the extra annual cost by your current revenue per employee to see how much new revenue the hire needs to break even on efficiency. In the example above, a $360,000 hiring plan needs $600,000 of ARR growth to hold the ratio.

Then check the cash side. Add the new monthly payroll to your burn and recompute runway. If the plan shortens runway below the point where you can finish your next raise or reach profit, stage the hires or tie them to revenue milestones.

Practise hiring trade-offs in Founder Runway

In Founder Runway you make founder decisions across 20 turns, with four options on every decision. Hiring, spending and growth choices all feed cash and runway, and the run ends as a failure, a promising company, EBITDA positive or high-value exit potential. Pick a B2B, B2C or B2G model and a starting stage from Pre-Seed to Series A.

The game does not display revenue per employee as a metric. It trains the judgement behind it: whether the people you add will earn their cost before your cash runs out.