ARR per Employee
Revenue divided by headcount — the one-line productivity test investors run on every SaaS company, and what counts as good.
What is it?
ARR per employee divides annual recurring revenue by total headcount. It is the bluntest efficiency metric in SaaS — one line, no adjustments — which is exactly why investors love it: it is nearly impossible to game and instantly comparable across companies.
It became a headline number in the efficiency era and has stayed one in the AI era, where the benchmark conversation shifted from 'how big is the team' to 'how much revenue can a small team carry'. Every story about a startup reaching $10M ARR with nine people is an ARR-per-employee story.
How to calculate?
Divide ARR by full-time headcount, contractors included if they are doing the work of employees. A $300,000 ARR business with a team of 12 runs at $25,000 per employee. Use period-end headcount for a snapshot, or average headcount when the team is growing fast enough for the choice to matter.
The trend carries more signal than the level: ARR per employee rising means revenue is compounding faster than headcount — operating leverage is appearing. Falling means each hire is buying less growth than the last one did.
What is a good ARR per employee?
At scale, $200,000–$300,000 per employee is solid for public SaaS, the best operators clear $400,000, and AI-lean companies have pushed past $1M. Early-stage numbers run far lower and that is fine — a seed-stage team at $25,000 per employee is normal, because the product is being built ahead of the revenue.
Judge the stage, then the trajectory. The number should roughly double between major stages: something like $50k at seed, $100–150k at Series A-B, $200k+ approaching scale. A company whose ARR per employee plateaus early is scaling headcount as fast as revenue — growth without leverage, which is the expensive kind.