The problem
The handoff from AE to CSM is the single most-broken seam in B2B SaaS. Here's the typical flow:
1. AE closes the deal. 2. CRM stage flips to "Closed-Won." 3. CSM gets pinged via Slack: "new account assigned." 4. CSM opens Salesforce, sees three lines of notes: "Closed via competitor displacement. Champion: Maria. Implementation: Q2." 5. CSM joins kickoff call. Asks the customer to "share what you're looking to achieve" — which the customer already explained 4 times during the sales cycle. 6. Trust erodes. Implementation drags. Renewal six months later is suddenly at risk.
The cost: in our experience, ~25% of churn in year one traces back to bad AE→CS handoff. The customer felt like they re-bought after they bought.
The fix: a structured AE→CS handoff doc, auto-generated
This is a structured doc, not freeform notes. AI generates it from real artifacts. CSM reads it before the kickoff call.
Required sections
#### 1. The deal-shape one-pager
- Champion (with title, role in org, why they bought)
- Decision committee (and where each landed: ally, neutral, blocker)
- Pain points that drove the deal (quoted from Gong calls + emails)
- Use cases promised in the sale (specific, not "improve productivity")
- Workarounds in place today (what they were doing instead)
#### 2. The "what AE sold but knew was a stretch" section
This is the trust-breaker section. Every AE in a competitive deal made a promise they can't perfectly back. CSM needs to know what those are.
Examples: - "Our integration with Snowflake handles 5M rows/day" — true, but at p99 latency that may not meet their SLA. - "You'll be live in 4 weeks" — possible, but only with their data engineer dedicated, which AE wasn't sure they have.
#### 3. The political map
- Who in the buying org is privately enthusiastic
- Who voted yes reluctantly
- Who's on a competing vendor for an adjacent function
#### 4. First 30/60/90 milestones promised
What AE said the customer would see when. CSM owns delivery against these.
#### 5. Implementation risks
Anything from technical reviews, security questions, change-management worries that came up in sales.
The AI workflow
Run this Claude skill on every Closed-Won event in Salesforce:
name: ae-to-cs-handoff
trigger: Opportunity stage = Closed Won
Inputs: - All Gong call transcripts for the opportunity (typically 4-8 calls) - Email threads - Slack channels (deal room if you have it) - Salesforce notes + custom fields - Any deal review docs
The Claude prompt extracts each section above from the transcripts. Critically: for the "what AE sold but knew was a stretch" section, the model is instructed to look for hedge words AE used ("should be fine," "I'll need to confirm," "let me get back to you on that") and flag those as risk areas.
Output: a Notion page or Salesforce doc, posted in the deal Slack channel 24 hours after Closed-Won. CSM reads before kickoff.
Pitfalls
- **AE feels surveilled**: the "what AE knew was a stretch" section can read as gotcha. Frame it as "context the CSM needs to deliver" not "where the AE oversold."
- **CSM doesn't read it**: include the 5 sections as required talking points in the kickoff agenda. CSM has to reference them.
- **Customer notices repetition still**: in kickoff, CSM should explicitly say "I've reviewed everything you discussed with [AE name]. Confirming the use cases were X, Y, Z. Today let's start where you left off." — this signals continuity.
Tools that wire it
- **Gong or Chorus**: source of truth for what was said in calls
- **Salesforce or HubSpot**: deal artifacts
- **Anthropic Claude (long-context model)**: handles 6+ hours of call transcripts in one window
- **Vitally or Catalyst**: where the handoff doc lives for ongoing reference
- **Slack**: notification + discussion thread
The metric
Track CSM kickoff call NPS at 7 days post-kickoff (customer-facing micro-survey). The handoff lift typically shows in 2-3 weeks. We've seen +18 NPS at companies that ran this play well.
Why this matters
NRR > 110% companies all share one trait: their CS team feels like an extension of the customer's team, not a new vendor relationship. The handoff doc is what creates that continuity. AI just makes it scalable.