Two meetings, not one: fixing the sales-to-CS handoff

A customer does not care about your org chart. They do not know or need to know who owns what internally, but they notice immediately when they are asked the same question twice, or handed to a stranger with no explanation of who that person is or why they are suddenly in the room.

That was the starting point for Session 3: Mastering the Sales-to-CS Baton Pass, where the panel went past the general idea of a handoff zone and got specific about what belongs inside it, who should be in the room, and how the whole thing has to change shape as a company grows.

The conversation kept circling back to one theme: skipping conversations to save time usually costs more time later, in the form of confused customers, repeated questions, and information that lives in one person's head instead of anywhere the team can reach.

What should the first handoff actually look like?

Alison Bukowski argued that most organisations try to be efficient by skipping the internal conversation before a handoff and leaving notes instead. Her view: there should be two meetings, not one.

1. 1
   Internal handoff meeting

   Sales shares deal context and color commentary with the post-sales team before anyone talks to the customer.
2. 2
   External handoff meeting

   Sales stays in the room while the customer meets post-sales, so the transfer feels warm rather than abandoned.

Erin Felton added a detail that is easy to miss: in that external meeting, the customer needs to know exactly who is in the room and why. Not a string of names and titles, but a clear answer to the question every customer is silently asking, which is what this person will actually do for them. The panel agreed that customer success should be the main point of contact after the sale, with other teams supporting from around that relationship rather than each introducing themselves separately.

Why does asking customers to repeat themselves cause churn?

Angela Sutton brought research into the discussion showing that asking customers to repeat information is a top driver of churn during onboarding, alongside slow onboarding and poor communication. The panel's shared read was that sales usually asks the right questions to close a deal, but not the questions post-sales teams will need weeks later.

The panel was clear that this isn't a documentation problem to solve with more paperwork. It is a design problem: sales and post-sales need to agree in advance on what each side needs to know, rather than sales guessing at what customer success will care about later.

What belongs in a system, and what needs a person?

Erin Felton and Anderson Campbell independently landed on the same distinction. Structured, stable facts, the kind of thing that will still be true in six months, belong in an automated system. Anything involving judgement, nuance, or a relationship needs a human conversation.

Kristine Kukich pointed out that none of this works without decent underlying data, and noted that the push toward AI has at least forced many organisations to finally deal with data hygiene they had been avoiding. Jamie McDermott raised the idea of a dedicated information and context manager sitting between teams. The panel liked the concept but was skeptical it would survive contact with an org chart, since a role like that tends to get pulled into whichever department it technically reports into.

How does the handoff change as a company scales?

The panel agreed the handoff is not the same problem at every size, it just looks similar from a distance.

At a small startup, the risk is silence. One person often carries context that would sit across four departments in a larger company, and if that person is unavailable, the knowledge simply is not written down anywhere. Kristine Kukich and Anderson Campbell suggested a simple test here: could someone else pick up this account tomorrow, using only what is written down.

In the mid-market, the failure mode shifts to disconnected silos. Teams exist and have their own processes, but the bridges between them have not been built yet. At the enterprise level, the problem flips again: information does get captured, but it piles up in systems nobody actually reads. The panel described this as process outrunning the purpose it was built to serve, where steps get skipped for convenience because there are simply too many of them relative to the size of the team running them.

What stayed consistent across all three sizes, in the panel's view, was discipline. The mechanism for handling a handoff will look different at five people versus five hundred, but the underlying rigor, actually agreeing on what moves, when, and to whom, has to exist at every stage or the handoff breaks regardless of company size.

One exercise worth trying on its own: map out what currently depends on one person's memory, and write it down somewhere the rest of the team can reach.

Frequently asked questions

Why does the panel recommend two handoff meetings instead of one?

An internal meeting lets sales pass on context and color commentary that would otherwise be lost in notes. An external meeting, with sales still present, lets the customer meet post-sales without feeling like they have been quietly transferred to a stranger.

What is the biggest driver of churn during onboarding, according to the panel?

Angela Sutton cited research showing that asking customers to repeat information they have already given is a top driver of onboarding churn, alongside slow onboarding and poor communication.

Does the sales-to-CS handoff process look the same at every company size?

No. The panel described silence and single points of knowledge as the main risk for small startups, disconnected silos as the mid-market failure point, and process outrunning its purpose as the enterprise-level problem.