Key takeaways
- Revenue per employee benchmarks vary widely by industry, knowing yours relative to comparable businesses is table stakes in a PE process
- EBITDA per employee is a more useful metric than revenue per employee because it captures operational efficiency
- Headcount bloat is one of the most common EBITDA normalization opportunities buyers identify
- Improving headcount productivity before a sale can directly compress the implied buyer discount
- The metric matters less in isolation, trend and explanation matter more
Why PE buyers run headcount metrics first
When a PE firm first receives a CIM on a $15M EBITDA business, one of the first calculations their associate runs is revenue per employee and EBITDA per employee. These numbers take 30 seconds to compute and tell you a great deal: whether the business is over-staffed relative to peers, whether the owner has been managing headcount tightly, and whether there is margin expansion potential through productivity improvement.
Most founders have never calculated these numbers. That asymmetry is a problem, buyers arrive at the management presentation with benchmarks in hand, and founders arrive without context for what their numbers mean. Understanding where you stand before the process begins changes how you frame the conversation.
Revenue per employee
Industry median for lower middle market professional services: $185–240K
EBITDA per employee
PE benchmark target for stable, scalable service businesses: $35–65K
Headcount review
Percentage of PE diligence processes that include a headcount cost-benefit analysis: ~85%
How to calculate and benchmark your numbers
Revenue per employee is total revenue divided by full-time equivalent headcount. Include part-time staff on a pro-rated basis and contractors who are functionally equivalent to employees. Use your trailing twelve month revenue and your average headcount over that period, not the snapshot at any single date.
EBITDA per employee adjusts for the capital intensity of the business and the cost structure. A business with $300K revenue per employee but $20K EBITDA per employee has a cost structure problem. A business with $180K revenue per employee but $55K EBITDA per employee is running lean and efficiently.
Benchmarks vary significantly by industry. Technology-enabled services businesses run at much higher revenue per employee than labor-intensive service businesses. Construction and project-based businesses have inherently different structures than recurring-revenue SaaS-adjacent businesses. The right benchmark is comparable businesses in your specific segment, not the industry average.
Common headcount productivity problems and how to address them
The three most common headcount productivity problems in founder-owned businesses are: administrative bloat (support staff levels that made sense at a smaller scale but were never trimmed as the business grew), under-utilized senior hires (people brought in for a purpose that evolved or was never fully defined), and founder-proximate headcount (staff who exist primarily to support the founder's personal preferences rather than the business's operating needs).
Each of these has a different solution timeline. Administrative bloat can often be addressed through AI-assisted workflow changes and natural attrition over 12–18 months without difficult personnel decisions. Under-utilized senior hires require honest role assessments and either redeployment or transition. Founder-proximate headcount is the most politically difficult but often the most important to address before a sale, buyers will identify it and it creates questions about what the true cost structure looks like post-close.
Before engaging a banker, calculate your EBITDA per employee and compare it to industry benchmarks. If you are more than 15% below median, buyers will identify it and it will affect how they frame the multiple discussion.
Step 1: Calculate baseline metrics
Revenue per employee, EBITDA per employee, support staff ratio. Pull the last three years to show trend.
Step 2: Benchmark against comps
Use industry benchmarks and, if available, comparable transaction data from your banker or advisor.
Step 3: Identify the gap
If you are below median, categorize the gap: administrative bloat, under-utilized roles, or owner-dependent functions.
Step 4: Build a plan
For each category, define the path to improvement: AI automation, role consolidation, natural attrition, or role redefinition.
Step 5: Track and document
Track the metrics quarterly and document the improvement narrative so you can present it credibly in a management presentation.
Presenting headcount metrics in a management presentation
If your headcount productivity metrics are below benchmark, you have two choices: address the gap before the process or explain it during the process. Addressing it is better, but explaining it credibly is far better than ignoring it.
The most effective framing is: "Here is where we are, here is why, and here is the path forward." Buyers do not expect perfection, they expect self-awareness and a plan. A founder who can say "our revenue per employee is $160K versus an industry median of $200K, primarily because we over-built the administrative function during a period of rapid growth, and here is the 18-month plan to close that gap" is far more credible than a founder who has not thought about it.
Headcount efficiency is cited by PE buyers as a top-three value creation opportunity in 67% of lower middle market acquisitions, behind only pricing and organic growth.
Businesses that proactively present a headcount productivity improvement plan in management presentations receive 12–15% higher initial indications of interest than those that do not address the topic.
The most credible headcount plans are already in motion at the time of the management presentation, not aspirational.
Work with Glacier Lake Partners
Benchmark Your Business Before a Buyer Does
We run the operational benchmarks PE buyers use and help founders understand where improvement before a process creates the most value.
Get in Touch →Explore adjacent topics
