Starts when the deal closes
Start the checklist from your CRM’s closed-won event through the API and webhooks or Zapier, and every due date counts from the signature. Tasks go to the account executive, CSM and CS lead from the role fields.
Sales to Customer Success Handoff Checklist Template
The customer told sales everything once. If the first thing the CSM asks is what they are trying to achieve, the handoff has already failed.
This free template is for account executives, customer success managers and the CS leads who manage both sides of the handoff. It runs from the signed order form to the moment the CSM owns the account: a complete deal record, the customer’s goals in their own words, the stakeholders, every promise made during the sale, an internal handoff meeting, a warm introduction and a check 30 days later that nothing was lost. Two scope questions tailor each run. A deal with non-standard terms or commitments shows a legal and product review task, and a customer who needs an implementation project shows the phase that hands the account to the implementation team.
Why Handoffs Fail, and Where This Checklist Stops
A handoff fails in one of three ways. The information never moves: the CSM gets a CRM link and a two-line note, and the customer is asked at kickoff to repeat what they told sales. The information moves but is wrong: the record says 50 seats when the order form says 40, or the renewal date is the signature date rather than the start date. Or a promise moves only in the account executive’s memory: the integration that was “on the roadmap”, the discount that ends after year one, the response time agreed in an email thread. That last kind does the most damage, because the customer remembers it and the CSM has never heard of it.
The fix is a fixed list of what must be written down before the CSM accepts the account, a short meeting to walk through it, and a check 30 days later. This template is that list. It stops when the customer has met their CSM and the next stage is running.
Treat the handoff as part of the sale rather than admin after it. Account executives are usually paid on signature, so the record competes with the next deal for their time. Making acceptance a gate rather than a courtesy is what gets it done: until the CS lead accepts, the deal is closed but the handoff is still open, and both teams can see it.
Handoff
Sales to CS, inside your company
Starts at the signed order form and ends when the CSM has accepted the account, met the customer and booked the kickoff. It moves facts, promises and relationships from one team to another.
Onboarding
The customer reaches first value
Starts at kickoff: account set-up, training and the first real workflow. Run it with the SaaS Customer Onboarding Checklist or, for small accounts, the Simple Customer Onboarding Checklist.
Implementation
A project with workstreams
Enterprise deals with a security review, single sign-on, integrations or data migration. Phase 5 here hands over to the Enterprise Customer Implementation Checklist.
What the Sales to CS Handoff Checklist Covers
Seven phases run from the signed order form to a 30-day check that nothing was lost. Phase 5 appears only when the customer needs an implementation project, and the legal and product review task in Phase 2 appears only when the deal included non-standard terms or commitments.
Close
Phase 1: Confirm the Close
Start this checklist the day the order form is signed, not when the CSM has time.
- Name the account executive, CSM and CS lead — later tasks and the handoff approval are assigned from these fields
- Answer the scope questions — did the deal include non-standard terms or commitments, and does the customer need an implementation project
- Confirm the deal is signed, not just agreed — an executed order form or contract, and a closed-won opportunity that matches it
- Create the customer record in the CS system — linked to the opportunity, with the CSM as owner
- Set the handoff meeting date — within the first week, so the customer is not left waiting for the CSM to catch up
Deal
Phase 2: Complete the Deal Record
- Record what was sold — plan, seats or licences, modules, add-ons and any services hours
- Record pricing, discounts and when they end — a first-year discount that lapses at renewal is a conversation the CSM needs to plan for
- Record the contract dates — start date, term, renewal date, notice period and whether the contract renews automatically
- Attach the signed documents — order form, master agreement, DPA, security addendum and any side letter
- List every promise made during the sale — roadmap items, custom work, integrations, response times and anything agreed by email or on a call
- Send non-standard commitments for legal and product review — shown only when the deal included them; each gets an owner and a yes, a no or a date
Context
Phase 3: Capture Goals, People & Risks
- Write the customer’s goals in their own words — quote the discovery notes rather than translating them into your product’s language
- Agree measurable success criteria — what the customer will look at in 90 days to decide whether this worked
- Map the stakeholders — economic buyer, champion, day-to-day admin, end-user leads and anyone who argued against the purchase
- Record the technical environment — systems in use, identity provider, data sources and the integrations the customer expects
- Note why they bought now — the deadline, event or pain that made this quarter the one; it sets the onboarding priority
- Flag the risks — a busy champion, a sceptical team, a tight deadline or a competitor they nearly chose
Handoff
Phase 4: Run the Handoff Meeting
- Hold the internal handoff meeting — the account executive walks the CSM through the record, with the order form on screen
- List the CSM’s gaps and questions — the account executive answers them in writing within two working days
- CS lead approval of the handoff — accepts the account, or returns it with the gaps that must be filled first
- Agree the account executive’s role after close — who handles escalations, the executive relationship and expansion
Implement
Phase 5: Hand Over to Implementation
Shown only when the customer needs an implementation project.
- Name the implementation lead — and check their availability against the customer’s timeline
- Share the technical discovery and scoping notes — so the implementation team does not rediscover what sales already learned
- Check the implementation scope against what was sold — workstreams, services hours and dates; raise any gap before the customer hears a different plan
- Start the Enterprise Customer Implementation Checklist — with this handoff record attached
Intro
Phase 6: Introduce the Customer
- Send the warm introduction — from the account executive, naming the CSM and saying why they are the right person
- Book the kickoff — with the champion, the admin and, for larger accounts, the economic buyer
- Replay the goals at kickoff — read back the customer’s own words and ask what has changed since they signed
- Share the onboarding plan and first milestone — so the customer leaves the call knowing what happens next and when
Check
Phase 7: 30-Day Check
- Ask the customer whether anything promised is missing — a direct question, early enough to fix the answer
- Compare progress with the success criteria — on track, at risk or blocked, with the reason
- Rate the handoff with the CSM — what was missing, wrong or late, sent back to the sales leader
- Update the handoff template — add the question that would have caught this month’s gap
A Handoff Timeline From Signature to Day 30
The days below suit a mid-market deal. Set the template’s due dates to match your own sales cycle, but keep the order: the record is complete before the handoff meeting, and the meeting happens before the customer meets the CSM.
Day 0
Signed
The order form is signed and the opportunity is closed-won. The checklist starts, the roles are named and the scope questions are answered. The account executive thanks the customer and says a CSM will be in touch this week.
Days 1 to 3
Deal record complete
The account executive fills in what was sold, the contract dates, the promises and the customer’s goals while the conversations are fresh. Non-standard commitments go to legal and product.
Days 3 to 5
Handoff meeting and acceptance
Thirty minutes, account executive and CSM, record on screen. The CS lead accepts the account or sends it back with named gaps.
Days 5 to 7
Warm introduction
The account executive introduces the CSM by email or on a short call. Where an implementation project is needed, the implementation lead is introduced at the same time.
Days 7 to 14
Kickoff
The CSM replays the goals, confirms the stakeholders and shares the onboarding plan. The customer should hear nothing they have to correct.
Day 30
Nothing lost
The CSM asks the customer directly whether anything promised is missing and rates the handoff. Patterns go back to the sales leader.
What the CS lead checks before accepting. Acceptance is not a formality. The CS lead reads the record against the order form and sends it back if any of these is missing or does not match:
- Seats, modules and services hours agree with the signed order form
- The renewal date is calculated from the contract start date, not the signature date
- Every discount has an end date and every promise has an owner
- At least two named contacts, so the account does not depend on one champion
- Success criteria the customer would recognise as their own
Larger deals start earlier. For enterprise accounts many teams bring the CSM into late-stage calls, so the customer meets them before signature and the handoff meeting confirms what both already know. The checklist still applies; the record still has to be written down.
Why Run Sales Handoffs in CheckFlow?
A quality gate before the customer
The CS lead’s approval halts the checklist until the record is complete, so the CSM never meets a customer with half the story. Rejections and the reasons for them stay in the history.
The handoff sits between two other templates. Before it, the Sales Pipeline Stages Checklist defines what closed-won means. After it, the SaaS Customer Onboarding Checklist takes the customer to first value, or the Enterprise Customer Implementation Checklist runs the project for larger deals. Commitments made in a proposal belong in the deal record too; the RFP Response Checklist keeps them in one place.
Building a repeatable customer journey? CheckFlow for client onboarding runs the handoff, onboarding and implementation from templates, so every new customer starts with the same facts on file.
Frequently Asked Questions
What should a sales to customer success handoff include?
Everything the CSM needs so the customer never has to repeat themselves: what was sold, the price and any discounts with their end dates, the contract start, renewal and notice dates, the signed documents, and every promise made during the sale. Add the customer’s goals in their own words, measurable success criteria, the stakeholders and the technical environment, plus the risks the account executive saw and why the customer bought now.
When should the handoff from sales to customer success happen?
As soon as the contract is signed, and before the customer meets the CSM. Starting on the signature date catches the account executive’s memory while it is fresh and stops the customer waiting. A common pattern is a complete deal record within three working days, an internal handoff meeting by the end of the first week and a warm introduction straight after it. For larger deals, bringing the CSM into late-stage calls shortens the handoff further.
Who owns the customer after the handoff?
The CSM owns the relationship and the outcome from the moment the CS lead accepts the handoff. The account executive usually keeps a defined role: the executive relationship, escalations they can help with and, in many teams, expansion deals. Agree that split in the handoff meeting and write it down, so the customer knows who to call and two people are not contacting the customer about the same thing.
What is the difference between a sales handoff and customer onboarding?
The handoff moves information inside your company; onboarding moves the customer to first value. The handoff ends when the CSM has accepted the account and met the customer. Onboarding starts at kickoff with account set-up, training and the first real workflow. Enterprise deals with security reviews, integrations and data migration add a third stage, an implementation project, which usually runs before the customer is fully live.
Should the customer join the handoff meeting?
Not the internal one. The handoff meeting is where the account executive and CSM go through the record frankly, including the risks and the stakeholder who argued against the purchase, which is hard to do with the customer listening. The customer joins the warm introduction straight afterwards, where the account executive introduces the CSM and the CSM replays the goals so the customer can see nothing was lost on the way.
How do you stop promises getting lost between sales and CS?
Make listing them a required task and make the CSM’s acceptance depend on it. The account executive writes down every commitment made on calls, in emails and in the proposal, and anything non-standard goes to legal and product for a yes, a no or a date. At 30 days the CSM asks the customer directly whether anything promised is missing, while there is still time to put it right.
Is CheckFlow free for this template?
14-day free trial, no card required. The Business plan is $10 per user per month after the trial. Full details at checkflow.io/pricing.