Sales to CS handover: stop losing the customer context

The contract is signed. Two weeks later the first onboarding call starts, and the customer hears the question they were dreading: "To start, could you remind us of your context and what you expect from the tool?"

They have already told the whole story. To the seller, in discovery, then in the demo, then during the negotiation. They explained why the current tool was no longer enough, who had to approve, what had to work before the end of the quarter. And now they have to start over, in front of someone they do not know.

That moment costs more than it seems. It is the first impression of the relationship after signature, and it tells the customer that your company does not talk to itself.

Why the customer has to repeat themselves at kickoff

The cause is almost never bad will. The seller spent weeks with the customer and knows a lot, but that knowledge sits in their head and in recordings nobody reopens. The CRM record holds an amount, a close date and three lines of notes written between two meetings.

When the account changes hands, the record is what moves, not the seller's memory. The customer success manager, the account manager or whoever runs onboarding starts from scratch, and the only reliable source left is the customer.

A failed handover does not show on the day of signature. It shows at kickoff, when the customer realises they will have to repeat everything.

What gets lost between the sale and onboarding

Six things nearly always disappear in the handover. They are also the ones the team taking over the account needs most.

• The reason they bought. Not the generic need, the precise reason that tipped the decision. "We lose two days a month consolidating the numbers by hand" does not call for the same onboarding as "our leadership wants a single report".
• The success criteria they stated. What the customer said they would look at to judge the purchase. If they mentioned a deadline, a metric or a specific use, that is what they will measure your work against.
• The seller's promises. An integration "coming soon", extra support, a feature shown in the demo as available. The customer remembers them word for word, the delivery team never heard them.
• The risks and objections raised. An objection handled during the sale has not gone away, it is waiting for its first chance to return. A doubt about adoption by field teams will resurface in the first weeks.
• The stakeholders. Who signed, who uses it, who pushed back, who needs reassurance. The sponsor is not always the user, and the sceptic on the committee has not vanished.
• The timing constraints. An internal launch date, a trade show, an audit, a fiscal year end. The customer gave that date during the sale, and onboarding is planned without it.

A handover template that fits on one page

A good handover is not a long document. It is one page of precise fields, each filled with verifiable facts rather than impressions. The table below shows, for each field, the difference between a vague entry and a useful one. The examples are illustrative.

The left column is what gets written from memory on the evening of signature. The right column is what the customer actually said, and it is the only one that lets someone else take over the relationship without asking the questions again.

Who does what, and when

Before signature

The handover starts before the deal is won. As soon as it enters negotiation, the person who will take over the account should be able to read what was said, and the seller should know their promises will be read. That alone makes commitments more careful and more precise.

At signature

The seller fills in the handover page, then walks through it with the person taking over, for half an hour. The goal is not to summarise the sale, it is to answer the questions of whoever will deliver: what exactly was promised, who can block, what must be visible after a month.

At kickoff

The first call no longer opens with an open question, it opens with a restatement. "You told us the goal was to present the first numbers at the 15 January committee, and that adoption by the field teams worried you. Is that still the case?" The customer corrects what has moved, and knows they were heard.

When possible, the seller joins that first call. Their presence tells the customer the relationship continues, and it clears up any misunderstanding about what was agreed on the spot.

Handover from memory or handover from the conversations

The difference is not the seller's discipline. Even the most rigorous one summarises, and summarising means choosing. A handover built from the exchanges themselves lets the person taking over go back to the exact sentence whenever a doubt comes up.

Checking that what was promised matches what is delivered

Gaps between sale and delivery are rarely lies. They are optimistic wordings, a "it is planned" that became "it is available" in the customer's mind, demos showing a setup the customer will not have at first.

The check is simple to describe: take every commitment made during the sale, set it against the onboarding plan, and deal with the gaps before kickoff rather than after. A gap announced by your team is a clarification. The same gap discovered by the customer is a broken promise.

• List every commitment the seller made, with the sentence as it was said.
• Mark which are delivered from day one, which will come later, and which will not be delivered.
• For the last two groups, prepare the sentence to say to the customer at kickoff.
• Send back to sales the promises that keep coming up and that the product does not yet keep.

What to track after the handover

The handover is not an event, it is the start of follow-up. Three things deserve a weekly look during the first months.

• Commitments and their due dates. Your team's and the customer's. Data access promised by the customer's IT team for month end blocks as much as a configuration promised by you.
• The first risk signals. A remark about how long it takes to get started, a key user who stops attending check-ins, a comparison with the old tool. On their own they say nothing; read together they often announce disengagement.
• Customers going quiet. An active customer you have not heard from in several weeks is not a satisfied customer by default. Silence after onboarding is more often abandonment than autonomy.

This follow-up only has value if it happens in the same place as the handover. If commitments live in a document, risks in the CSM's head and dates in a calendar, nobody sees the customer as a whole.

The limits of a handover, even a good one

No template replaces the conversation between the person who sold and the person taking over. A generated synthesis remains a draft to review: it gathers what was said, it does not know what was half implied or what the seller sensed without hearing it.

And a handover is only as good as the conversations that were recorded, with the participants' consent. What was said in a corridor or on an unrecorded phone call will only travel through memory, with everything memory forgets.

The final test is still the kickoff. If the customer has nothing to repeat and spends the call correcting a few details rather than explaining everything again, the handover worked.