Khaled Azar 
Key person risk in SaaS M&A is the risk that revenue, product knowledge, customer trust, or operating judgment sits with one person instead of the company. Buyers price that risk hard because Mercer research across more than 200 transactions says 40% of critical talent leaves in the first 18 to 24 months after close.
If you are the founder, the question is not whether you matter. You should matter. The question is whether the business can keep selling, shipping, renewing, and deciding when you are no longer the daily operating system.
What Key Person Risk Means in SaaS M&A
The risky version is not leadership. It is invisible dependency.
In a SaaS sale, key person risk usually shows up in four places: customer relationships, product decisions, sales motion, and technical knowledge. If the founder owns all four, buyers see a company that may not survive the transition intact.
This is different from normal founder involvement. A founder joining strategic customer calls is fine. A founder being the only reason top customers renew is not. A founder guiding product strategy is fine. A founder being the only person who understands the roadmap, architecture, and backlog tradeoffs is not.
That is why this post complements our guide on how to reduce owner dependency before selling. Owner dependency is the operating problem. Key person risk is the buyer lens: if this person leaves, what breaks first?
CFO.com coverage of a WTW M&A retention survey found that 28% of respondents did not have complete visibility into M&A retention spend, even though key employee retention is central to deal continuity.
The 90 Day Key Person Risk Fix
You do not fix key person risk by disappearing. You fix it by making the business prove it can function without you as the bottleneck.
Start with a simple map. List the top 10 places where someone says, “Ask the founder.” Do not make it theoretical. Pull the last 30 days of Slack, email, CRM, support escalations, product decisions, sales calls, and finance approvals. Write down every recurring dependency.
Then score each dependency by buyer impact. A founder approving a $200 software subscription is annoying. A founder owning the top five customer relationships is dangerous. A founder being the only person who can explain churn drivers, pricing exceptions, or roadmap commitments is a diligence problem.
| Dependency | Buyer concern | 90 day fix |
|---|---|---|
| Founder owns top customer calls | Revenue may leave with the seller | Move account ownership to a named leader and document account plans |
| Founder closes every material deal | Sales process is personality based | Document sales stages, handoff rules, pricing authority, and win loss notes |
| Founder is product referee | Roadmap knowledge is trapped | Create roadmap rationale, customer request log, and decision rights |
| Founder knows the messy parts of finance | Forecast and add back quality are hard to prove | Build a monthly operating pack with ARR bridge, churn, margin, and cash notes |
The fastest useful fix is documentation plus delegation. Documentation without delegation looks like homework. Delegation without documentation looks fragile.
The goal is not to make the founder irrelevant. The goal is to make the founder explainable, replaceable in daily workflow, and valuable during a defined transition.
What Buyers Actually Check in Due Diligence
Buyers do not ask, “Are you important?” They ask for evidence that the company is not trapped inside your head.
In diligence, key person risk becomes document requests and management questions. The buyer asks for org charts, employment agreements, contractor agreements, compensation plans, customer ownership maps, roadmap materials, support escalation logs, sales pipeline reporting, and transition plans.
Goodwin wrote in November 2025 that acquired workers are nearly twice as likely to leave after a deal, with attrition rising in the first 12 months after buyout. That matters even more when a SaaS company depends on a handful of technical, sales, or customer success leaders.
Buyers also connect key person risk to the rest of diligence. If the founder owns revenue quality, they will test the ARR bridge harder. If the founder owns accounting judgment, they will ask more questions during quality of earnings review. If the founder owns customer relationships, they will connect the issue to customer concentration risk.
The buyer question that reveals whether you fixed it: “Who besides you can walk us through this customer, this product decision, and this forecast without prep?” If the answer is always you, the risk is not fixed.
Where Key Person Risk Hits Valuation
Key person risk rarely shows up as one clean line item. It bleeds into deal structure.
A buyer may lower valuation because the forecast feels less durable. They may push for a longer transition, add an earn out, hold back more price, or make key employee retention a closing condition. None of that feels like a “key person risk discount” in the LOI, but that is what it is.
This is why Deloitte’s 2026 M&A survey matters. Deloitte surveyed 1,500 U.S. corporate and PE leaders and found that 90% of PE respondents and 80% of corporate respondents expected deal volume to increase in 2026. More buyers in market does not mean softer diligence. It means better prepared sellers get compared against weaker ones faster.
If your metrics are clean but dependency is messy, buyers have options. They can buy another SaaS company that is easier to transfer.
Deloitte’s 2026 M&A Trends Survey found high buyer appetite, but also more measured expectations and continued volatility. Fragile operating models get punished.
What to Put in the Data Room
You should not wait until post LOI diligence to assemble this. Put the proof in the data room before buyers ask. That creates confidence and shortens the “founder dependency” conversation.
At minimum, include an org chart with decision rights, customer ownership map, sales notes, customer success playbooks, support escalation rules, roadmap rationale, key employee agreements, compensation summary, and a transition plan for the first 100 days after close.
This belongs next to the materials in your M&A data room preparation checklist, not buried in a folder called operations. Key person risk is not an HR issue only. It affects revenue, product, diligence speed, and closing certainty.
For SaaS founders, I like one extra document: a founder dependency memo. One page. Three columns. What I do today, who owns it next, and what proof shows the handoff is working. It is simple, and it changes the buyer conversation.
If buyers can see named owners, documented processes, and live examples of the team operating without founder approval, the risk moves from scary to manageable.
How Long It Takes to Fix
A clean first pass takes 90 days. A convincing fix usually takes 6 to 12 months because buyers want evidence, not intentions.
In the first month, map dependencies and pick the three highest risk areas. In month two, delegate ownership and document the workflow. In month three, let the new owner run the process while you observe. By month six, you should have logs, customer interactions, reports, and decisions that prove the handoff happened.
That timing matters if you are planning a sale. A strong SaaS exit starts when the business can answer buyer questions without calling the founder into every room. For a broader prep view, see our SaaS exit readiness checklist.
Frequently Asked Questions
What is key person risk in M&A?
Key person risk in M&A is the risk that a company depends too heavily on one founder, executive, engineer, salesperson, or customer owner. Buyers test it because Goodwin notes acquired workers are nearly twice as likely to leave after a deal, with attrition rising in the first 12 months.
How do you reduce key person risk before a sale?
Reduce it by mapping your top 10 dependencies, fixing the three highest risk areas first, documenting workflows, and moving ownership to named leaders. A 90 day sprint can create the first proof, but 6 to 12 months is stronger for buyer confidence.
Do buyers discount for key person risk?
Yes. Buyers discount key person risk through lower valuation, longer transition terms, earn outs, holdbacks, and retention conditions. WTW survey coverage found CEO retention awards averaged 137% of base salary, which shows how seriously deal teams price continuity.
How long does it take to fix owner dependency in SaaS?
A practical first pass takes 90 days, but a buyer grade fix usually takes 6 to 12 months. SaaS buyers want evidence that customer ownership, product decisions, sales process, and reporting work without the founder as daily bottleneck.
Next Steps
If you are thinking about a sale and know too much of the company still runs through you, fix it before buyers turn it into deal structure.