Sales to CS handoff checklist
Most customers tell their story three times: once to sales, once to the onboarding team, and once more to their CSM, because nothing useful was written down in between. Worse, the promises made during the deal (a custom field, an integration date, a discount at renewal) surface months later as surprises. This checklist makes the handoff a gate: the opportunity cannot move to onboarding until sales has documented what the customer bought, why, and what they were told.
Download it
What you get
- A handoff record with the fields sales must complete before closed-won is processed
- A commitments log for anything promised that is not in the standard product or contract
- A success criteria table that turns the business case into measurable onboarding goals
- A handoff meeting checklist and a send-back rule when the record is incomplete
Who it's for
- CS ops and onboarding leads tired of re-running discovery
- Sales leaders who want renewals to go smoothly for their reps
- RevOps teams building the closed-won to onboarding workflow
What's inside
6 sections, each listed with its own size. The first is previewed below; the remaining 5 come with the download, with blank rows ready to fill in.
| Section | Size | Previewed |
|---|---|---|
| Handoff record | 9 fields to complete | Below |
| Commitments log | 6 columns, 3 worked example rows | In the download |
| Success criteria | 6 columns, 3 worked example rows | In the download |
| Handoff gate | 9-point checklist | In the download |
| Handoff call agenda (30 minutes) | 6-point checklist | In the download |
| Why handoffs fail and how the gate fixes it | Guidance notes | In the download |
Preview of section 1
Handoff record
Completed by the AE before the deal moves to onboarding. Use the customer's words where possible.
- Why they bought
- e.g. Managers rebuild the forecast by hand every week and the CFO no longer trusts the number
- What they bought
- e.g. Forecasting module, 60 seats, 24-month term, starts 1 November
- Business outcome they expect
- e.g. Forecast within 10% of actual by end of second quarter
How to use it
1. Make the handoff record a required step at closed-won
Build the fields into the opportunity or a linked handoff object and block the move to onboarding until they are complete. A handoff that depends on an AE remembering to send a note will not happen at quarter end.
2. Log every non-standard commitment
Anything promised that is not in the order form or standard product goes in the commitments log: roadmap items, custom work, pricing at renewal, named support contacts. If it is not in the log, CS is not bound by it, and the AE should know that before they promise it.
3. Hold a 30-minute handoff call
Bring the AE, CSM, and onboarding lead, and walk through the record, not the deck. The CSM should leave able to explain why the customer bought and what success looks like at 90 days. For large deals, invite the customer's champion to the second half.
4. Let CS send it back
If the record is incomplete, CS returns it with the missing fields named and the AE has two business days to fix it. Track send-backs by AE and review them with sales leadership monthly; the pattern usually sits with a few reps.
Frequently asked questions
What should be included in a sales to customer success handoff?
Why the customer bought, what they bought, the outcome they expect, the sponsor and champion, other stakeholders, integrations, competitors evaluated, risks, renewal terms, and a log of any non-standard commitments. Success criteria with a baseline and date turn that into something CS can measure.
When should the sales to CS handoff happen?
The record should be complete at signature, and the handoff call should happen within five business days. For long or complex sales, introduce the CSM before signature so the customer meets them during the deal.
Who owns the handoff, sales or CS?
Sales owns completing the record; CS owns accepting it. RevOps owns the workflow that enforces the gate. Splitting it this way means neither side can blame the other for a missing field.