Your customer has met three CSMs in two years.
Each one opened with the same call.
Tell us about your goals.
Walk us through how your team uses the product.
Who else should we be talking to?
The first time, the customer answered in detail. The second time, they answered politely. The third time, they sent a junior admin.
Nobody on your side noticed. The account stayed green. Usage held. The renewal is due soon.
The customer noticed everything.
I checked the TopCSJobs board data to see how often the seat behind that account changes hands.
The Same Job, Posted Again
TopCSJobs pulls CS postings straight from employer hiring systems and keeps every listing after it closes.
I compared 584 CSM postings from the last 90 days against every CSM listing since March.
At least 1 in 7 companies hiring CSMs re-posted the same role. Same city, same responsibilities, posted again about seven weeks after the first listing came down.
The data can’t say why.
Maybe the hire left. Maybe the seat never filled.
For the customer, both end the same way → their account sat with someone covering it, then moved again.
That number is a floor.
It only counts roles where the posting matched almost word for word. Every reworded or relocated version of the same seat falls outside it.
What Never Makes It Into the Handover
When a book changes hands, the CRM moves in seconds. Owner, ARR, renewal date, health score. All of it transfers.
Three things stay behind.
The promises
A product manager said “Q3” on a call last spring. An AE wrote “we can look at that” in a pricing thread.
A promise made on a call is still a promise to the customer, and the new CSM usually hears about it for the first time at renewal.
The renewal story
Why the customer signed last time. Which outcome they report to their boss. What almost made them leave.
Your forecast still reads green, because none of that lives in a field.
The relationship
Two years of trust doesn’t move with a welcome email.
The new CSM starts at zero, and the customer has to decide whether to invest again.
Why the Green Accounts Go First
Teams that inherit accounts triage by noise.
The account that escalates gets a call this week. The account that files a ticket gets a reply. The silent account gets a welcome email and goes to the back of the queue.
Silence looks like health. Often it means the customer stopped expecting much.
Then the clock does the rest.
An account inherited a year before renewal has time to rebuild. One inherited 90 days out has a meeting or two, and the new CSM spends the first one learning the account.
When the seat stays open for weeks, the book lands on teammates who were already near their limit. The silent accounts wait longer still.
The inherited account closest to renewal and furthest from anyone’s attention is the one you lose.
Find the Account That Slips First
You inherited a book, or you’re about to split one.
Somewhere in it is an account that looks fine, renews soon, and carries a promise nobody on your side remembers making.
You won’t spot it in a health score. It’s green.
Below, paid members get the system that finds it in one sitting and keeps the customer from starting over:
Which account to call first
Five signals that rank your inherited book by renewal risk. One of them is a number your CRM gets wrong.
The first call
The opening line that replaces discovery, and why the customer trusts you more after it.
The promise you didn’t make
The two questions that decide what happens to an inherited commitment, and the sentence that turns it from a renewal threat into credit.
The next handover
The one rule that stops a book from moving before it’s ready.
If your accounts change hands at the start of the year, the renewal risk is being set this quarter →