The Metric That Tells You If You Are Overhired
Revenue per employee is the simplest efficiency metric in SaaS. It tells you how much revenue each person in your company is responsible for generating. It is not about making people work harder — it is about whether your headcount is proportional to your business.
Benchmarks
| Stage | Revenue/Employee | Context |
|---|---|---|
| Pre-Product-Market Fit | $50K-100K | Expected, still building |
| Growth Stage ($5-20M ARR) | $150K-250K | Should be improving |
| Scale Stage ($20-100M ARR) | $200K-350K | Efficiency matters |
| Public SaaS | $250K-500K+ | Best-in-class territory |
Why This Metric Matters for Marketing
Marketing teams are often the first to get cut when revenue per employee drops. If you can show that adding a marketer increased ARR by $300K, you are safe. If you cannot attribute revenue to marketing headcount, you are a cost center that gets trimmed. Track marketing-sourced pipeline per marketing employee to protect your team.
The AI Inflection Point
Revenue per employee is changing fast. AI tools are enabling 5-person teams to do what used to require 20. Companies that adopt AI early will see revenue per employee skyrocket while competitors stay flat. This metric is becoming the dividing line between efficient companies and legacy operators.
Common questions about Revenue Per Employee
What is a good revenue per employee for SaaS?
Best-in-class public SaaS companies achieve $300K-500K+ per employee. Growth-stage companies typically run $150K-250K. Early-stage startups under $5M ARR often fall below $100K. The number should increase as you scale — if it is declining, you are hiring faster than you are growing.
How do you calculate revenue per employee?
ARR divided by total full-time equivalent employees. Include contractors who work full-time equivalent hours. Exclude part-time freelancers. Some companies use revenue run rate instead of trailing twelve months — pick one and stay consistent.