Net Revenue Per Employee
Net Revenue Per Employee divides your ARR by total headcount. It measures how efficiently your team generates revenue. A company with $5M ARR and 25 employees has $200K revenue per employee. It is increasingly used by investors as a proxy for operational efficiency.
Why Net Revenue Per Employee Matters for SaaS Companies
Revenue per employee reveals whether you are building a capital-efficient company or an over-staffed one. Post-2022, investors prioritize efficiency alongside growth. For Seed to Series B companies, this metric helps determine when to hire (and when not to). Adding headcount when revenue per employee is declining means each hire generates less return.
Formula
Revenue Per Employee = ARR / Total Full-Time Employees (include contractors as FTE equivalents)
Benchmark
Healthy SaaS: $150-300K per employee. Best-in-class: $300K+. Below $100K: likely over-staffed relative to revenue.
Tools for Measurement
An Operator's Take
I use revenue per employee as a hiring guardrail. If the metric is declining quarter over quarter, I ask: are we hiring ahead of revenue (intentional and time-bound) or are we over-staffed? At one company, revenue per employee dropped from $180K to $110K over 6 months because they hired aggressively for a growth target they missed. Instead of hiring more, we focused on getting more output from existing headcount through automation and process improvements. Revenue per employee recovered to $190K within two quarters without a single new hire.
Dealing with this at your company?
Get a free diagnostic — no pitch deck, just an honest assessment of where you stand.
Common Mistakes
What I see go wrong most often in the field.
Not counting contractors as FTE equivalents. If you have 20 full-time and 10 full-time-equivalent contractors, your real headcount is 30.
Comparing your metric to public company benchmarks without adjusting for stage. Early-stage companies naturally have lower revenue per employee because they are investing ahead of revenue.
Using revenue per employee as the sole hiring criterion. Some roles (engineering, product) are investments that take time to generate revenue impact.
What to Do This Week
Concrete steps you can take right now.
Calculate your current revenue per employee including contractor FTEs. Track it quarterly.
If declining for 2+ quarters, audit recent hires: is each role contributing to revenue generation, retention, or future capacity?
Before your next hire, model the impact on revenue per employee. Can you achieve the same outcome through automation or process improvement?
Related Resources
Try These Tools
Further Reading
Frequently Asked Questions
What is a good revenue per employee for SaaS?
For Seed-B companies, $150-200K per employee is healthy. Series C+ companies should target $200-300K+. Best-in-class public SaaS companies exceed $400K. These benchmarks vary by business model — PLG companies tend to have higher revenue per employee than sales-led companies due to lower headcount requirements.
Operations & Systems Consultant
16+ years leading operations and growth, including through a $2B exit and an IPO. I untangle the software and processes companies accumulate over time and rebuild them into systems teams can run.
Need Help With Pricing Strategy?
Most established companies are paying for operational debt they can't see. Let's figure out what it's costing you.
16+ years leading companies · Senior-level, not junior staff · Fixed-fee or embedded engagements