ARR per employee is the cleanest one-number read on how efficiently your team turns headcount into revenue. See where you sit against SaaS norms, your revenue-to-payroll ratio, and how much room you have to hire before efficiency slips.
Annual recurring revenue.
Full-time-equivalent employees.
Salary, benefits, overhead per FTE per year.
Your ARR per employee at different team sizes, holding ARR and cost per employee fixed. See how each hire moves the efficiency number before you make it.
| Headcount | ARR per employee | Revenue-to-payroll | Tier |
|---|
team ahead of revenue, normal
the efficiency band to aim for
elite, efficient public SaaS
ARR per employee strips away accounting noise and asks a simple question: how much recurring revenue does each person on the team support? No add-backs, no adjustments, just revenue over people.
It is a favourite investor read because it is hard to game. You cannot reclassify your way to a better number - it is the revenue you actually book against the people you actually pay. That is why a board will reach for it before almost anything else, often alongside the broader revenue per employee figure.
ARR per employee = ARR / FTEs Example: $5,000,000 of ARR across 40 FTEs:
In a tighter funding market, capital efficiency carries real weight. A healthy ARR per employee signals you can grow without burning through cash, which is exactly what a board wants to see before they back the next round of hiring.
Read it next to your burn multiple and Rule of 40. Efficiency that comes with controlled burn - ideally a path to free cash flow - is the combination that earns a premium. One number alone tells half the story; together they tell a board whether the growth is paying for itself.
Roughly $150-250k is a healthy scaling range, with the most efficient public SaaS above $250k. Early-stage companies often sit nearer $100k while the team is ahead of revenue, which is normal when you are hiring to build before the revenue catches up. Read the number alongside your growth rate rather than in isolation.
Annual recurring revenue divided by full-time-equivalent headcount. If you run $5,000,000 of ARR across 40 FTEs, that is $125,000 per employee. See ARR for how to count recurring revenue cleanly.
Count them as full-time equivalents so the ratio reflects the real cost of delivering the revenue. Two half-time contractors count as one FTE. Leaving contractors out flatters the number and hides the true headcount behind the revenue, which defeats the point of the metric.
It is a clean, hard-to-game read on capital efficiency, showing how much revenue each hire supports without the noise of accounting choices. In a tighter funding market it carries real weight because it signals whether a company can grow without burning through cash on headcount.
Fast growth justifies a temporarily lower ratio because you hire ahead of revenue. A team that doubled headcount this year to support next year's revenue will look inefficient on a snapshot and efficient a year later. Judge it alongside your growth rate and burn, not in isolation.
ARR per employee uses recurring revenue only, so it is the cleaner read for subscription businesses where one-off revenue would distort the picture. Revenue per employee folds in services, setup fees and other non-recurring income, which can flatter or muddy the underlying efficiency of the subscription engine.
Yes. The old rule of thumb was roughly $200k as 'good', but AI-native and lean teams have pushed the bar up: $300k per employee is increasingly treated as the new 'good' and $500k as 'great', with the 90th percentile now near $700k per FTE. Traditional SaaS still clusters lower - median revenue per employee for private SaaS was around $130k in 2025 - so judge yourself against direct peers at your stage, not the AI-era outliers.
Two levers: grow recurring revenue per head, or hold headcount flatter. In practice that means raising price or expansion (most SaaS undercharge by 20-40%), leaning on product-led and self-serve so revenue grows without a bigger sales team, using AI and automation to do more with the same people, and delaying hires until a real bottleneck demands them. Improving the number is usually a monetisation and efficiency problem before it is a headcount one.
Strongly. Private SaaS at $1-3M ARR runs near $100k per employee, rising as the company scales - you should be around $175k near $20M ARR, and roughly $200k (median) past $50M ARR, with best-in-class clearing $350-400k. Bootstrapped companies tend to run more efficiently than equity-backed ones at the same size. A snapshot only makes sense next to your stage and growth rate.
ARR per employee is one read. Mowt pulls your real recurring revenue from Stripe and tracks it next to growth, churn and burn, updated daily - so you know whether each hire is making the team more efficient or less.
No credit card required · Connect Stripe in 1 click
No credit card required. Connect Stripe in 1 click.
We're building iOS and Android apps that'll bring your metrics everywhere.
Our mobile apps are currently in active development. Follow us on social media for updates and be the first to know when they launch.