Sales to CS Handoff Checklist How-to
A handoff is not a document dump. It is a risk transfer ceremony. The gate question is spoken aloud: “What did the customer believe they bought, and what evidence do we have that we can deliver it?” If that answer is fuzzy, the deal is not ready to leave sales, and the checklist must fail closed.
This play is for AEs, CSMs, delivery leads, and their managers. Motions differ (PLG, enterprise, services). Adapt the same ceremony; do not pretend one template fits every model. This page does not invent churn statistics, SLA benchmarks, or legal enforceability of verbal promises.
Play card
| Field | Detail |
|---|---|
| Time box | 45-60 min internal handoff; customer kickoff scheduled separately |
| Players | AE (checklist owner until transfer); CSM/delivery lead; optional SE, finance, exec |
| Goal | Completed checklist, promises log, owner map, kickoff date, open risks |
| Done looks like | Gate question answered clearly; owners named; customer kickoff dated |
Links: Sales to delivery/CS handoff guide, How Sales Works, Help This Deal by Role, RACI lite, How Departments Work Together.
When to use
- Pre-close risk transfer through post-close kickoff on a named account.
- Any closed-won where delivery or CS will own outcomes.
- When promises during late-stage selling need a written home.
When to delay handoff
- Fuzzy scope or unmet contingencies.
- Missing commercial terms, order form, or success criteria.
- Gate question cannot be answered without guessing.
- Champion left and no replacement stakeholder is named.
Delay is cheaper than a surprise “that’s not what we sold” moment.
Prep before the internal handoff meeting
AE brings:
- Promises log (features, dates, services, commercials called out in selling).
- Success criteria in customer language.
- Stakeholder map (economic buyer, champion, day-to-day users, blockers).
- Known risks (integration, data, timeline, security).
- Commercial summary at a level CS needs (not a full contract dump without context).
Timed steps: internal handoff
| Clock | Move |
|---|---|
| 0-5 min | Purpose: risk transfer, not slide share. |
| 5-20 min | Gate question aloud; walk promises log line by line. |
| 20-35 min | Owner map: who owns onboarding tasks, escalations, commercial exceptions. |
| 35-50 min | Open risks and fail-closed items; decide delay vs proceed. |
| 50-60 min | Kickoff date, customer agenda, and “AE exits when ___.” |
Gate question script set
“What did the customer believe they bought?”
“What evidence do we have we can deliver it on the committed timeline?”
“Which promises are contractual, which are verbal, and which were hopeful?”
“What breaks if the champion changes next month?”
“What must be true before AE steps back?”
If answers are fuzzy, mark checklist fail closed and list unblockers.
Timed steps: customer-facing kickoff (separate meeting)
Keep internal honesty and customer kickoff distinct.
- Reconfirm outcomes and success criteria with the customer.
- Introduce CS/delivery owners and escalation path.
- Align on timeline, inputs the customer owes, and early risks.
- Capture new promises live into the log (do not leave them in chat only).
Checklist fields (AE / CSM / delivery)
AE section: problem sold; products/skus; commercial summary; promises log; stakeholders; competitors displaced (facts only); landmines; intro plan.
CSM section: success plan draft; onboarding owner; QBR or review cadence if used; health signals you will watch (define locally; do not invent benchmarks here).
Delivery section: scope boundaries; integration owners; environment prerequisites; timeline confidence; change-request path.
Promises log fields
Promise | Source (email/call/order) | Customer expectation | Owner after handoff | Due / milestone | Risk if missed
RACI lite for handoff tasks
| Task | AE | CSM | Delivery | Finance |
|---|---|---|---|---|
| Checklist completion | A/R until transfer | C | C | C as needed |
| Promises log accuracy | A | C | C | I |
| Kickoff scheduling | C | A | R | I |
| Commercial exceptions | C | I | I | A/R per policy |
Refine with RACI lite if ownership fights appear.
Required output
- Completed checklist (or explicit fail-closed with unblockers).
- Promises log.
- Owner map.
- Kickoff date on the calendar.
- Open risks with owners and dates.
Measuring handoff quality without blame theater
Use process signals: checklist complete before kickoff; promises logged; AE attended intro; risks named before go-live; fewer “I never heard that” escalations in the first phase. Do not invent churn percentages tied to handoffs unless you have sourced internal data.
When handoffs keep failing across deals
Managers should look at system causes: late-stage overpromising, no promises log standard, CS pulled in too late, or incentives that reward close over transfer. Fix the play adoption and approval gates; do not only coach the last AE who stumbled. Pair with Help This Deal by Role so late-stage helpers do not create undeliverable commitments.
Motion adaptations
- Enterprise: heavier security and stakeholder map; formal kickoff.
- Services-led: scope and change-request path are the ceremony center.
- PLG / high velocity: shorten the meeting; keep the gate question and a minimal promises log in the CRM; do not skip ownership naming.
Watch-outs
- Document dump with no conversation.
- Surprise discounts or side promises missing from the log.
- Unowned integrations.
- Champion departure with no backup.
- AE disappearing before success criteria are shared with the customer.
- Pretending one handoff model fits PLG, enterprise, and services equally.
Next links
Cluster article: Sales to CS handoff. Sales hub: How Sales Works. Ownership: RACI lite. Cross-functional: How Departments Work Together.