A sales to CS handoff is the transfer of a signed deal from the account executive to the customer success or delivery team, with everything they need to start: what the customer wants to achieve, what was promised, who matters at the account and what must happen first. Done well, the customer never has to repeat themselves.
This guide is for account executives who close complex deals and then watch the first weeks of delivery go wrong, and for the sales managers who inherit the problem. It covers what to include, when to start, how to run the handoff and a checklist you can copy. In the UK, “handover” is the more common word. It means the same thing.
Key takeaways
- A sales to CS handoff transfers the deal's context, not just its contract: goals, promises, stakeholders, risks and open commitments.
- Forrester reports that 81% of B2B buyers express dissatisfaction with the provider they chose, so the weeks after signature decide whether the deal turns into a reference or a churn risk.
- The most expensive gap in a handoff is “what was promised”, because the customer remembers every promise and the CRM records few of them.
- A good handoff starts before closed-won, with a written brief, an internal handoff call and a joint kickoff where the account executive introduces the customer success manager.
- The same handoff discipline protects the account when an account executive changes territory or leaves the company.
What is a sales to CS handoff?
The sales to CS handoff is the moment a deal changes owner. Until signature, the account executive owns the relationship. After it, a customer success manager, an onboarding lead or a delivery team takes over. In IT services, the receiver is often a project manager or a delivery director rather than a CSM.
The handoff has two layers. The visible layer is the contract, the order form and a few CRM fields. The invisible layer is everything the account executive learned over months: why the customer bought, who argued against it, what the CFO needs to see by the first review and which promise was made on a call in week six. The first layer moves on its own. The second layer is the one that gets lost.
Why context gets lost between sales and customer success
Complex deals produce a lot of context, spread across a lot of people. Forrester's State of Business Buying 2024 reports that 13 people are involved in the buying decision on average, and that 89% of purchases involve two or more departments. Each of those people said something during the sales cycle. Most of it lives in calls, emails and the account executive's memory.
Customer success teams describe the result in plain terms. One team lead in an r/CustomerSuccess thread on handoffs wrote: “Someone closes the customer, then onboarding needs to figure out what was promised, who cares about what, whether anything weird came up during the sales process and what needs to happen next.” A reply in the same thread named where that context hides: “Half the important stuff isn't in the fields anyway, it's buried in what someone said three meetings ago.”
Three causes come up again and again:
- The CRM holds the deal, not the story. Stage, amount and close date are recorded. The buyer's reasons, doubts and side agreements are not.
- The account executive is already on the next deal. The handoff competes with a quarter that just started.
- Promises are spread across documents. The proposal says one thing, the statement of work another, and a follow-up email adds a third.
The cost lands on the customer first. In another r/CustomerSuccess thread, a CS lead described kickoff calls where the team arrived “with a name, a contract value, and maybe a sentence from the CRM about the use case,” and the customer's reaction: “these guys do not know what they sold me.”
What should a sales to CS handoff include?
Use this checklist as the template for your handoff brief. Every item answers a question the customer success team would otherwise have to ask the customer again.
| Item | What to capture | Why CS needs it |
|---|---|---|
| Business outcome | The result the customer bought, in their words and their metric | Defines what success means at the first review |
| Success criteria and dates | What must be true at 30, 90 and 180 days, and who judges it | Turns the outcome into milestones CS can plan |
| What was promised | Scope, timelines, integrations, custom terms, anything said on a call or in an email | The customer remembers every promise |
| What was not promised | Requests you declined or left for later, and why | Stops scope creep from looking like a broken promise |
| Stakeholders | Champion, economic buyer, daily users, blockers, each with their stance | Tells CS who to keep close and who to win over |
| Why they bought | The trigger, the alternatives considered, the reason you won | Shows what value to prove first |
| Risks and objections | Concerns raised during the cycle and how they were answered | The same concerns return during onboarding |
| Open commitments | Every action still owed, by either side, with an owner and a date | Nothing falls between teams |
| Commercial context | Renewal date, notice period, pricing concessions, expansion signals | Prepares the renewal from day one |
| Source documents | Proposal, statement of work, business case, security answers, key call recaps | Lets CS check the brief against the source |
Two items deserve extra care. “What was promised” is where most handoffs fail, so check it against the contract and the statement of work line by line. “Why they bought” is the most underrated item: if the customer chose you to cut reporting time, the first value CS proves should be reporting time, not the feature the onboarding script starts with. If you built a business case with the champion, attach it. It holds the figures the customer will measure you against.
When should the handoff start?
Start before the deal closes. A handoff that begins after signature starts with a gap of days, sometimes weeks, while the customer waits for someone to call.
Three moments work well:
- When the close plan is agreed. If your close plan already lists implementation and go-live, name the customer success owner in it.
- Before closed-won. Some teams make the handoff brief a required step to mark the deal won. The CS lead in the thread above said completion went “from maybe 20% completion to basically 100%” once the brief was required to close.
- On large deals, before signature. Introducing the customer success manager during late-stage meetings shows the buyer who will own the relationship and lets CS hear the promises first-hand.
How to run a sales to CS handoff in five steps
- Draft the brief from the sources. Use call recaps, emails, the proposal and the CRM, not memory. Fill every item in the checklist, and write “unknown” where you do not know.
- Check the promises against the paper. Read the brief next to the contract and the statement of work. Flag every promise that is not in the paper and decide now who honors it.
- Hold an internal handoff call. Thirty minutes between the account executive and the receiving owner. CS asks questions; the account executive answers and corrects the brief.
- Run a joint kickoff with the customer. The account executive opens the call, recaps the goals in the customer's words and hands over to the customer success manager. The customer sees continuity instead of a new vendor.
- Stay reachable for an agreed period. Agree how long the account executive stays involved, for example until the first value milestone, and for which questions.
One CS leader in the first thread summed up what to automate and what not to: gathering the data, yes; confirming it, no. In their words, “summaries drift from the source, and ‘what was promised’ is the field where drift costs the most, because it's the one the customer remembers.” Whatever tool drafts the brief, a person who was in the deal confirms it.
Example: the handoff brief for Helix Logistics
Helix Logistics is a fictional account. Marta, the operations director, signed on June 30. Here is the brief the account executive prepared before the internal handoff call.
- Business outcome: cut the time to answer carrier tenders from five days to two, before the autumn peak.
- Success criteria: first tender answered with the new process by August 15; Marta reviews results with the CFO in October.
- What was promised: integration with Helix's transport management system by go-live; a training session for the tender team in French and English.
- What was not promised: a custom dashboard for the CFO, requested in May and moved to phase two.
- Stakeholders: Marta (champion, strong); the CFO (economic buyer, cares about cost per tender); the IT lead (cautious, raised the integration question twice).
- Why they bought: their current process missed two tender deadlines last year; we won against an internal build because of the timeline.
- Risks: the IT lead's integration concern; the tender team's workload in September.
- Open commitments: we owe the final security answers by July 7; Helix owes the user list by July 10.
- Commercial context: renewal on June 30 next year; 60-day notice; a second region is a possible expansion.
The brief tells the customer success manager what to do first: secure the integration with the IT lead, because that is both the main promise and the main risk.
When an account executive leaves: the same problem, bigger
Sales managers face the same loss at a larger scale. When an account executive changes territory or leaves, every open deal and every recent customer loses its history at once. The relationship context, the stakeholder notes and the promises in flight go with them.
The fix is the same discipline applied earlier. If every deal keeps its context in one place, with its stakeholders, commitments and documents, the next owner reads the deal instead of rebuilding it. Our guide to stakeholder mapping covers the part that is hardest to reconstruct: who supports you, who does not and why.
Hand over complex deals without losing context, with Cobl
A handoff is only as good as the context behind it. When that context is spread across calls, emails, documents and the CRM, someone rebuilds it by hand, under pressure, while the next quarter starts.
This is the work an AI sales agent is built for. Cobl, the AI sales agent for complex deals, keeps one record per deal so you can centralize deal context: the timeline, the stakeholders, the documents and the commitments on both sides. You can ask it what was promised and see the source. Once the contract is signed, Cobl hands the deal to delivery with the full context, then looks for the next opportunity. You review what it prepares before anyone relies on it, and nothing goes to the customer without your approval. It works like an AI sales assistant on the deal: it prepares, you decide.
Move a live deal forward. Try Cobl free for 15 days.
.avif)
