As we made our final approach into Lisbon, it was 7:30 a.m. local time. The cabin temperature started to warm up, coaxing us out of our blankets. Soothing music played. Fresh orange juice was squeezed. This closed our flight in a way that started off the rest of our trip on a high note.
In sales, it's easy to feel like you're at the finish line once you sign the contract. But in reality, you've just brought the customer to their starting line. And in a lot of sales-to-CS handoffs, what crosses that line is the account record: the contract value, the products purchased, the contacts, and a kickoff date. The business case and the customer's true definition of "value" typically stay with the seller.
So inevitably, the CS team ends up opening the kickoff call by asking the buyer some version of their goals again, and the champion who built the business case feels like they're starting over from scratch.
Which is why a good handoff is built on four things, all covered in each section of the doc below:
(1) why they bought
(2) who owns the outcome
(3) what was promised, by when
(4) what could get in the way.
What should a sales-to-customer-success handoff include?
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 cut support costs by 30% before the 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:
- The problem statement: "Despite trying [failed solution], they still can't [desired outcome] because of [problem], costing them [quantified loss]."
- The executive priority: the exact internal phrasing, the name of the company-wide initiative it connects to, and any timeline constraints, like "must go live before Q4 peak season."
- The business case itself, linked, with the expected impact and how the project should move each core business metric.
2. Contact map: who owns it.
Everyone involved, with their title, role in the purchase, internal influence, and notes. Then, go deeper on the people who matter most:
- The executive sponsor: what's in it for them personally, how they like to be contacted, and what keeps them up at night.
- The primary champion: what's in it for them, what success looks like in their words, their biggest fear about implementation, and how much they trust you (and why).
- Other key people: the technical lead, the people who'll use it day to day, with their priorities and concerns.
3. Technical requirements: what was promised.
- Success milestones, and who owns technical decisions that drive those milestones.
- Required features versus nice-to-haves, and any custom work that was specifically discussed.
- Technical constraints: legacy systems, data migration needs, security and compliance requirements, and the existing tech stack.
- The success criteria, adoption targets, and how success will be measured by specific dates.
4. Risks and opportunities: what could get in the way.
- The risks that could affect success, each with its impact, an action item, and an owner.
- The next 30 days of tasks and the open questions, each with an owner and a date.
- The expansion opportunities worth revisiting later, and when to revisit them.
Why carry the business case into onboarding?
Because customer success is one of the teams the business case was written for.
In Selling With, I walked through each part of a solid business case, and one of them is a specific recap of what's been promised to the customer. Which means most of the handoff is written before the contract's 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 customer's executive will judge the project on (and therefore, the renewal), so they should be the first measurable outcome your CS team works toward, the same way they anchor a mutual action plan. Plus, any custom work that was promised with the investment, where the team running the rollout can see it all laid out.
Before you hand it over, ask yourself:
- Does customer success know this customer as well as I do?
- Have I thoroughly documented any concerns or unique needs my buyer has?
- Will the handoff I'm about to make keep up the momentum I've built?
When should the handoff start?
Earlier than most teams start it. One play I've been a big fan of for years is the "Account Team → Rep → Buyer" email, which is crazy effective when it's executed well on a high-value, late-stage deal:
- Partner with your account team (a CSM, AM, or solutions engineer).
- Pick a few late-stage deals, and detail each customer's current state.
- Find one way you both can help the buyer today.
- Give your teammate this email to send to you.
- Forward that email on to your buyer.
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 might adapt a sample hierarchy from another account, and set up a working session to refine it with them: the key is to deliver independent, standalone value they can use immediately, even before and regardless of whether they buy from you.
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?
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.
How do you align sales to what your buyers do internally?
During the handoff process and once the deal's signed, ask your champions: what'd they do that you didn't see?
Pick a deal that just recently closed with a champion who was generally open and transparent with you, then write up the decision process as you understood it, and send them 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, are you 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.
"Our CS team already has an onboarding process."
Great, keep it and build on it. The handoff framework gives that existing process a structure that's built around what this specific customer is trying to accomplish, in their words, and who's on the hook for it.
So pick the next deal that's about to close and write its one-liner, why they bought, in a sentence your CS team could repeat on the kickoff call. If you can't, the handoff isn't ready yet.