The problem
The SDR books the meeting. The AE walks in cold. Whatever the SDR knew — pain mentioned in email exchange 4, the buyer's offhand "we tried X last year and it failed", the fact that the prospect's CTO posted about migration plans on LinkedIn — none of it makes it to the AE.
In the average B2B sale, an AE's first discovery call wastes 8-12 minutes re-asking what the SDR already knew. Worse, the buyer feels it: "didn't I already tell your team this?"
This isn't a process problem. Your CRM has a "notes" field. SDRs use it 30% of the time and the notes read like Marvel film synopsis: "Met at SaaStr. Interested in product. Budget Q1." Useless.
The fix: an AI brief generator at SDR handoff
Build a Claude Code skill (or Zapier flow if you can't ship code) that runs on every meeting-booked event:
Inputs - All email threads from the prospect (last 90 days) - LinkedIn activity from the buyer + 2 colleagues in the buyer center (Apollo + Cognism pull) - Any inbound form fills, demo requests, content downloads - Past Gong calls if your team has prior history with this account
Output: a 1-page AE brief in Slack
The brief has 5 sections:
1. Why now (3 lines) Why is this account in market this quarter? Look for: layoffs, exec hires, funding events, public migration commentary, competitor renewal cycle.
2. Buyer center (2-4 names) Decision maker, champion, blocker, technical reviewer. With one-sentence sketches of each.
3. Pain mentioned (3-5 bullets) Direct quotes from email/form/call. Source-linked.
4. Objections likely to surface Based on competitor mentioned, budget signals, internal vendor sprawl complaints.
5. Tone advice Personal preferences gleaned from LinkedIn — does this buyer respond to data-heavy decks or story-led narratives?
The exact Claude Code skill
name: ae-brief
description: Generate a 1-page AE discovery brief from SDR notes + email threads
trigger: Meeting booked event in Salesforce → Zapier webhook → Claude Code skill
System prompt:
You are a B2B sales prep specialist. Given the artifacts (emails, LinkedIn activity, form submissions, prior Gong call transcripts), generate a 1-page AE brief with these exact sections: Why now, Buyer center, Pain mentioned (with quotes + source), Objections likely, Tone advice.Constraints: - Every "pain mentioned" must cite a specific email/call with timestamp. - Buyer center max 4 names; if you have less data, say "unclear" — don't fabricate. - "Why now" must be evidence-backed; if you can't find a trigger, write "No clear trigger — treat as cold." - Keep it under 350 words. AE has 60 seconds. ```
What changes when this lands
In our experience: AE first-call open rate (prospect engages > 3 substantive turns) jumps from ~55% to 75-80%. Cycle time on opportunities created from booked meetings drops ~12% because the AE's discovery questions get past surface in turn 1.
Pitfalls
- **Hallucinated pain points**: never let the AI invent a quote. Force source links. If you don't have a quote, write "unclear."
- **Brief becomes a wall of text**: cap at 350 words. Force it.
- **AE doesn't actually read it**: post in Slack 30 minutes before the call. Pin it. If AE leadership tracks first-call quality, this lifts adoption fast.
- **Privacy**: anything you pull from email/Gong is internal data. Don't ship to public endpoints; use Anthropic API direct, not the chat product, for compliance.
The tools that wire this together
- **Apollo or Cognism**: enrich the buyer center with LinkedIn + role data
- **Salesforce or HubSpot**: source of meeting-booked event + activity history
- **Gong or Chorus**: prior call transcripts if account has history
- **Anthropic Claude API**: the actual brief-generator
- **Slack**: where AE consumes the brief
Why this is a handoff article, not a tool review
We can compare Apollo vs Outreach all day. The thing that actually moves deals is the seam between roles. Most teams have great point tools and a black hole at the handoff. AI fills the hole.