Khaled Azar 
Somewhere in the middle of diligence, a buyer will ask who handles your renewals. It sounds like small talk. What they are testing is whether your retention belongs to the product, to a process, or to one person who happens to be very good at their job, and most founders fail that test without ever knowing it was run.
Gainsight looked at 17,034 customer success managers at US companies above $100 million in ARR and found the median one carries $1.4 million of ARR. Those are companies with real customer success teams, budgets and software. They still put that much revenue under a single name. A company doing $5 million does not have 3 or 4 customer success managers. It has 1 person who also handles onboarding and support, or it has you.
The answer they want is boring. Renewals run on a process, here it is, and here is the evidence it works when the usual person is out sick. Most founders cannot give it.
By the end of this post you will be able to run one test on your own renewals, see what a buyer would see, and know which fixes are worth starting before you go to market.
What is customer success dependency, and why does a buyer care?
Because they are not buying last year’s revenue. They are buying next year’s, and next year’s revenue gets renewed by whoever is still there.
They pay you today for money that arrives over the following 3 to 5 years, and every one of those dollars has to survive a renewal conversation. If those conversations only go well because one person makes them go well, the buyer is not buying a revenue stream. They are buying an employment risk with a revenue stream attached.
This is the same thing they are testing when they ask about key person risk or when they push on how much of the business runs through you. Customer success dependency is just the version of it that founders never think to prepare for, because the person involved is usually not the founder.
How would they even find out?
They ask the same question 4 different ways and see whether the answers match.
- They read your notes. Not the CRM summary, the actual account notes. If the last real entry on your biggest customer is 14 months old, the knowledge is not in the system. It is in somebody’s head.
- They look at who is on the calendar. Pull the meeting invites for your top 10 accounts over the last year. Count the distinct names on your side. If it is 1, that is the finding.
- They ask your customers. During reference calls, a good buyer asks who the customer would call if something broke. Customers answer honestly and immediately, because they are not thinking about your deal.
- They compare your churn to your headcount changes. If someone left and a cohort dipped 2 quarters later, that shows up in cohort retention even when the headline number looks fine.
None of these require you to admit anything. By the time the question gets asked out loud, they usually know the answer already and are checking whether you do.
What does it actually cost me if they find it?
Rarely the deal. Usually the structure, which is a polite way of saying some of your money moves later or goes away.
A buyer who believes retention depends on a person has 3 tools. They can hold money back until the risk passes, which is an escrow or holdback. They can make part of the price conditional on retention holding up, which is an earnout. Or they can pay less, on the argument that they are buying a smaller, riskier thing than the one you described.
The third is the worst and the hardest to argue with, because by then the conversation is not about your business. It is about their confidence, and confidence is not something you can produce in week 6 of diligence.
Nobody reduces your price because you have a good customer success person. They reduce it because they cannot see what happens when that person is gone. The fix is not hiring more people. It is making the work visible.
What if my customer success lead is genuinely excellent?
Then you have a bigger problem than a mediocre one, and this is the part founders resist.
A great customer success lead absorbs friction. They remember which stakeholder hates the new interface, they catch the quiet unhappiness early, and they do it without writing much down, because writing it down is slower than just handling it. Every one of those instincts is real value, and none of it transfers.
The odds are not on your side either. In the Customer Success Collective’s 2026 look at the customer success job market, 44% of CS professionals had been at their current company for 2 years or less, up from 18% the year before. Nearly 40% planned to change employers within 1 to 2 years, and 71% of those who answered directly were already looking.
Share of customer success professionals who had been at their current company for 2 years or less in 2026, against 18% a year earlier. A buyer holding your company for 5 years is doing that arithmetic while you are telling them how good your CS lead is.
Your excellent person is an asset today and an open question at closing. The work is to turn what they know into something that survives them.
The renewal trace: the test a buyer is running on you
Here is the exercise. It takes about 1 hour and you can do it this week.
Take your 3 largest renewals from the last 12 months. For each, write down every step between 90 days out and a signed agreement. The health check. The heads up to your champion. The pricing conversation. The internal approval. The paperwork. Next to each step, write the name of the person who did it.
Now count the distinct names.
| Distinct names across your 3 largest renewals | What a buyer concludes | What it does to your deal |
|---|---|---|
| 1 name | Retention is a person | Retention tied to price, through a holdback or an earnout |
| 2 names, same 2 every time | Retention is a small team, and a fragile one | Questions about what happens if either one leaves. Usually a retention package |
| 3 or more, varying by account | Retention is a process | Moves off the risk list |
Most founders expect to land in the third row and land in the first. That gap is the whole point of running it yourself, months before somebody runs it on you.
Then run it again on your 3 largest upsells. This is the leg founders skip and buyers do not. When renewals and expansion trace back to the same single name, your retention rate and your growth rate rest on one person. That is the difference between a buyer questioning your churn and a buyer questioning your forecast.
What do I fix before I go to market?
4 things, in this order, because the order is what makes it believable.
- Write the renewal down as a sequence. Not a policy document. What happens at 90, 60 and 30 days out, who does it, and what gets sent. If it lives in one person’s calendar reminders, it is not a process.
- Put the account knowledge somewhere else. 1 page per major customer: who decides, who blocks, what nearly went wrong last year, what they asked for and did not get. Almost nobody does this, and it is the most valuable hour on the list.
- Give a second person real renewals. Not shadowing. Ownership of actual accounts, with the outcome attached to them. A buyer can tell the difference between a name on an org chart and a name on a signed renewal.
- Then produce the evidence. Once that person has closed real renewals you have a before and after, which is the only version of this argument that survives diligence.
The first 2 cost nothing but attention. The last 2 need time to become true, which is why this belongs in preparation and not in the deal.
How long does this take?
The writing takes 2 weeks. The proof takes 2 or 3 renewal cycles.
On annual contracts, a second person needs to have carried real renewals for 6 to 9 months before the pattern means anything. On quarterly contracts you can build the same evidence in half the time. Either way it is longer than diligence, which is why this starts before you have a buyer, not after.
Retention is the number a buyer trusts least as a single figure, which is why what your retention is made of matters as much as the number. A strong figure with one person behind it is not a strong figure. It is a bet the buyer is being asked to take without being told.
Frequently asked questions
What is customer success dependency in a SaaS acquisition?
It is when your renewals depend on a specific person rather than on a repeatable process. Buyers treat it as a form of key person risk. The test is simple: if the person who runs renewals left tomorrow, could somebody else carry the next 12 months of renewals using what is written down? If the answer is no, a buyer prices that.
Will a buyer walk away over this?
Very rarely. It changes the structure instead, and the finding itself is common enough that buyers expect it. What actually costs money is having no answer ready when they raise it.
Does hiring more customer success people fix it?
Not on its own, and not quickly. Adding headcount without moving ownership just gives you more people watching one person do the work. What changes a buyer’s mind is a second person who has personally closed real renewals on real accounts, with the record to show it.
What if I do the renewals myself as the founder?
Then it is the sharper version of the same problem, because you are the one leaving. A buyer will assume every renewal conversation currently runs through your relationship and will structure the deal to keep you around long enough to transfer it. Handing renewals to somebody else before you go to market is one of the few things that visibly raises what a buyer will pay.
When should I start on this before selling?
At least 2 to 3 renewal cycles before you go to market. The paperwork is fast. The evidence is not, and evidence is the only part a buyer credits.
Not sure how a buyer would read your retention today? A value assessment covers where your revenue depends on people rather than process, and what that is worth at closing.