Key takeaways
- IC memos flag key man risk at a 0.3–0.5x EBITDA multiple discount when three named individuals represent 60%+ of operational continuity
- Buyers identify key man dependencies in management interviews, not the data room, the "90-day absence" exercise reveals non-obvious exposures founders routinely miss
- Retention agreements sized at 3–6 months of base salary ($50–150K typical) reduce departure rates 65–70% compared to businesses with no formal retention program
- Below-market compensation is the vulnerability that makes loyal employees receptive to outside offers during the uncertainty of a sale process
- Address below-market pay 12–18 months before a process so the adjustment appears in trailing financials, not as a diligence-window question
In this article
Operating diagnosis
How buyers assess key man risk
For adjacent context, compare this with Founder Dependency: The Operating Signals Buyers Read Before Diligence Begins and The Founder Vacation Test: The Cheapest <a href="/insights/transaction-readiness-checklist-founder-owned" class="subtle-link">Transaction Readiness</a> Diagnostic Available; the strongest operators connect these topics instead of treating them as separate workstreams.
What this means in practice: the first improvement is usually not a new dashboard; it is a named owner, a fixed metric definition, and a recurring decision cadence that forces action.
Operator Checklist
- Name the metric, process, or decision this issue affects.
- Assign a single owner with authority to change the process.
- Pull the last 12-24 months of data and identify the pattern, not just the latest month.
- Choose one corrective action that can be tested in the next 30 days.
- Review the result in the next management cadence and document the decision.
In every PE-backed middle market transaction, the buyer conducts management interviews, conversations with your leadership team, key operators, and customer-facing employees. The goal is partly to evaluate talent, but equally to identify concentration: who does the business actually depend on, and what happens if that person leaves?
A skilled buyer interviewer will ask the same question multiple ways: "Walk me through how decisions get made in your area." "If you took two weeks off, what would not happen?" "Who would you call if you had a problem you could not solve yourself?" The answers map the dependency network of the business and reveal which people represent concentration risk.
Loyal long-term employees do stay in many cases, relationships built over 10 years are genuinely stable, and that loyalty is real. What's often missed is that a sale process, with months of uncertainty, management distraction, and ambiguous post-close role definitions, which is exactly the moment those employees are most vulnerable to outside offers. Buyers price the departure risk accordingly.
IC memos at PE funds routinely flag key man risk as a primary diligence concern. A business where three named individuals represent 60% of operational continuity, customer relationships, and financial reporting gets a concentrated dependency flag that translates directly into a 0.3x–0.5x EBITDA multiple discussion in the investment committee.
~40%
Percentage of middle market transactions where a key employee departure creates material diligence friction
6–12 months
Retention risk window on either side of a transaction close
$50–150K
Typical retention bonus cost for a key employee, fraction of deal value risk avoided
Identifying your actual key man exposures
Most founders can name the obvious key men: the COO who runs day-to-day operations, the rainmaker who drives 60% of new business. The non-obvious key men are more dangerous because they are not on the list: the controller who actually knows how the books work, the project manager who holds the relationships with the top three customers, the technician whose institutional knowledge is embedded in systems no one else understands.
A useful exercise is to imagine the business running for 90 days without each person on your team, one at a time. Which absences would create customer-facing problems? Which would slow down financial reporting? Which would create delivery risk? The answers to those questions define your actual key man map, not your org chart.
Scroll to see more →
Compensation benchmarking as a retention foundation
The most common reason key employees leave during a transaction is not that they disagree with the sale, it is that a recruiter approached them with a competitive offer at exactly the moment they were uncertain about their future. Compensation below market is the vulnerability that makes them receptive.
Benchmarking compensation for your key employees before a process begins tells you where you are exposed. For each key person, identify the market rate for their role in your geography and industry using salary survey data, comparable job postings, and your advisor's perspective. Where you are materially below market, address it before a process begins, not in the middle of one.
Addressing below-market compensation during a live transaction process creates accounting and disclosure questions. Address it 12–18 months before engaging a banker so the adjustment is in the trailing financials and normalized in the QoE.
Identify key man dependencies
Map every role where departure would create customer, delivery, or operational risk. Be honest, the list is usually longer than the org chart suggests.
Benchmark compensation
Use salary surveys, comparable job postings, and advisor input to establish market rates for each key role.
Address below-market pay
For employees materially below market, make the adjustment now, not during a process. Document the rationale.
Design retention agreements
For the highest-risk roles, structure retention bonuses tied to deal close and a post-close employment period. Work with counsel on the mechanics.
Build succession for each key role
For each key man identified, identify a backup, either internal or a planned hire. Document the succession plan.
Operating workflow scan
Turn the issue in this article into a ranked AI workflow roadmap with readiness gaps and estimated time savings.
Find the first workflow →Retention agreements: what works and what backfires
Retention agreements tied to transaction close are a standard tool. Structured well, they align employee incentives with deal execution, the employee has a financial reason to stay engaged and perform through a potentially disruptive process. Structured poorly, they signal to buyers that you think key employees will leave, which raises the question of why.
The most effective retention agreements are: offered to a small, clearly defined group of true key men (not the entire management team), sized to be meaningful (three to six months of base salary) but not so large they attract scrutiny, tied to both deal close and a post-close employment period (typically 12–18 months), and presented to buyers as standard practice rather than a sign of distress.
Key employee departure during the due diligence or exclusivity period leads to deal termination or material price reduction in approximately 23% of cases where it occurs.
Retention agreements covering the top three to five key employees reduce departure rates during deal processes by 65–70% compared to businesses without formal retention programs.
The most effective retention structures combine a financial retention bonus with a defined role in the post-close organization, employees want to know they have a place, not just that they will be paid to stay.
Common mistakes founders make on employee retention and key man risk.
A $9M EBITDA business treated this issue as an operating cadence problem rather than a one-time analysis.
Management assigned a single owner, rebuilt the metric history across 18 months, and reviewed the trend monthly.
Within two quarters the team could explain the pattern, the corrective action, and the result without founder interpretation. In a buyer discussion, that documented cadence mattered more than the isolated improvement because it showed the business could manage the issue repeatedly.
Frequently asked questions
What is the 90-day absence exercise and how do I run it?
Imagine the business running for 90 days without each person on your team, one at a time. For each team member, ask: which customer relationships would be at risk, which delivery processes would slow down or fail, and which financial or operational reporting would become unreliable? The answers reveal your actual key man dependencies, not the org chart version. Complete this exercise at least 18 months before a process so you have time to address what you find.
How large should a retention bonus be to be effective?
Retention bonuses sized at three to six months of base salary are the standard range. The structure matters as much as the amount: a portion vesting at deal close (25 to 40%) and the balance over 12 to 18 months of post-close employment creates both a reason to stay through the process and a reason to stay after it. Bonuses that vest 100% at close solve the process problem but not the post-close retention problem.
Can I use informal letters of understanding rather than formal retention agreements?
No. Informal agreements discovered in diligence create immediate questions about what other informal commitments exist in the business. Use qualified counsel to draft formal plan documents for any retention arrangement. All grants must be documented with board or manager approval resolutions and included in the diligence data room from day one.
What is key man risk in M&A and how do buyers price it?
Key man risk is the degree to which a business's performance, customer relationships, or critical operations depend on specific individuals whose departure would create measurable harm. PE buyers assess this risk in management interviews and IC memos, when three or fewer individuals represent 60% or more of operational continuity, buyers typically apply a 0.3–0.5x EBITDA multiple discount to offset post-close execution risk. The discount is larger when the key individuals are not covered by a retention program.
How do you identify key man dependencies before a sale process?
Run a 90-day absence exercise for every manager and senior contributor: if this person were unavailable for 90 days starting tomorrow, what would break? Customer relationships that only they manage, operational decisions only they make, and institutional knowledge only they hold are all key man dependencies. This exercise consistently surfaces non-obvious dependencies, controllers who are the only person who understands the accounting system, technical leads who are the only person who can maintain a legacy platform, and that buyers find independently in management interviews.
How should retention agreements be structured for key man risk?
Effective retention agreements combine a financial component (typically 3–6 months of base salary, paid on a schedule tied to post-close milestones) with a defined post-close role. Employees who receive a financial retention payment but have no clarity on their post-close title, compensation, or responsibilities have a reason to leave the day after the retention period ends. The role definition matters as much as the dollar amount, buyers also respond more favorably to retention programs that include explicit post-close integration plans for each covered individual.
How many employees should be covered by a retention program before a sale?
Limit formal retention to 3–5 individuals who represent genuine key man risk, the people buyers will identify as critical in management interviews. Broad retention programs covering 8–12 people signal to buyers that the founder believes most of the management team might leave after close, which creates a broader organizational risk impression. A focused program with documented rationale for each covered individual demonstrates that management has made a considered assessment of post-close risk.
Work with Glacier Lake Partners
Assess Your Key Man Risk Before a Process Begins
We help founders map key man dependencies, benchmark compensation, and build the retention structure that keeps critical employees engaged through a transaction.
Assess Your Readiness →Operating workflow scan
Find the reporting or execution workflow worth automating first.
Turn the issue in this article into a ranked AI workflow roadmap with readiness gaps and estimated time savings.
Find the first workflow →Research sources
Disclaimer: Financial figures and case-study details in this article are anonymized, composite, or representative examples based on middle market operating situations, and are not guarantees of outcome. Statistical references are drawn from cited third-party research; individual transaction and operational results vary based on business characteristics, market conditions, and deal structure. This content is for informational purposes only and does not constitute legal, financial, or investment advice. Consult qualified advisors for guidance specific to your situation.
Explore adjacent topics
