From Closed-Won to Live Customer: The Sales-to-Success Handoff

A customer signs. The rep celebrates, updates the CRM and moves on to the next deal. A few days later, someone from onboarding sends a welcome email and books a kickoff call. In that call, the customer explains everything again: what they bought, why they bought it, what they were told it would do and when. Sometimes what they were told does not quite match what the product does. Six months later, the account is at risk and nobody is sure why.

This pattern is common enough that the authors of one of the best-known books on the subject put it first. In Customer Success, published by Wiley in 2016, Nick Mehta, Dan Steinman and Lincoln Murphy set out ten laws of customer success. The first is "Sell to the Right Customer". The second is that the natural tendency for customers and vendors is to drift apart. The third is that customers expect you to make them wildly successful.

All three are decided, or at least strongly influenced, by sales. Who you sell to, what you promise and how much you tell the team that delivers it shape the customer's first months more than any onboarding email.

It is easy for a rep to think of churn as somebody else's problem. Commission is usually paid on the signed contract, and the renewal is a year away. But retention matters to sales for practical reasons.

In a widely cited 2001 Bain & Company brief, Frederick Reichheld reported that in financial services a 5% increase in customer retention produced more than a 25% increase in profit. The figure comes from one industry and an earlier era, so do not apply it to your company as if it were a law. The underlying point holds for SaaS, though: a customer who stays and grows is worth far more than one who leaves after a year, and replacing lost revenue is expensive.

More directly, retained customers produce references, case studies, expansion deals and introductions. A rep whose customers succeed finds the next deals easier to win. A rep whose customers churn hears about it in every reference call.

The most important thing a salesperson knows about a new customer is what the customer is trying to achieve. Lincoln Murphy calls this the customer's Desired Outcome, and in a 2016 article he describes it as having two parts: what the customer needs to achieve, and how they need to achieve it. He originally called these the Required Outcome and the Appropriate Experience; he has since renamed the first part a Goal.

Both parts matter in a handoff. Suppose a customer buys a help-desk tool because they need to cut the time it takes to answer customer emails in half before their busy season. That is the goal. But they also told your rep that their agents are not technical, that IT can only give them two hours of help, and that their director wants a weekly report. That is the appropriate experience. An onboarding plan that achieves the goal but needs a week of IT time will still feel like a failure to this customer.

Murphy's point is that customers choose you not only because they believe you can deliver the result, but because they believe you will deliver it in a way that suits them. Your rep knows a lot about both. If it is not written down and passed on, it is lost.

A handoff document should be short enough to read in five minutes and specific enough that the customer never has to repeat themselves. A useful template:

1. The goal: what the customer is trying to achieve, in their words, with a measurable target and a date if they gave one.
2. Why now: the event or problem that triggered the purchase.
3. How they need to get there: constraints on time, people, technical skills, IT involvement and anything else that shapes the right onboarding approach.
4. The people: the champion, the budget owner, the day-to-day users, any skeptics, and who has to approve changes. Include what each person cares about.
5. What was promised: features, integrations, timelines, service levels or anything else the customer was told. Be honest, including anything that was said loosely.
6. What was not promised: requests you declined or pushed to later, so nobody accidentally commits to them.
7. Risks: concerns raised during the deal, objections that were never fully resolved and anything that could make adoption hard.
8. The first milestone: the first concrete result that will show the customer the purchase is working.

The section on promises is the one reps most often skip, and the one that matters most. If the customer was told an integration "should be ready next quarter", the onboarding team needs to know before the customer asks about it.

A cold handoff is an email: "Meet Sam, who will be looking after your onboarding." A warm handoff is a meeting where the customer, the rep and the onboarding lead talk together.

In the warm handoff, the rep summarizes the goal and the plan out loud, in front of the customer, and asks them to correct anything that is wrong. This does three things. It proves to the customer that what they told sales was heard. It gives the onboarding lead the context directly, with the customer there to fill in gaps. And it surfaces any mismatch between what the customer expects and what the team can deliver while it is still easy to fix.

A simple agenda for a 30-minute handoff call:

• Five minutes: introductions and why the onboarding lead is the right person for this customer.
• Ten minutes: the rep summarizes the goal, the constraints and the first milestone, on a shared screen, and the customer corrects it.
• Ten minutes: the onboarding lead walks through the first 30 days and agrees dates for the first steps.
• Five minutes: questions, and confirmation of who the customer should contact for what.

Ideally, introduce the onboarding lead before the contract is signed. Buyers who are nervous about whether the rollout will work often find it reassuring to meet the person who will lead it. It is one practical way of taking risk off the table, as described in losing deals to no decision.

The handoff can only pass on promises that were made. If those promises were too optimistic, onboarding inherits a problem it cannot solve.

Matthew Dixon and Ted McKenna make this point in their work on customer indecision. On their JOLT Effect site, they warn that promising an optimistic time to value based on a best-case implementation increases indecision rather than reducing it. It is better to describe the common obstacles to full value and show a clear plan for getting past each one. That advice helps close the deal, and it also gives the customer accurate expectations for onboarding.

A few rules that help:

• Base timelines on what similar customers actually achieved, not on the fastest case.
• Say plainly what the customer will need to do: the people, time and decisions required from their side.
• Put important promises in writing, and share them with the onboarding team before the customer signs.
• If you are not sure whether something is possible, say so and find out, rather than saying yes to close the deal.

This is where the first law in Customer Success matters most. Selling to a customer whose goal your product cannot reach, or who cannot get there in the way they need, produces a contract that is likely to end in churn. Sometimes the right thing to do is not to sign.

New customers are most enthusiastic, and most nervous, in the first weeks. The goal of onboarding should be to reach one result the customer can see as quickly as possible, rather than to configure everything.

Choose that first milestone during the sale, write it into the handoff and make sure everyone knows it. For the help-desk example, it might be: "By the end of week two, the team handles all incoming email in the new tool, and the director receives the first weekly report."

Then work backwards to the minimum setup required. Everything else can come later, once the customer has seen the product work for them.

Many onboarding calls follow the same pattern: the onboarding lead shares their screen and demonstrates the setup, and the customer tries to repeat it later on their own. That later attempt is where people get stuck, often on something small, such as a setting that looks different in their account or a permission they do not have.

It usually works better the other way round. Ask the customer to share their screen and do the setup themselves, while you guide them. You see exactly what they see, you catch problems as they happen, and the customer learns by doing. The same approach works for the first week check-in: "Can you show me how you handled this morning's emails?"

Make sharing easy for the customer, especially for people who are not technical. Help99, which we make, is one way to do it: the customer enters a six-digit code in their browser, agrees to share, and chooses the tab or screen they want to show, with nothing to install. It is guidance only: you see what they share and talk them through it, but you cannot click or type on their computer. Any tool that lets the customer show their own screen with little effort will serve the same purpose.

The customer chose to buy partly because they trusted the rep. If the rep disappears the moment the contract is signed, that trust has to be rebuilt from scratch, and the customer may feel that the relationship was only about the sale.

Staying involved does not mean running onboarding. It means a few small, visible actions:

• Joining the handoff call and the call where the first milestone is reached.
• Sending a short note in week two asking how things are going, and passing anything important to the onboarding lead.
• Being available if a promise made during the sale is questioned.
• Celebrating the first result with the champion, who may need it to justify the purchase internally.

These take an hour or two per customer. They also make the customer far more likely to act as a reference later, which will help you win the next deal.

• The customer repeats their story. The onboarding lead did not get, or did not read, the handoff notes. Fix it by making the handoff document a required step before the deal is marked as closed, and by holding the warm handoff call.
• A promise surprises the onboarding team. Something said in the sale was never written down. Fix it by asking reps to list every commitment, including informal ones, and by having onboarding review larger deals before signature.
• The wrong people are involved. The onboarding plan is built with the champion, but the day-to-day users or IT were never consulted. Fix it by including the people map in the handoff and inviting the right people to the kickoff.
• Onboarding tries to do everything at once. Without a clear first milestone, the team configures every feature, and weeks pass before the customer sees any value. Fix it by agreeing the first milestone during the sale.
• The champion leaves. The one person who drove the purchase changes jobs, and nobody else knows why it was bought. Fix it by building relationships with several people during the sale and recording the goal in a way the whole customer team can see.

The handoff should not only go one way. Onboarding teams learn things that would help sales: which promises cause problems, which customers succeed fastest and which warning signs during the sale predict trouble later.

Set up a short monthly review where onboarding shares two or three examples with sales. Which customers struggled, and what could the sales process have done differently? Which customers succeeded quickly, and what did they have in common? Over time, this feedback improves who you sell to, what you promise and how you describe the product.

Customer success, as Mehta, Steinman and Murphy describe it, is not a department that starts working after the sale. It starts with the first conversation. For the earlier stages of that conversation, see SPIN discovery and selling to a buying committee.