The short version
- The cost of a bad handoff is the customer repeating themselves in week one, after they have already explained it twice during the sale.
- Put the buyer's own words at the top of the form. Not the summary, the sentences they used about why they were buying.
- Capture what was promised that is not in the contract. That is where the first churn risk lives.
- A handoff meeting without a written form is a meeting whose content evaporates within a fortnight.
A customer signs on Friday. On Monday they meet their new contact, who opens with "so tell me a bit about what you are hoping to achieve". The customer has now explained their problem three times to the same company, and the third time is the one that makes them wonder what they have bought.
What a bad handoff costs
It shows up in three ways, and none of them are recorded as handoff problems.
The customer loses confidence in week one, which shortens every subsequent benefit of the doubt. A promise made during the sale goes unmet, because nobody after the sale knew about it. And onboarding gets configured for the use case in the proposal rather than the one the buyer actually described, which is frequently different.
All three are cheap to prevent and expensive to repair, and all three come from the same root: the sale produced understanding, and only the contract was transferred.
The handoff form
One page. Written by the seller, read by the new owner before the first call, not during it.
| Field | What goes in it |
|---|---|
| 1. In their words | Two or three sentences the buyer actually said about the problem. Quoted, not paraphrased. |
| 2. What we promised | Everything said that is not in the contract, including what we said we would not do. |
| 3. Who is who | The champion, the budget holder, the sceptic. Name the sceptic. There is always one. |
| 4. What success looks like to them | The measure the champion will be judged by internally, which is rarely the one in our deck. |
| 5. Known risks | What nearly stopped the deal, what they compared us against, what they are nervous about. |
| 6. Open questions | What the seller does not know. Usually technical detail deferred during the sale. |
Hold a fifteen minute call on top of the form, never instead of it. The call surfaces the tone and the hesitations. The form is what someone reads in month four when the renewal conversation starts.
Why the buyer's own words go first
A summary is a translation, and translations lose the specifics that make a customer feel understood.
Compare: "needs better reporting" against "my board asks me the same three questions every month and it takes my analyst two days to answer them." The first is a category. The second tells the new owner what to configure, which three questions to solve first, and what sentence to use in the first call to show they have been briefed.
It costs the seller nothing, because they heard the sentence and wrote it in their notes. It just has to survive the transfer.
The promises row
This is the one that prevents churn, and it needs a direct prompt because sellers do not volunteer it.
Ask three questions, verbatim answers.
- What did you tell them we would do that is not in the contract?
- What did you tell them we would not do, or would never change?
- What do they expect in the first ninety days that nobody has scheduled?
The second question catches the most dangerous category. An undertaking that a customer will always be consulted before a change, or that a particular integration will never be deprecated, does not appear anywhere and is remembered perfectly by the customer.
Make it culturally safe to answer honestly. If sellers believe the promises row will be used against them, they will write nothing, and you have a form that documents only the contract you already had.
What happens after week one
The form covers the first two weeks well. After that, the new owner hits questions the form never anticipated. Did we agree to the extra environment. What was said about the January price change. Why did they reject the annual plan.
The seller has moved on to a new quarter, or has left. So the new owner asks the customer, and asking the customer to re explain their own history is exactly what the handoff was supposed to prevent.
This is what StandIn is built for. Each day, the seller 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. After the handoff, their StandIn answers from that record, in their words, with a source under every answer. It never guesses, and when the answer is not in the record it says so and names who to ask. The customer success owner can find out what was said in the third call without writing to a colleague who is now selling something else. See how teams use it and the account handover checklist.
Common Questions
Should the seller stay on the first customer call?
Yes, for the introduction, and they should hand over visibly rather than lingering. A seller who stays for the whole call teaches the customer to keep going to them.
How do we get sellers to fill this in?
Make it a gate on the commission process and keep it to one page. Both matter. A gate on a four page form produces four pages of nothing.
What if sales and customer success are the same person?
Fill it in anyway, for yourself. In six months you will not remember the exact sentence the buyer used, and you will need it for the renewal.
Does the CRM not cover this?
It covers the deal. It does not usually hold the buyer's own words, the undertakings given verbally, or who the sceptic was, because there are no fields for them and no prompt to write them.
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.