ARR Per Employee Calculator
Calculate annual recurring revenue per employee to benchmark software business efficiency, and model how hiring plans affect the ratio.
💹 SaaS Metrics📐 ARR per employee = annual recurring revenue / full-time equivalent headcount💼 Business
Annual recurring revenue
Full-time equivalent headcount
Planned hires this year
Expected ARR growth (%)
Prior year ARR per employee (optional)
Please enter valid values.
Formula & Reference
| Variable | Symbol | Formula | Units |
|---|---|---|---|
| ARR Per Employee Calculator | — | ARR per employee = annual recurring revenue / full-time equivalent headcount | currency per FTE |
Step-by-Step Examples
Example 1
Efficient Scale-Up
ARR 9,600,000, 62 FTE, 18 hires planned, 45% ARR growth, prior year 138,000.
- ARR per employee = 9,600,000 / 62 = 154,839
- After hires: 80 FTE, ARR 13,920,000
- New ratio = 174,000 — improving
- To hold 154,839 at 80 FTE would need 12,387,120 ARR
- Up 12.2% on prior year
✓ 154,839 — improving to 174,000
Example 2
Hiring Ahead of Revenue
ARR 4,000,000, 40 FTE, 20 hires, 20% growth.
- Current ratio = 100,000
- After: 60 FTE, ARR 4,800,000
- New ratio = 80,000 — declining 20%
- Headcount growing 50% against 20% revenue growth
✓ Declines from 100,000 to 80,000
Example 3
Highly Efficient
ARR 18,000,000, 55 FTE.
- ARR per employee = 327,273
- Well above 250,000 — characteristic of product-led models with low touch sales
✓ 327,273 — highly efficient
Real-World Applications
Efficiency Benchmark
ARR per employee is the standard efficiency comparison across software businesses of different sizes.
Hiring Discipline
Modelling the ratio after planned hires shows whether the headcount plan is supported by the revenue plan.
Investor Diligence
It is a routine diligence metric, since it indicates whether growth is being bought with headcount or generated by leverage.
Product-Led Signal
Very high ratios usually indicate product-led growth with low-touch sales and support motions.
Common Mistakes to Avoid
⚠️
Comparing across business models
Enterprise software with high-touch sales naturally shows lower ARR per employee than self-serve product-led businesses. The comparison only works within a model.
⚠️
Expecting the ratio to rise monotonically
Hiring ahead of revenue temporarily depresses the ratio, which is normal and often correct during a growth phase.
⚠️
Excluding contractors from headcount
Heavy contractor use inflates the ratio artificially. FTE should include all labour regardless of engagement type.
Frequently Asked Questions
What is a good ARR per employee? ▾
Commonly 100,000 to 200,000 for growing software businesses, with highly efficient product-led companies exceeding 250,000 or more.
Why does the ratio matter? ▾
It indicates whether revenue growth comes from operating leverage or simply from adding people, which determines long-term margin potential.
Should contractors be included in headcount? ▾
Yes, as full-time equivalents. Excluding them makes outsourcing look like efficiency and distorts comparison.
Is a declining ratio always bad? ▾
No. Hiring ahead of revenue is normal during expansion. It becomes concerning when the ratio declines persistently across several periods.
How does it differ from revenue per employee? ▾
ARR per employee counts only recurring revenue, excluding services and one-off revenue, making it a cleaner efficiency measure for subscription businesses.