What revenue per employee actually measures
Revenue per employee (RPE) is annual revenue divided by full-time-equivalent headcount. It is a coarse but powerful efficiency metric. A 10-person SaaS company with $2M ARR has $200K RPE. The same size agency with $1.2M in fee revenue has $120K RPE. Neither number is good or bad in isolation — it has to be compared against industry norms — but within an industry, RPE is one of the cleanest benchmarks available.
RPE captures the scalability of your business model. High RPE means each person generates a lot of revenue — often a sign of automation, strong product-led growth, or high-margin pricing. Low RPE means the business is labor-intensive and each new dollar of revenue requires another person on payroll.
Industry benchmarks
- SaaS (at scale): $250K–$400K RPE. Best-in-class (Atlassian, Shopify peak) hits $500K+.
- Agency / professional services: $150K–$250K RPE.
- Ecommerce DTC: $300K–$500K RPE (revenue, not margin).
- Retail (brick and mortar): $150K–$250K RPE.
- Consulting (high-end): $250K–$400K RPE.
- Manufacturing: $250K–$450K RPE.
- Restaurants: $60K–$120K RPE. Labor-heavy by nature.
- Law firms: $200K–$400K RPE.
- Top tech companies (Apple, Meta): $1.5M–$2.5M RPE.
Compare yourself to the right industry, not to Apple. A $500K RPE SaaS business is best-in-class; a $500K RPE restaurant is impossible.
Why RPE is a growth-stage metric
RPE matters most for businesses with 5+ employees. Below that, one or two people can skew the number wildly. Above that, it becomes a meaningful signal of whether your headcount growth is matching revenue growth or outpacing it.
If revenue growth is 30% year over year but headcount grows 50%, your RPE is declining — the business is becoming less efficient over time. If headcount grows 15% and revenue grows 30%, RPE is expanding — you are building leverage. The second pattern is what good management looks like; the first is what burns investors' cash or eats owner distributions.
Where low RPE is a problem
- Over-hiring in support. Growing support team linearly with customer count means your product is not solving its own problems. Invest in self-service.
- Thick middle management. Adding managers faster than individual contributors raises cost without adding revenue capacity.
- Agency model on retainer. Low utilization on retained staff means billable hours are not covering the fully-loaded cost. See the employee cost calculator.
- Too many specialists. A 12-person startup with three separate analytics people and two DevOps is probably over-specialized for its size.
Where high RPE is a warning, not a trophy
Extremely high RPE can also be a problem. If RPE is 2× the industry benchmark, you may be under-staffed — stretched teams, burned-out operators, critical single points of failure. A business running at $600K RPE against a $250K industry norm is either wildly efficient (rare) or quietly on fire (more common). Pressure-test by asking: "If three key people quit, does the business still function?" If the honest answer is no, you are riding high RPE by running people too hot.
RPE and pricing power
High RPE almost always correlates with pricing power. You charge more per customer, use fewer hands to serve them. Low RPE often indicates commoditized pricing — lots of work per dollar. If you want to improve RPE, the most durable path is usually price increases on existing customers paired with productivity gains, not headcount cuts. Cut headcount and you lose capacity; raise price and you raise RPE without shrinking capacity. The pricing calculator helps model what a price change does to the whole system.
RPE milestones for growing companies
- $100K RPE: survival threshold for most businesses. Below this, you are likely losing money.
- $200K RPE: standard for services and mid-market businesses.
- $300K RPE: efficient operator in most categories.
- $500K RPE: excellent. Usually requires strong product leverage and/or premium pricing.
- $1M+ RPE: rare. Pure software companies with enterprise contracts, or capital-intensive businesses with very few employees.
Include contractors?
RPE is traditionally calculated on full-time employees (W-2 or equivalent). But businesses increasingly use contractors, offshore staff, and fractional executives. A business with 8 W-2 employees and 10 full-time equivalent contractors has 18 people doing the work — its "real" RPE is revenue divided by 18, not 8. Use the larger number for internal operational benchmarking; use the W-2-only number when comparing to industry averages that typically exclude contractors.
When to look at gross profit per employee instead
For low-margin businesses (restaurants, retail, distribution), revenue per employee is misleading because cost of goods is most of revenue. Gross profit per employee is a better metric — it measures the dollar contribution to the business's fixed costs and profit per head. A restaurant with $150K RPE and 30% gross margin has $45K gross profit per employee. That is the number that actually funds management, rent, and profit.
Revenue per employee vs profit per employee
The ultimate efficiency metric is profit per employee. It rolls in both pricing power and cost discipline. Best-in-class small businesses operate at $40K–$100K profit per employee. Top-tier tech companies hit $500K+ profit per employee. If RPE looks healthy but profit per employee is weak, you have a cost problem, not a revenue problem — likely a margin issue worth running through the profit margin calculator.