A sales to customer success handoff needs seven things before the kickoff: the customer's goals in their own words, who signed and who will use it, every promise beyond the order form, what was demoed, the risks and who voted no, their deadline and why, and the commercial terms. Put them on one page, confirm them with the AE in a 20-minute call, and run the kickoff from that page.
Your sales to customer success handoff is a Slack message. The deal closes, the AE adds you to a channel with the company name, and the CRM has the contract value, the term, a main contact and a stage history. What it does not have is why they bought, what problem they were trying to solve, who else was in the room, and what they were told. You find those out over the first three calls, and the customer notices that you are asking questions they answered two months ago.
This page is the checklist for the onboarding manager or Head of CS setting the handoff up for the first time, or replacing the one that exists on paper and not in practice. It gives you the seven things sales must share, the 20-minute call that confirms them, what belongs in the CRM versus the handoff doc, and the rule for when the AE stays on the account.
- The CRM holds facts (contract, contacts, stage history). The handoff needs decisions and commitments: why they bought, what was said, who is sceptical. Those live in a one-page doc the CSM drafts and the AE corrects.
- Write the goal in the customer's words, verbatim from a call or email. 'Improve efficiency' is the AE's summary; 'stop our analyst rebuilding the CSV every Monday' is a goal you can be measured against.
- Every promise beyond the order form gets its own line with where it was said. The kickoff where the customer says 'we were told X would be included' is the most common handoff failure in the threads we read, and it is entirely preventable.
- The handoff call is 20 minutes, the CSM drafts before it, and the AE signs off within 24 hours. The AE stays involved only while an open promise, a sponsor relationship or a dated expansion path needs them.
- Book the kickoff on the closing call, not after the handoff. A date agreed before signature is part of the purchase; one requested a week later is a favour.
Questions this page answers
- what should sales share with customer success before handing over a customer
- sales to CS handoff checklist or template
- what do you keep outside the CRM and does it survive a handoff
- customer says sales promised a feature we don't have
- how long should the AE stay involved after the deal closes
- what questions should I ask the AE on a handoff call
- Why is the CRM record not a sales to customer success handoff?
- What seven things must sales share on the handoff?
- What happens on the 20-minute handoff call, minute by minute?
- What lives in the CRM, and what lives in the handoff doc?
- When should the account executive stay involved?
- What does a filled handoff doc look like?
- How do I know the handoff is working?
- How does GainTrace carry the handoff into the account?
Why is the CRM record not a sales to customer success handoff?
The r/CustomerSuccess thread this page answers asked what people want from sales, and the poster's description of the current state will be familiar.
“Sometimes you get the company details, contract information, and the main contact, but you still have to spend a few conversations finding out why they bought, what problem they were trying to solve, who else was involved, and what they expect from the product.”
The CRM is not bad at this by accident. Its fields move a deal forward: stage, amount, close date, next step. After the close they have done their job. The context a CSM needs was never a field; it was in the discovery recording, the pricing thread and the AE's head. A second thread, from someone who had watched it at several companies, put the consequence in one line.
“Deal closes. AE moves on. CSM gets added to a Slack channel with zero context. Then on the kickoff call the customer says 'wait, we were told X would be included' and the CSM has no idea what X is.”
The corpus says this is a pattern. Of 946 r/CustomerSuccess threads we read, 28 are about a handoff or handover and 27 involve something a customer says was promised, oversold or missold. Among 3,628 public G2 reviews of the three most-reviewed customer success platforms, 25 name handoffs or transitions as the problem the buyer wanted solved, and 80 name account notes. People buy software to fix a handoff a one-page document would have fixed, because nobody agreed what the page should say.
The fix is a document shaped differently from the CRM record: decisions and commitments, dated, in the customer's words where possible, drafted by the CSM and corrected by the AE. The rest of this page is what goes on it; the customer onboarding best practices post covers what follows.
What seven things must sales share on the handoff?
The handoff seven are the items a CRM record cannot carry: the business reason for buying, the metric the buyer named, who else was in the room, what was promised outside the order form, the deadline they said they had, the objection they raised last, and how they want to be contacted. A handoff without them is a data transfer.
Each item has a test for 'done'. If the AE cannot pass the test, the item is not handed off, it is guessed, and the guess will surface at the kickoff.
Before the kickoff is booked, the handoff doc contains
- Goals in the customer's words. One to three sentences quoted from a call or email, dated. Test: a CSM who has never met the account could read it back to the sponsor and get a nod. 'Improve efficiency' fails; 'stop our analyst rebuilding the CSV every Monday' passes.
- Who signed and who will use it. Four names, which may overlap: the economic buyer, the signer, the champion who ran the evaluation, and the day-to-day owner who will configure and use it. Plus whoever voted no or went quiet. Test: the kickoff invite goes to the right person first time.
- What was promised. Every commitment beyond the order form (a feature, an integration, a timeline, a service, a named person), one line each, with where it was said and whether it is in writing. Test: nothing the customer says 'we were told' on the kickoff is missing from the list.
- What was demoed. Which features, on which data, and anything shown that was mocked up, on a roadmap build or configured beyond what they bought. Test: the CSM knows which screens the customer expects on day one and which they will not get.
- Risks. The tool they are leaving and why it failed, the competitor they nearly chose, procurement or security friction, and any stakeholder who resisted. Test: the CSM can name the one thing that would make this customer regret the decision in month three.
- Timeline. Their deadline and why it exists: an old contract ending, a board date, an event, a hire starting. Test: the go-live date is the customer's date, and the CSM knows what happens on their side if it slips.
- Commercial terms. ARR, term, payment schedule, the discount and its condition, auto-renew and notice period, seat or usage caps, and the expansion path the AE sold. Test: the CSM can answer 'what happens when we hit 50 users' without looking it up.
The first item is the one most often faked, because an AE writing it after the fact paraphrases. Lift the quote from the recording or the email. It is also the item with the longest life: the CSM who asked what survives a handoff described a renewal wobble six months in where nothing in the CRM answered "what they wanted, what we promised, and what changed since". The goal line answers the first, the promises list the second, and a dated line of decisions the third.
The third item is where the money is. The r/CustomerSuccess thread about a customer adamant a feature was promised describes a CSM who went through the demo recordings, found nothing that was not in the product, shared them, and still had an angry customer and a founder pushing to build it anyway. A promises list agreed with the AE before the kickoff settles that argument on day one instead of month three. When it has already started, the customer says a feature was promised page covers the conversation.
What happens on the 20-minute handoff call, minute by minute?
The call works when the CSM has already drafted the doc from the CRM, the order form and the last two call recordings or notes, and the AE's job is to correct it. An AE asked to author a handoff from a blank page produces the CRM record again. An AE asked to correct a draft produces the story.
Before the call: the CSM drafts the page
Thirty minutes, the day the deal closes. Pull the order form, the CRM record and the last discovery and pricing calls. Fill the seven items and mark every guess with a question mark. Send the draft with the invite so the AE reads it before the call.
Minutes 0 to 3: the deal in the AE's words
One question: tell me the story of this deal from first call to signature. Do not interrupt. The story contains the goal, the sceptic and the near-miss, in a form no CRM field allows.
Minutes 3 to 8: goals and people
Read the goal line back and ask whether the customer would recognise it. Confirm the four names and the no-voter. Ask who the AE would call if the sponsor stopped replying; that name is often not in the CRM.
Minutes 8 to 13: promises and demos
Read the promises list line by line; the AE confirms, corrects or adds. Ask directly: is there anything you said might be possible, or showed, that is not on this list? Then ask what was demoed that the customer did not buy. Write additions down on the call.
Minutes 13 to 16: risks
What nearly lost this deal, what tool are they leaving and why, and who on their side will be looking for a reason to say this was a mistake. The AE knows; nobody has asked.
Minutes 16 to 19: timeline and terms
Confirm their deadline and its reason. Walk the terms once, with attention to the discount condition and the expansion path, the two the customer will raise at renewal.
Minutes 19 to 20: the kickoff and the intro
Confirm the kickoff date, which should already have been agreed on the closing call (see customers not showing up to onboarding), and that the AE sends the intro email today naming the CSM and the date. Ask for a 'confirmed' reply on the doc within 24 hours.
After the call: the page goes on the account
Link the doc from the account record, share it with the AE and onboarding, and run the kickoff from it. Anything the customer raises that is not on the page is added, dated, with the AE copied.
What lives in the CRM, and what lives in the handoff doc?
They have different lifetimes and different authors. The CRM record is authoritative for facts and is updated by systems. The handoff doc is authoritative for decisions and commitments and is edited by one person, in place, so it stays one page.
| Item | CRM | Handoff doc | Why the split |
|---|---|---|---|
| ARR, term, close date, payment schedule | Yes, the source | Summarised once | Systems keep it current; the doc would go stale |
| Contacts and titles | Yes | The four roles and the no-voter | The CRM has 14 contacts; the doc says which four matter and why |
| Goal in the customer's words | A 'use case' picklist at best | Yes, verbatim, dated | Picklists paraphrase; a renewal conversation needs the quote |
| Promises beyond the order form | No field for it | Yes, one line each, with where it was said | A promise with no home becomes a dispute |
| What was demoed | No | Yes | Expectation gaps on day one come from here |
| Risks and the sceptic | A risk flag or a score | The reason behind the flag | The flag tells you to worry; the doc tells you what about |
| Timeline | Go-live date | The customer's reason for the date | Slips are negotiated on the reason, not the date |
| Decisions and commitments since close | Activity log, append-only | One running line, dated, edited in place | The log is for audit; the line is the only thing anyone rereads |
| Product gaps found at handoff | No | Flagged here, logged in the feedback intake | Product needs it ranked with ARR; the doc needs it as a promise or not |
“What we write after a call gets shaped by the CRM fields, so it comes out as sentiment, next steps, maybe a summary. Six months later when a renewal wobbles, none of that answers the question you actually have, which is what they wanted, what we promised, and what changed since.”
The last row matters. When the handoff surfaces a gap between what was sold and what exists, it goes in two places: on the doc as a promise (or explicitly not one), and in the shared feedback intake so product sees it with the ARR attached. The customer feedback to product page has the intake fields and the rule that promised items rank separately.
When should the account executive stay involved?
The default: the AE sends the intro email the day of the handoff call, joins the first ten minutes of the kickoff to hand the relationship over in front of the customer, and is then out of the day-to-day. Less than that and the customer feels dropped; more and the customer keeps emailing the AE, who keeps answering, and the CSM never becomes the owner.
The AE stays involved past the kickoff only while one of four conditions holds, and the doc says which.
- An open promise beyond the order form. The AE is on the conversation that resolves it, in writing, because they made it. Once the resolution is dated on the doc, they are off.
- A sponsor relationship only the AE has. If the economic buyer has never spoken to the CSM, the AE stays until one direct sponsor call has happened, which should be inside the first two weeks.
- A dated expansion path inside the term. If the AE sold 'we will add the second team in Q2', they own that conversation when Q2 arrives, with the CSM setting it up on usage evidence. The cross-sell playbook covers the handoff rule in the other direction.
- Risk in the first 30 days. No kickoff held by day 10 or no login by day 14 gets one call from the AE to the sponsor, because the AE's relationship is still the warmer one. After that it is a CS motion.
Compensation decides whether the rule is followed. With a clawback for churn inside 90 days, AEs stay involved unasked and the risk is they stay too long. Without one, write the rule on the doc: 'AE stays on until the SFTP promise is resolved' is a sentence a sales manager can hold someone to. Whether CSMs should carry revenue themselves is argued on should CSMs be accountable for revenue.
What does a filled handoff doc look like?
Illustration: a 40-seat analytics subscription, $48k ARR, closed on a Tuesday
Goal (customer's words, discovery call, 14 July): "Our analyst spends Monday mornings rebuilding the export in Excel for finance, and the regional managers all share one login because we never set them up properly." People: economic buyer is the COO (approved, will not attend kickoff); signer is the finance director; champion is the ops manager who ran the evaluation; day-to-day owner is the analyst, who has not yet been told. No-voter: the IT lead, who wanted to build it internally. Promised beyond the order form: a scheduled export to their SFTP (said on the pricing call, 2 September, not in writing) and "we can get you live before your old contract ends" (email, 28 August). Demoed: the regional dashboard on our demo data; the custom export was shown from a roadmap build. Risks: leaving a spreadsheet, not a vendor, so nothing forces adoption; IT lead will look for a reason. Timeline: old contract ends 31 October, so live by 24 October; if it slips the analyst keeps the Excel process, which is survivable but embarrassing for the champion. Terms: $48k, 12 months, annual upfront, 15% discount conditional on a case study by month six, auto-renews with 60 days' notice, 40 seats with overage at list. AE stays on: until the SFTP export promise is resolved in writing with the ops manager. Kickoff: agreed on the closing call, Thursday next week, analyst and ops manager invited. About 200 words, one page; the CRM record for the same account is 14 contacts and 31 activities and answers none of the questions the kickoff will raise.
Everything on that page is something the CSM would otherwise have discovered on a call, usually the wrong one: the SFTP promise from the analyst in week three, the discount condition from finance at renewal, the IT lead as an unexplained cooling in month two. For enterprise accounts, the goal line becomes the first row of the mutual success plan and the promises become dated rows in it.
How do I know the handoff is working?
Four numbers, kept on a sheet if that is what you have, reviewed monthly by the Head of CS with the sales manager in the room.
- Kickoffs where the customer raised something not on the handoff doc. Target zero. Every one is a line added to the doc and a conversation with the AE about why it was missing.
- Days from close to a confirmed handoff doc. Target two. Past five, the AE has moved on and the story is degrading.
- Open promises past 30 days. Each is a dispute waiting for a renewal. Report them by AE.
- Calls the CSM spent re-discovering what sales already knew. Count for one month. The thread this page answers put it at 'a few conversations' per account; at 20 new accounts a quarter that is a week of CSM time asking questions the customer already answered.
The same doc survives the next handoff, from CSM to CSM when books are rebalanced or someone leaves. The poster who kept a running line of decisions outside the CRM had solved it for themselves, not the team: "That file is still mine, in my words, so when an account moves to another CSM they mostly start from zero no matter how full the CRM looks." A doc on the account record, in the seven-item shape, in the customer's words rather than the author's, is the version that survives. An enterprise CSM among the G2 reviewers described being "able to handoff accounts with clear and transparent account notes, key contacts, renewal details" with less "internal back and forth". For them it was a platform feature; for most teams it is a template and a rule.
When the handoff is clean and the customer still stalls after the kickoff, the problem has moved to value delivery, and onboarding complete but the customer churned is the next page.
How does GainTrace carry the handoff into the account?
GainTrace pulls the contract, contacts and stage history from the CRM automatically, so the handoff doc only has to hold what the CRM cannot: the goal, the promises, the sceptic and the dated line of decisions, all on the account alongside billing, usage and support. Product signals show whether the day-to-day owner named on the doc has logged in by day 14, and customer success on GainTrace covers how an open promise or a missed kickoff becomes a task with a date and an owner, without an admin building the workflow.
Frequently asked questions
What should sales share with customer success before handing over a customer?
What questions should a CSM ask the AE on a handoff call?
How long should the AE stay involved after the deal closes?
Should the handoff live in the CRM or in a separate document?
What do I do when the customer says sales promised something that is not in the product?
Does a sales to CS handoff template also work for handing accounts between CSMs?
How this was researched
We read 946 r/CustomerSuccess threads and pulled the ones on the sales-to-CS handoff, what CSMs keep outside the CRM, CSM-to-CSM account handovers and customers who insist a feature was promised; the quotes and counts above come from those threads and are linked below. We read 3,628 public G2 reviews of the three most-reviewed customer success platforms and counted the reviews naming handoffs, transitions or account notes as the problem the buyer wanted solved. The filled handoff doc is an illustration with stated figures, not a customer's data.
- r/CustomerSuccess: What do you really want Sales to share with you before passing on a customer?
- r/CustomerSuccess: What do you keep outside the CRM, and does it survive a handoff?
- r/CustomerSuccess: How do you handle the Sales to CS handoff at your company?
- r/CustomerSuccess: How to deal with clients who are adamant that we have promised them features that our product does not have?
- r/CustomerSuccess: Best Practices for CSM Account Handover + AI-Powered Transition Docs?
- G2: Customer Success software category (source of the 3,628 public reviews)
Draft the seven-item page for your next closed deal before you book the handoff call, then see the promises, the owner and the kickoff date tracked on the account automatically. Start free or book a demo.
See GainTrace first in your Google results
Add as a preferredsource on Google