The sales to CS handoff, run as a playbook

In most teams the handoff is a Slack message or a Chatter post, written by the AE on the way to the next deal. Company, contract value, a contact name. Everything that mattered, why they bought, what they were told, who in the room was quietly unconvinced, stays in the AE's head and in six hours of recordings nobody will rewatch.

The CSM finds out in the kickoff.

Customers describe the symptom the same way every time: being asked the same questions twice. They explained their data migration to sales in March, a new person asks about it again in May, and they draw the obvious conclusion about how well your company talks to itself. Meanwhile the post-sale team spends its first few weeks reconstructing a deal it should have inherited.

Nobody in that sequence is being lazy. It is a process with no deadline and no owner, so it runs on goodwill, and goodwill does not survive quarter-end.

Day -14 · Owner: AE

Start the handoff while the deal is still at commit. The calls are fresh, so the AE can still say which promise was made on which call. And the AE still has a reason to care, because the deal has not closed.

The rule that makes the pack worth reading: every line is marked Confirmed, Unclear or Not discussed, and every Confirmed line points at a source, a call timestamp or an email. A pack full of confident statements with no sources is worse than no pack at all, because the CSM will believe it.

Spend most of the time on one section: everything promised during the sale. Features, dates, discounts, and every "we can look into that". It is the list the customer will hold you to, and it is the one that gets written most loosely. If you want a vocabulary for which of those count as commitments, the commitment taxonomy is ours.

Day 0 · Owner: RevOps

A handoff that depends on the AE remembering is optional. Make it mandatory at the one moment the AE cares about most.

Add two fields to the opportunity or deal: a Handoff Pack URL and a Handoff Status picklist with Draft and Complete. In Salesforce, a validation rule blocks the move to Closed Won until both are filled in. In HubSpot, set those two properties as required on the Closed Won stage in the pipeline settings. Either one is twenty minutes of admin work.

Expect a week of complaints. Then expect them to stop, because the fastest way to close a deal is now to finish the pack.

Do not add a third required field. Every field you add becomes a field someone fills with "n/a".

AND(
  ISPICKVAL(StageName, "Closed Won"),
  OR(
    ISBLANK(Handoff_Pack_URL__c),
    NOT(ISPICKVAL(Handoff_Status__c, "Complete"))
  )
)

Error message: Finish the handoff pack before closing. Link it in Handoff Pack URL and set Handoff Status to Complete.

Day 1 to 2 · Owner: CSM runs it, AE attends

Within two business days of signature, the AE and the CSM meet for thirty minutes. The AE tells the story of the deal. The CSM plays the customer's skeptic: why did they pick us over the incumbent, what exactly did we say about the integration timeline, who in that room did not want this?

Anything new goes into the pack before the meeting ends. Not after. After is where it gets lost.

If the AE has already been pulled onto next quarter and will not show up, and this happens more than anyone admits, the CSM books the thirty minutes with the recordings instead. Go through the pack line by line against the calls, mark every gap Unclear, and make the AE the owner of each one with a 48-hour deadline to answer asynchronously. Named gaps are fine. Guessed ones are what hurt you in month four.

Day 5 · Owner: CSM

Kickoff within five business days of signature. Open it by reading back what you understand they bought and why, in their own words, and then ask what you got wrong. This is the cheapest moment you will ever have to catch a bad handoff. It costs one slightly awkward minute now instead of a renewal later.

Then go through the promises, line by line, and put a date next to each one in front of them.

Some will not have a date yet. Say so. A customer can live with "we do not know yet, you will have an answer by the 20th". What they will not forgive is finding out in month four that the thing they were promised was never tracked by anyone.

Day 30 · Owner: CS lead

At day 30 the CS lead opens the pack and checks one thing. For each promise from the sale: is it done, on track, or quietly dead?

Score the handoff, not the CSM. How many promises had a source. How many Unclear lines were resolved before kickoff. How many surprises came up in the first month that the pack never mentioned.

Run this on every deal for one quarter and you end up with something far more useful than a satisfaction score: a list of the kinds of things your sales team promises that your delivery team never hears about. It usually comes down to a handful of recurring topics, a security questionnaire, a custom report, a timeline someone improvised late on a call. Fix those in the sales process and every future handoff gets shorter on its own.

The day-30 audit is always the first thing to go when a CS team gets busy. It is manual, and nothing visibly breaks on the day you skip it. That is the point where teams either hire a CS operations person or automate the assembly: the pack drafted from the calls and emails, the promises extracted and dated, the AE and CSM approving the draft instead of writing it from scratch. We build the second one, and the mechanics of how we run it are in the sales to CS handoff runbook.

One question this playbook leaves to you. Where exactly does "we can look into that" become a promise? It is worth an hour with your sales lead. Teams draw that line in very different places, and the argument is more useful than wherever you end up.

Run it by hand for a quarter first. The list of things your team promises and never tracks is the most useful document your CS org does not have yet.