The short version
- The CRM holds the deal. It does not hold what was said on the call, and what was said on the call is what the customer remembers.
- Three things transfer: commitments made, sensitivities, and what is due. Everything else the new owner can find themselves.
- The customer should hear about the change from the person leaving the account, by name, before they hear it from anyone else.
- Write down the promises that were never written down. That is the whole job, and it is the part most handovers skip.
Account handovers go wrong in a specific way. The new owner has every record: contract, renewal date, support history, notes. Six weeks in, the customer references something agreed in a call last spring, the new owner has never heard of it, and the relationship takes a knock that takes two quarters to repair.
"Your colleague said we would not be charged for the extra seats until January." Nobody wrote that down.
What the CRM does not hold
A CRM is built to record the state of a deal. It is not built to record the texture of a relationship, and the texture is what the new owner needs on day one.
Three things are reliably missing. Commitments made verbally and never entered anywhere. Sensitivities, which are the things you must not say and the history behind them. And the customer's own words about why they bought, which is the thing that makes a renewal conversation land.
None of these are oversights. They are the sort of thing nobody writes into a system because there is no field for them, and because at the time everyone involved remembered.
The checklist
| Item | What good looks like |
|---|---|
| Commitments made | Every promise, written or verbal, with who made it, when, and whether it has been kept |
| What is due | Dates in the next 90 days: renewals, reviews, deliverables, invoices |
| Who is who | The economic buyer, the day to day contact, the one who will block things, and how each prefers to be reached |
| Sensitivities | The outage in March, the failed integration, the person who left badly. What not to raise, and why. |
| Why they bought | In the customer's own words, not the internal summary |
| Open questions | What the departing owner does not know, and who might |
Six items, one page. The temptation is to add account history and product usage, and the new owner can read those themselves. Keep the handover to what is only in someone's head.
Unwritten commitments
This is the row that prevents the worst outcome, and it needs a specific prompt to fill in, because people do not remember their promises when asked generally.
Ask the departing owner these three questions and write the answers down verbatim.
- What have you told them we would do that is not in the contract?
- What have you told them we would not do?
- What are they expecting in the next quarter that nobody has scheduled?
The second question is the one people forget, and it is often the most consequential. "I told them we would never move them onto the new pricing without a conversation first" is precisely the sort of promise that causes a churn event when a new owner does not know it exists.
Telling the customer
The order matters more than the wording. The departing owner tells them first, by name, with a reason and a handover date. Then a joint call if the account justifies it. Then the new owner alone.
What damages accounts is finding out by accident: a reply from a new address, or a calendar invite from a stranger. That reads as being deprioritised, whatever the actual reason.
Do not over explain the internal reason. One line is enough. What customers want to know is who they call now and whether anything they were promised is still true.
The new owner's first 30 days
The handover document answers the first week. After that the new owner hits the long tail: a question about something that happened eight months ago, a reference to a conversation nobody recorded, an assumption the customer makes that came from somewhere.
The departing colleague is now busy with something else, or gone. So the new owner either asks around, guesses, or asks the customer, and asking the customer to re explain their own history is the thing that makes a handover feel like a downgrade.
This is what StandIn is built for. Each day, the account owner spends about ninety seconds on a brief: what moved, what is open, what is blocked, what is next, mostly drafted from the work that already happened. When they hand over or are unavailable, their StandIn answers from that record, in their words, with a source under every answer. It never guesses, and when the answer is not there it says so and names who to ask. The new owner can find out what was agreed in March without writing to a former colleague or asking the customer. See how teams use it.
Common Questions
How long should the overlap be?
Two weeks for a routine reassignment, four for a strategic account. The value is in the joint calls, not in the document, so count the overlap in customer conversations rather than in days.
What if the departing person has already left?
Go to the customer earlier than you otherwise would, and be honest that you are picking things up. Most customers respond well to "I want to make sure I have this right" and badly to a new owner pretending to full continuity.
Should the handover document be shared with the customer?
No. It contains internal sensitivities. Share a short summary of what is due and who is now responsible.
Does this apply to a sales to customer success handoff?
The principles carry over and the emphasis shifts to what was promised in the sales process. That case is covered in the sales to customer success handoff.
90 seconds, then it's on.
Engineers publish a brief before they log off. The next timezone starts with full context, not a reconstruction of what happened while they slept.