Mastering the Sales-to-CS Baton Pass
Sales to post-sales handoffs and scaling by company size
A PSA panel digs into what belongs in the sales-to-post-sales handoff, what should be automated, and how handoffs change as a company scales.
What the panel said
This session is the third in the Post-Sales Alliance series, hosted by Jamie McDermott alongside Kristine Kukich, with Alison Bukowski, Erin Felton, Anderson Campbell and Angela Sutton on the panel. The group moved past the idea of a general handoff zone and got into what actually sits inside it, who touches it, and how that changes as a company grows from five people to a full enterprise.
Alison Bukowski argued that most organisations try to save time by skipping the internal conversation before a handoff and just leaving notes. She said there should be two meetings: one internal, where sales shares context and color commentary with the post-sales team, and one external, where sales stays in the room during the handoff so the customer feels supported rather than passed along. Erin Felton added that in that external meeting, it has to be obvious to the customer who everyone is and why they are there, not just a string of names and titles.
Angela Sutton brought in research showing that asking customers to repeat themselves is a major driver of churn during onboarding, alongside slow onboarding and poor communication. The panel agreed that sales usually asks the right questions to close a deal, but not the questions post-sales teams need later, and that this gap should be closed through an ongoing loop between sales, CS and onboarding rather than a bigger form.
On systems versus people, Erin Felton and Anderson Campbell both described a similar split: structured, stable facts belong in automated systems, while anything involving judgement, nuance or relationships needs a human. Kristine Kukich pointed out that none of this works without decent data underneath it, and that AI has at least pushed many organisations to finally tackle data hygiene. Jamie McDermott raised the idea of a dedicated information and context manager role sitting between teams, which the panel liked in principle but worried would eventually get absorbed into whichever department it reports into.
On scaling by company size, Kristine Kukich and Anderson Campbell described different failure points: silence and single points of knowledge at the startup stage, disconnected silos in the mid-market, and process outrunning its original purpose at the enterprise level, where information gets captured but no one reads it.
One thing worth trying: map out what silently depends on one person's memory right now, and write it down somewhere the rest of the team can actually reach.
Take it with you
More writing on this
Get the next recap by email