Why revenue per employee is still the cleanest efficiency metric
Revenue per FTE (full-time-equivalent) is annual revenue divided by headcount. It's coarse — it doesn't tell you about margin, cash flow, or product quality — but within a peer set, it exposes operational efficiency faster than any other single number. A 10-person SaaS company at $2.5M ARR has $250K revenue per FTE; the same-size agency at $1.5M in fee revenue has $150K RPE. Both might be running well, but the SaaS business has 67% more operational leverage per head. That leverage compounds: the $250K RPE company can add a customer without adding a person for longer than the $150K RPE one.
The comparison tool extends RPE with growth rate, gross margin, and net margin — four dimensions investors and operators actually triangulate on. A company can lead on RPE but lag on growth (efficient but dying) or lead on growth but lag on margin (scaling on fumes). The radar chart exposes both patterns at a glance. The single-number efficiency score collapses the four axes into one comparable number with 35/25/25/15 weights on RPE / growth / net margin / gross margin. The weights are tuned for early-stage companies where growth trajectory matters as much as current margin — for mature businesses you'd weight margin heavier.
A worked example: three SaaS companies side by side
Take three real-shape SaaS companies at similar funding stages:
- Company A: $3.4M ARR, 14 FTEs, 28% YoY growth, 74% gross margin, 11% net margin. RPE = $243K. Efficiency score: 64.
- Company B: $1.8M ARR, 9 FTEs, 45% YoY growth, 68% gross margin, 5% net margin. RPE = $200K. Efficiency score: 60.
- Company C: $5.8M ARR, 22 FTEs, 18% YoY growth, 76% gross margin, 14% net margin. RPE = $264K. Efficiency score: 62.
All three cluster within 4 points of each other on the composite, but they tell very different operational stories. Company A is the balanced operator — decent growth, clean margin, solid revenue per head. Company B is the early-growth company burning profit for traction — if they hold 45% growth for another year they'll pass Company A on revenue. Company C is the mature operator — highest absolute revenue and margin, but growth has decelerated and is barely beating inflation. Looking at RPE alone ranks C > A > B. Looking at the full radar ranks them by what matters for your thesis: growth, efficiency, or scale.
Where RPE benchmarks break down
RPE is useful only when comparing like-to-like. A few traps:
- Consulting vs SaaS vs retail — never compare across these. SaaS peaks at $500K RPE; consulting caps at $300K–$400K because every hour is billable or not. Retail and restaurants cap at $150K because labor-to-revenue ratios are baked in.
- Contractor-heavy businesses — if one competitor uses 40% contractors and another uses 10%, their FTE-based RPE looks very different even if both have identical economic structure. Normalize by counting full-time contractors as 0.8 FTE.
- Revenue stage— a company that raised $50M last year and hired 40 people in 6 months will have terrible RPE for 12–18 months until revenue catches up. That's not inefficiency, it's deliberate investment.
- Hardware + software mix — a company selling hardware with attached software (Peloton, Ring) has inflated revenue numbers because hardware cost passes through to customers. Their RPE looks strong but gross margin reveals the real economics.
The three most common efficiency gaps
When a company scores 20+ points below peers, the gap almost always traces to one of three root causes.
Pricing discipline.The most common gap. A company charging $29/mo when peers charge $49–$99 will show low revenue per FTE forever. Diagnosis: compare your ACV or ARPU against peer midpoints. If you're 25%+ below, you have a pricing problem, not an efficiency problem. Fix: quarterly price reviews, grandfathered increases, and a strict rule that new customers pay new prices.
Operating expense creep.Second most common. Teams accumulate software subscriptions, contractors, agencies, and "just this one hire" across two or three years. Individually each decision is small; aggregated they push net margin 10–15 points below peer average. Diagnosis: total software spend per FTE (should be under $4K/yr for SMB SaaS, under $6K/yr for mid-market), total contractor spend as % of payroll (should be under 20% for mature companies), number of SaaS tools per FTE (under 12). Fix: annual audit of every recurring charge, kill ruthlessly.
Channel underinvestment.Shows up as a growth gap rather than margin gap. A company with strong unit economics but 18% growth while peers grow 30–45% is usually under-spending on acquisition. Diagnosis: marketing spend as % of revenue. Benchmarks: 8–12% for mature SaaS, 20–35% for growth-stage SaaS, 10–20% for D2C. Fix: pick one channel, commit a real budget for 90 days, measure CAC and payback. Don't spread a small budget across five channels.
How investors actually use these numbers
A typical investor diligence spreadsheet has 8–12 companies in the peer set, with RPE, growth, net margin, gross margin, and capital efficiency (ARR / total funding raised) as the columns. They sort on composite efficiency, then drill into the top and bottom outliers. Your goal as an operator is to be in the top quartile on at least one axis and median or better on the others. Being median on everything scores you nowhere; being elite on one axis earns you the conversation. Use the radar view in the tool above to see whether your profile has a standout axis — and if it doesn't, pick one to build toward over the next 2–3 quarters.
What to run after this comparison
If the comparison shows you trailing on revenue per FTE, use the pricing strategy planner to model a price increase. If you're trailing on net margin, use the profit margin calculator to find the opex bucket that's eating the difference. If you're trailing on growth, model MRR momentum with the MRR calculator and unit economics with CLV. The comparison tool identifies the gap; the operational calculators tell you how to close it.