One of the most common mistakes in SaaS is hiring too early. Revenue per employee gives you a data-driven guardrail: before you hire, calculate what RPE will look like after the hire.
The pre-hire RPE test
Before committing to any new hire, run this calculation:
Post-hire RPE = Current ARR ÷ (Current Headcount + 1)
At $4M ARR and 16 employees ($250k RPE current): - Post-hire RPE = $4M ÷ 17 = $235k/employee
That's a 6% efficiency decline. Whether that's acceptable depends on what revenue the hire enables.
Revenue required to maintain RPE after a hire
Revenue needed = Target RPE × (Current Headcount + 1)
To maintain $250k RPE after a 17th hire: - Revenue needed = $250k × 17 = $4.25M
If you're at $4M ARR and adding one person, you need to generate $250k more ARR to maintain efficiency. Is this hire expected to directly or indirectly generate that? If not, delay.
When it's OK to hire ahead of RPE
Hiring ahead of RPE is acceptable when: - The hire directly enables revenue (AE who will close deals, SDR who generates pipeline, CSM who drives expansion) - The hire removes a bottleneck that's actively blocking growth (engineering capacity preventing product releases) - You have 12+ months runway and are deliberately investing in growth
It's risky when: - You're hiring for operational comfort rather than growth enablement - RPE is already declining quarter over quarter - Runway is under 12 months
Use the Revenue per Employee Calculator before every hiring decision. It takes 60 seconds and makes the trade-off visible.