Revenue per employee (RPE) is the core SaaS efficiency benchmark. Investors use it to assess how well a business scales with headcount. Operators use it to decide when to hire next.
Benchmarks by ARR range
| ARR range | Median RPE | Top quartile | Notes |
|---|---|---|---|
| < $1M | $80k–$150k | > $200k | Founding team + early hires |
| $1M–$5M | $150k–$250k | > $350k | Product-market fit stage |
| $5M–$20M | $200k–$350k | > $500k | Scaling GTM |
| $20M–$100M | $250k–$450k | > $600k | Efficient growth |
| $100M+ | $300k–$600k | > $800k | Mature, high-leverage |
Why PLG companies have higher RPE
Product-led growth companies acquire, activate, and expand customers through the product rather than through large sales teams. This compresses CAC and keeps headcount lean relative to revenue.
Atlassian famously grew to $100M ARR with under 1,000 employees — roughly $100k+ per employee at the time, which was exceptional pre-2015.
Modern PLG benchmarks (Figma, Notion, Canva) show $500k–$1M+ RPE is achievable at scale when the distribution motion is product-first.
What drives below-median RPE
Over-hiring ahead of revenue: Common at seed/pre-seed where founders build the team they think they'll need in 18 months. Creates negative operating leverage until revenue catches up.
High-touch sales model: Mid-market and enterprise sales require more headcount per dollar of revenue than self-serve. This is acceptable if ACV justifies it — but RPE alone doesn't tell the whole story.
Services-heavy model: Professional services, onboarding, and implementation are headcount-intensive with lower margin than pure software.
Calculate your RPE and compare to benchmarks with the free Revenue per Employee Calculator.