Sit in on your next kickoff call and count one thing.
Count how many times the customer explains something they already explained to your AE. Their team structure. Why they are doing this now. The system they need it to talk to. The deadline they are working towards.
Each repetition takes maybe ninety seconds, so the whole thing costs you six or seven minutes of a sixty-minute call.
Six minutes you can afford. What the customer concludes while it happens, you cannot: these people do not talk to each other.
Your AE spent three months convincing them you understand their business. A team they have never met now has to prove it again from scratch, while asking for admin credentials and a security review.
A longer handoff form will not fix this.
Why handoffs fail, and it isn’t laziness
Almost every company has a handoff process, most of them have a template, and the template gets filled in. The onboarding team still starts without the context.
Three structural reasons, none of which a longer form fixes:
The AE is measured on the next quarter, not this customer’s week six. That is the comp plan working exactly as designed. The moment a deal closes, the AE’s attention moves to the next one, which is the right call for them. Any handoff process that relies on an AE volunteering effort after close is fighting the comp plan and will lose.
The valuable context is exactly the context that is awkward to write down. “Their VP of Ops did not want to switch and only stopped objecting when the CFO overruled him” is the single most useful sentence in the whole deal. Nobody types it into a CRM field. It feels like gossip, it might be wrong, and it will sit in a system the customer’s own champion could one day be shown.
Whoever asks the questions decides what gets said. When the AE decides what matters, they pass on what is easy to summarise. When the onboarding owner asks the questions, they ask about what will hurt them in week four. Same two people, same fifteen minutes, completely different information.
All three are about who does the work and when. The form is the least important part of a handoff, which is why rewriting it never helps for long.
What belongs in a handoff note (the nine fields)
Everything in the contract is already available to the onboarding team, so none of it belongs here. A handoff note that restates the order form has told the onboarding team nothing.
These nine only exist in the AE’s head.
| # | Field | What a good answer looks like | Where it usually gets lost |
|---|---|---|---|
| 1 | The value milestone, in the customer’s words | ”Our support team stops answering the same setup question forty times a week” | Replaced by the product outcome: “rolled out to the CS team” |
| 2 | The trigger event | ”Their previous tool was sunset in June and they have to be off it by October” | Never asked, because the deal closed and the reason stopped mattering |
| 3 | Promises made beyond the contract | ”We said the Salesforce sync would ‘probably be straightforward‘“ | The AE genuinely forgets. It was one sentence on call three |
| 4 | The named risk | ”They have failed a rollout like this before and the sponsor took the blame” | Feels negative to record on a won deal |
| 5 | The customer’s internal deadline | ”The board update is on 14 October and they want a number in it” | It is not a contractual date, so no field holds it |
| 6 | Stakeholder map, politics included | ”Champion is the Ops lead. The VP was overruled and is not on board” | Written as titles instead of positions |
| 7 | The alternative they nearly bought | ”It was down to us and Rocketlane; they picked us on the customer-facing side” | Considered irrelevant once the deal is won |
| 8 | Technical constraints already surfaced | ”Data has to stay in the EU. Their IT lead confirmed SSO is required at go-live” | Mentioned in a call, never routed to anyone technical |
| 9 | What the buyer explicitly did not want | ”They said no to a phased rollout. One cutover or nothing” | Nobody records a no |
Field 9 is the one almost no handoff template has. It stops your onboarding team from walking into kickoff and proposing the exact approach the customer already rejected in the sales cycle. When that happens the customer does not think “the plan is wrong.” They think “I already answered this.”
Field 7 earns its place for a different reason. The alternative they nearly bought tells you what the customer will compare you to for the next twelve months. If they nearly picked a professional-services platform and chose you for the customer-facing experience instead, a clumsy first two weeks reads as evidence they chose wrong.
Field 4 is the one your AEs will push back on, so set the standard out loud: a handoff note with no risk in it is not finished. Every deal has one. If the AE cannot name it, that is itself the finding, and it means nobody asked the buyer a hard question all cycle.
How to run the handoff meeting in 20 minutes
Nine fields is a short document. It is still a document, and documents get read by whoever is already motivated.
So attach it to a meeting.
Who: the AE, the onboarding owner, and the solutions engineer if one was involved. Three people, no managers. Managers turn a working conversation into a status report.
When: at verbal commit, before signature. This saves the most calendar time of any change here, and it saves it inside your own building. By verbal commit the deal is decided and the AE still has the account fully loaded. You can schedule the kickoff, request access, and start the security review before the subscription clock starts. Teams that wait for the signed PDF routinely lose one to two weeks to their own sequencing, then describe it as the customer being slow.
Length: twenty minutes. Hard stop. A handoff meeting that runs an hour is a meeting where somebody is reading the contract aloud.
Who asks the questions: the onboarding owner. The AE does not present the account, they get interviewed about it. Nine fields, one question each, plus whatever follows.
The last question, always: “What would make this customer unhappy in month two?”
It beats “what are the risks” because it forces a specific scenario instead of a category. You will get answers like “they think the migration includes their historical data and I am not certain it does.” That sentence is worth more than the rest of the meeting.
Write the answers straight into the plan as you go. The output of a handoff meeting should be a draft onboarding plan with dates in it, not a note that someone will later turn into a plan. If you are still designing the underlying process, our guide to building a customer onboarding process covers what that plan should contain and how to work backwards from the value milestone.
Four things the AE almost never passes on
Even with the meeting, some things reliably get left behind.
The informal commitment. Every deal contains at least one. “We can definitely do that.” “That should be no problem.” “Yes, we support that.” The buyer heard a promise. Your CRM recorded a closed-won. Nine weeks later the customer says “you told us this would work with our SSO provider” and they are right, someone did.
Ask the AE as a closed question: did you say anything in this cycle that we now have to make true? Open questions about promises get “no, nothing unusual.” Closed ones get answers.
The buyer’s private timeline. Contracts have start dates. Buyers have board meetings, budget cycles, and a quarterly review where they have to justify this purchase to someone. That date is invisible to you and it shapes how the customer behaves in week seven. Know it, and you can build the plan so something real exists by then. Miss it, and you experience it as unexplained urgency.
The sceptic. Most B2B purchases have someone who did not want it. They are usually not the champion and usually not in your kickoff call. They will be the person who skips training, never migrates their team, and supplies the anecdote that becomes “this never really worked for us” at renewal. You cannot manage a sceptic nobody told you about.
The reason they bought now. Not why they bought, why now. Companies live with a problem for years and then act in a specific month. Whatever made this month different is what will keep the project moving when the customer’s attention gets pulled elsewhere. Lose it and you lose your only source of urgency that does not come from you.
Who should own the handoff?
Give it to the onboarding side.
If the AE owns the handoff, it competes with pipeline, and it produces a form filled in from memory a few days after close. If the onboarding owner owns it, it becomes a set of questions asked by the person who will suffer from a bad answer. The AE still supplies everything. They stop deciding what matters.
Then let the receiving side refuse. An onboarding owner who can say “this handoff is incomplete, I am not scheduling kickoff until I have fields 4 and 6” is a quality gate. An onboarding owner who has to accept whatever arrives is a complaints department.
That sounds confrontational. In practice it takes about three refusals before handoff notes get better, because the AE learns that an incomplete note comes back rather than disappearing.
One more piece: put the AE in the kickoff call. Twelve minutes at the start, then they leave. The customer sees continuity instead of a baton drop, and the AE hears their own promises repeated back with the implementation team in the room. Handoff notes get more honest once AEs know they will be sitting there.
How do you know if your handoff is broken?
Three diagnostics you can run this month. None need a tool.
1. Count the repetitions. Attend your next five kickoff calls. Each time the customer explains something the AE already knew, make a mark. Zero is the target. One or two is normal. Three or more per call and your handoff is a document nobody reads.
2. Measure signature to kickoff. Median calendar days from contract signed to kickoff call held, across your last twenty accounts. Above five business days and the gap is almost never the customer. It is your scheduling, your access requests, and your handoff waiting for someone to have time. Those are the cheapest days you will ever recover, because you control every one of them.
3. Count early re-scopes. How many accounts had their plan materially changed in the first 30 days? An early re-scope is nearly always a handoff failure showing up late. Someone sold something, nobody wrote it down, and the implementation team found out in week two. Track it as a handoff metric rather than an onboarding one. Our guide to onboarding KPIs covers where it sits alongside the metrics that predict retention.
If all three look bad, do not start by rewriting the template. Move the meeting earlier and change who asks the questions. Most teams get most of the improvement from those two changes alone.
What if the customer never sees a handoff at all?
Everything above treats the handoff as a transfer problem. One person knows something, another person needs to know it, and detail goes missing on the way. Every fix so far has been about losing less of it.
Ask yourself what the customer actually experiences at handoff. They have been working with your AE inside some shared surface: a proposal, a mutual action plan, a shared drive, an email thread with eleven attachments. Then the deal closes and they get invited into something entirely new. New link, new login, new structure, and their first task in it is to re-supply information they already gave you.
From their side, it is a restart.
Now picture the version where the space the customer worked in during the sales cycle is the same space onboarding happens in. The mutual action plan gains implementation phases instead of being replaced by a project plan. The stakeholders already have access. The requirements they typed into an intake form during evaluation are still sitting there. The AE does not hand the account over so much as fade out of a room the onboarding owner has now joined.
You still need the internal handoff. Fields 3, 4, 6 and 9 are judgements about people, and no software will carry them for you. But the customer-visible restart disappears, and with it the six minutes of repetition and the impression behind it.
Most sales-and-onboarding workspaces are built around this shape, Valuecase among them: one customer-facing space that starts in the sales cycle and keeps going through go-live.
The trade-off is real, so be precise about it. Tools built for the implementation phase specifically, like Rocketlane and GUIDEcx, give you more depth once the project is underway: resourcing, dependency management, capacity planning across a services team. If your onboarding is a staffed delivery operation with utilisation targets, that depth matters more than continuity and the restart is a cost worth paying. We compared the two shapes in onboarding workspaces vs. project tools. If your onboarding is mostly about getting a customer’s team to do a sequence of things without losing momentum, continuity wins. Our sales-led SaaS stack works through that choice for the motion where this handoff matters most.
Not changing tools this quarter? The twenty-minute meeting still gets you most of the way, and it is free.
A handoff you can run next week
- Nine fields, none of which repeat the contract.
- A 20-minute live meeting at verbal commit, not after signature.
- The onboarding owner asks. The AE answers.
- Last question is always “what would make this customer unhappy in month two?”
- The output is a draft plan with dates, not a note.
- The AE joins the first twelve minutes of kickoff.
- The onboarding owner can refuse an incomplete handoff.
Then run diagnostic one at your next kickoff and count the repetitions. Get to zero and the customer walks into onboarding believing you are one company. Something will still slip in week five, and when it does, their read on it depends almost entirely on whether they already think you have your act together.
Once the handoff is clean, fix what the customer sees in their first week. The handoff feeds straight into the kickoff call, which is where that context becomes a plan the customer owns. Our onboarding checklist lists the 38 items and marks who owns each one, and tracking engagement during onboarding covers the signals that tell you an account is drifting two to three weeks before a date gets missed.