SDR → AE Handoff
Handoff completed in < 24h with brief attached
SDR-to-AE handoff is where deals go to die. SDR does the qualifying work, hands off in Slack: "you got the Acme meeting next Tuesday, good luck." AE opens the CRM 30 minutes before the call, reads a two-line note, and walks in cold. Prospect wastes half the meeting re-answering questions the SDR already asked. Half the handoffs never get a follow-up because the AE didn't know who to email. SDR wonders why their bookings-to-closed-won ratio is 5%.
An hour-by-hour walkthrough.
Step by step.
- 01
Detect the booked meeting + trigger handoff assembly
Meeting booked → 48-hour countdown to full handoff packet. Includes both SDR-to-AE handoffs and inbound-to-AE handoffs.
Chili Piper · Calendly · Google Calendar · CRM - 02
Enrich the account + contact deeply
Company: size, industry, stage, tech stack, competitors. Contact: LinkedIn history, role, likely influence, public content (blog posts, talks, tweets). Fit signals against ICP + similar-customer patterns.
LinkedIn Sales Navigator · Crunchbase · Clearbit · BuiltWith · Twitter - 03
Extract qualification + conversation history
Every email exchange, phone call transcript, LinkedIn message with the prospect. Pain points identified, budget signals, authority mapping, timeline hints. BANT summary + supporting quotes.
Email · Gong · Chorus · Outreach · CRM notes - 04
Draft talking points + similar-deal reference
Suggested talking points from prospect's pain + our messaging. Similar-shape closed deals as reference (industry, size, product mix, decision timeline). Cited so AE can dig deeper.
CRM history · Content library · Case study database - 05
Post-meeting logging + follow-up cadence
AE logs outcome + Rev updates opportunity + drafts recap email + schedules cadence (recap-day-0, security-packet-day-2, deep-dive-day-5, decision-check-day-14).
CRM · Email · Outreach cadence · Follow-up scheduler
What you connect to make this run.
Chili Piper · Calendly · Google Calendar
readMeeting-booked event as the trigger. Meeting metadata (attendees, when, source) drives handoff assembly.
Salesforce · HubSpot · CRM
read+writeFull opportunity + account + contact history. Write handoff packet + AE assignment + follow-up cadence back to the opportunity so pipeline visibility is complete.
LinkedIn · Crunchbase · Clearbit · BuiltWith
readExternal enrichment — company, contact, tech stack, industry. Cached to reduce cost; refreshed weekly for active accounts.
Gong · Chorus · Outreach · Salesloft
readConversation history: emails, calls, cadence responses. Pain points extracted from transcripts. Prior AE + SDR notes attached to the packet.
Before and after, honestly.
Playbooks that pair with this one.
Answers about this playbook.
What if the meeting is short-notice (booked for same-day)?
Rev prioritises short-notice handoffs. Full packet in under 20 minutes; AE gets the essentials even if the enrichment isn't complete. Post-meeting update adds what came late.
How does it handle handoffs from other sources (partner, event, referral)?
Source-aware handoffs. Partner referral includes partner context + past joint deals; event lead includes event conversation notes; referral includes referrer relationship. Same packet skeleton, source-specific enrichment.
Can AEs pull up the packet on-demand (not just pre-scheduled)?
Yes — any deal in the AE's book has an on-demand refresh. Useful for cold-call prep, follow-up crafting, or executive-briefing prep.
How does the SDR see whether their handoff converted?
SDR dashboard shows handoff outcomes: meeting attended, follow-up scheduled, next-stage advancement, ultimate close/lose. Feedback loop on handoff quality; SDR performance measured against final outcomes.
What about handoffs where the SDR should stay involved?
Handoff type configurable per team. Full handoff (SDR done, AE owns), assist handoff (SDR stays as project manager), or team-selling (both AE + SDR on the meeting). Rev routes and notifies per configured type.
See it run on your data.
Free plan, no credit card. Connect the systems this playbook needs and run it against a past event first.