Revenue Per Employee RPE
Revenue Per Employee (RPE) measures total annualized revenue divided by the total number of full-time equivalent employees. It is a benchmark for organizational productivity and operational efficiency. As companies scale, RPE should increase as revenue grows faster than headcount, demonstrating operating leverage in the business model.
RPE is a lagging indicator of efficiency; it should be evaluated alongside ARR per employee for SaaS businesses where ARR is the more stable revenue measure.
- Workday / BambooHRHeadcount data for RPE calculations
- NetSuiteRevenue data paired with headcount for RPE analysis
- MosaicRPE planning and scenario modeling during budget cycles
- LookerCustom RPE dashboards by department and time period
- Revenue growth rate relative to hiring pace
- Product automation reducing labor-intensive processes
- Sales productivity per rep (ACV per AE)
- Customer success efficiency (customers per CSM)
- Engineering efficiency (engineers per unit of product output)
Best-in-class SaaS companies target $200K–$400K ARR per employee; top-tier companies like Atlassian have historically exceeded $600K per employee.
How different roles think about this metric
Each function reads RPE through a different lens and takes different actions when it changes.
Common Questions About Revenue Per Employee
Click any question to expand the answer.
What is a good revenue per employee benchmark for SaaS?
How does RPE differ between business models?
Should contractors be included in the RPE denominator?
How can a company improve RPE without reducing headcount?
Related Metrics
Metrics that are commonly analyzed alongside RPE.
Role guides that include this metric
See how each role uses RPE in context with the full set of metrics they own.
See What’s Actually Moving Your RPE
askotter connects your data sources and applies causal analysis to tell you exactly why your metrics are changing, not just that they changed.
Book a demo