The deal closes on the last day of the quarter. The rep rings the bell, posts in Slack, and moves on to the next one. Two weeks later the customer’s onboarding kickoff opens with your CSM asking what problem they bought the product to solve, who their main contact is and when they need to be live. The customer answered all three questions in the sales process. Twice.
That kickoff costs you more than an awkward hour. It tells a new customer that the company they signed with doesn’t talk to itself.
Most sales to customer success handoff checklists list fifteen or twenty things to capture. Reps rarely fill in twenty fields at close won, so most of them end up empty. The handoff that works is short, enforced by the CRM, and checked against what happens to the customer afterward.
What should a sales to customer success handoff include?
A sales to customer success handoff should include five fields, required before a deal can move to closed won: why the customer bought, what success looks like and by when, the people involved and their roles, anything promised outside the contract, and the risks the rep sees. Everything else can live in notes, where it doesn’t slow the close down.
- Why they bought. The business problem in one or two sentences, in the customer’s words. This is the field your CSM reads before the first call, and the one that decides whether onboarding aims at the right outcome.
- What success looks like and by when. The result the buyer expects and the date they expect it. If the customer said they need reporting live before their board meeting in March, that date belongs in a field, not in the rep’s head.
- The people. The economic buyer, the day-to-day contact and anyone who pushed back during the deal. Associate each one to the deal as a contact with a role, so the CSM knows who signed and who has to be won over.
- What was promised. Any commitment outside the standard contract: a custom integration, a discount tied to a timeline, a feature the rep said is coming. Unwritten promises are often where early churn starts.
- Risks. Anything the rep is worried about. A champion who might leave, a competitor still in the building, a budget that was hard to get. This one is uncomfortable to write, which is why it has to be required.
Contract value, term and start date matter too, but those usually already live on the deal. The five above are the ones that never make it out of the sales conversation unless something forces them to.
Why only five handoff fields?
Because the goal is a handoff that happens on every deal, not a perfect one that happens on a third of them. Each required field is a small tax on the rep at the moment they are least patient. Five fields take a few minutes. Twenty fields get filled with “see notes” or a single period, and then the data is worse than having nothing, because it looks complete.
Pick the fields your CSM would ask about on the kickoff call. If a field doesn’t change what CS does in the first thirty days, leave it out.
How do you require handoff fields before closed won in HubSpot?
In HubSpot, set the five handoff properties as required on the closed won stage of your deal pipeline. A rep then cannot mark the deal won until every field is filled in. Pair that with good field types, labels written as questions, and the same fields shown earlier in the deal as optional, so reps capture answers while the conversation is fresh.
A few details make this hold up:
- Use the right field types. Dropdowns or dates where you can, short text where you must. “Success date” should be a date property, so you can report on it.
- Write the field labels as questions. “Why did they buy, in their words?” gets better answers than “Business pain.”
- Collect them before the last week. Add the same properties to an earlier stage as optional, so reps fill them in during the deal instead of rebuilding them from memory at signature.
In Salesforce, a validation rule on the closed won stage does the same job, and the opportunity path can show the five fields as key fields so reps see them at every step.
What should happen automatically at closed won?
Once the handoff fields are in, a closed won workflow should do the rest without anyone remembering to. It can assign the CSM, create the onboarding record with the five fields copied across, notify the CSM with a link to the deal, and create a task for a short internal handoff call between the rep and the CSM before the customer kickoff.
That internal call is the piece teams often skip, and in my experience the one CSMs value most. Fifteen minutes where the rep tells the story behind the fields. The fields make sure the information exists. The call makes sure it lands.
How do you know if the handoff is working?
Check it against your own customers once a quarter. Pull every account that churned or downgraded in its first year alongside the ones that renewed, and look at the handoff fields on each original deal. The question is whether weak or empty handoffs line up with the accounts you lost.
You don’t need a data team for this. A list of twenty accounts and an hour with your head of CS is enough to see whether incomplete handoffs line up with the accounts you lost. If they do, the five fields become the cheapest retention project you will run this year. If they don’t, you have ruled out one cause and can look elsewhere.
Where should you start?
Start with your CSMs. Ask them what they had to re-ask customers on the last five kickoff calls, and write down every answer. That list is your set of required fields, already in priority order, and it comes from the people who feel the handoff gap every week. Build those fields into the closed won stage first, then add the automation.
If you want an outside read on how your CRM carries information from sales to post-sale today, take our free CRM diagnostic. For keeping required fields from turning into clutter, read about CRM field bloat.
The customer only tells you why they bought once. Make sure the CRM is listening when they do.