Most sales handoffs pass along account facts and leave the reason the customer bought in the seller's head. This one carries the business case, the people who own it, and what they were promised.
A sales-to-customer-success handoff should carry the customer's reason for change, not just account facts. That means four things: why they bought and what they expect (the problem, the executive priority in their words, and the business case), who owns it and what each person is worried about, what was promised technically, and the risks and next steps that could affect success.
Placeholder answer
Short, practical frameworks for executive messaging, business cases, multithreading, and sales enablement.
In a lot of handoffs, what crosses over is the account record: the contract value, the products purchased, the contacts, and a kickoff date. The reason they bought stays with the seller. Which is how the customer success team ends up opening the kickoff by asking the buyer to explain their goals again, and the champion who built the case gets to start over with a new team.
So a good handoff carries four things, one per section of the doc below: why they bought and what they expect to get, who owns it, what was promised, and what could get in the way.
Start with a one-liner that says why this customer bought, in a sentence anyone on the account team could repeat. Something like, "Implementing to reduce support costs by 30% before holiday season peak." Then fill in four sections.
1. Strategic context: why they bought, and what they expect. This is the business case, carried over:
2. Contact map: who owns it. Everyone involved, with their title, role in the purchase, influence, and notes. Then go deeper on the people who matter most:
3. Technical requirements: what was promised.
4. Risks and opportunities: what could get in the way.
Because customer success is one of the teams the business case was written for. In Selling With, I described what each part of the revenue team gets from it, and for customer success, it's "a specific recap of what's promised to the customer." Which means most of the handoff is written before the contract is signed.
So whatever their executive calls the project, your CS team calls it that on the first kickoff call too (the forwardable emails guide covers why their internal language matters so much). The metrics in the business case are what the executive will judge the project on, so they should become the first measurable outcome your CS team works toward, the same way they're the last row of a good mutual action plan. And the custom work that was promised and the champion's biggest fear both go on page one, where the team running the rollout will see them first.
Earlier than most teams start it. One play from Selling With, the "Account Team → Rep → Buyer" email, is crazy effective when it's executed well on a high-value, late-stage deal:
Say you're selling to an operations team that doesn't have a master data hierarchy, which throws off their segmentation. You and your team adapt a sample hierarchy from another account, and set up a working session to refine it with them. Here's what your account team would send you to forward:
Subject: Meeting [Buyer's Name]
Hey [Sales Rep], how's it going with [Prospect]? I know they're not a customer or anything yet. But from what you shared, I can't wait to work with them. Think they'd be open to connecting with me next week?
Most [role, e.g., marcomm] teams at this stage [problem, e.g., don't have a master data hierarchy]. Since that's the case for them too, we can use this [framework] to start building theirs out. It'll either make their onboarding easier or help them out even if they don't end up working with us. Think they'd be open to it?
\- Account team
It's effective because I can almost guarantee no competitor is doing this. It shows your buyer there's a whole team thinking about them, and it actually "adds value." Plus, it sets up a smooth handoff and implementation. And if you use it on several deals, by the way, put some of that commission check toward dinner for your colleague.
Ask your champion once the deal is signed: what did they do that you didn't see? Pick a deal that just closed with a champion who was open and transparent with you, write up the decision process as you understood it, and send something like this:
Subject: Process Feedback
[Champion], thrilled we get to work together now. All because of what you've been doing behind the scenes! There was definitely room for me to have been a stronger partner for you, too. So I'm wondering, open to helping me understand the work you were doing internally? The emails, conversations, docs I never saw, but I know you worked hard on. It'd be interesting to compare how I think your team evaluated us (attached), to how you all actually did. Lunch on me if you're up for it?
It'll show you how your buyer's internal sale really went, which makes you a sharper seller on the next deal. So share what you learn with your CS team, too, since they're about to work with the same people.
Good, keep it. The handoff gives that process what it can't get on its own: what this specific customer is trying to accomplish, in their words, and who's on the hook for it.