How do you structure SDR-to-AE handoff to prevent dropped leads?

Direct Answer

Structure SDR-to-AE handoff as a three-touch checkpoint: a written qualification gate against shared MEDDPICC criteria, a live warm-transfer or three-way intro call with both reps on the line, and a 48-hour AE ownership lock with the CRM stage flipped at the moment of handoff. Without all three touches the lead disappears into the seam between roles, not into the funnel — and the seam is where most "we have a top-of-funnel problem" diagnoses are actually hiding.

The fix is operational, not motivational: written criteria, system-enforced fields, comp that pays SDRs on AE-accepted leads, and a weekly review built around three numbers. Inside two weeks the dashboard tells you whether the process is real or theatrical.

Operator Playbook

SDR-to-AE handoff is the highest-friction moment in early-stage sales. Leads don't fall through gaps — they fall through *handoff misalignment*. Here is how operator communities like Pavilion and Bridge Group structure the moment of transfer:

The Three-Touch Checkpoint

1. Qualification Gate (~2 min)

• SDR qualifies against shared, written criteria: budget confirmed, authority identified, timeline stated
• The Bridge Group SDR Metrics Report has tracked SDR conversion and ramp benchmarks for over a decade — its public summaries cluster median SDR-to-AE conversion in the mid-30s percent when criteria are written, with team-level dispersion widening sharply when criteria are improvised per rep
• Flag the lead record with partial states ("budget pending verbal," "authority TBD") so the AE knows what is *not* yet confirmed — see /knowledge/q117 on MEDDPICC scoring rigor and /knowledge/q08 on early-stage qualification artifacts

1. Warm Transfer or Intro Call (required, not encouraged)

• SDR + AE on the same call with the prospect — live three-way, or sequential when timezones won't cooperate
• AE captures prospect tone, objection language, and stated next action — not just qualification fields
• This drops the *context gap* that forces AEs to restart discovery, the single largest driver of stalled first meetings per coverage on SaaStr and operator threads in Pavilion
• Pair this with /knowledge/q188 on discovery-call structure so the AE is not re-asking the same questions the SDR already worked through

1. 48-Hour Ownership Lock

• AE owns the next touchpoint within 48 hours — no "passing it back" to the SDR for follow-up
• CRM status moves to "AE Owned" at the handoff moment; SDR focus shifts to net-new pipeline
• The InsideSales / XANT lead-response research, summarized in the Harvard Business Review write-up "The Short Life of Online Sales Leads", reports the odds of qualifying a lead at roughly 60x higher when first contact is inside the first hour vs. day two, and the odds of *contacting* a lead at roughly 100x higher inside the first five minutes vs. thirty minutes — ownership clarity is the only way to honor that window at scale

Three Root Causes of Dropped Leads

Metrics Dashboard

If you only track three numbers around handoff, track these:

• % of handoff calls with both reps logged on the call record — target >= 80%
• % of accepted leads contacted by AE within 48 hours — target >= 90%
• AE acceptance rate of SDR-qualified leads — target >= 70% (below that, the qualification gate is decorative)

Fold these into the weekly RevOps review alongside the pipeline-decay query in /knowledge/q260 and the SDR-comp clawback discussion in /knowledge/q221.

Comp Design That Reinforces the Process

Process fails when comp pulls in the opposite direction. The cleanest split:

• SDR variable pays on AE-accepted leads (not raw meetings booked) with a 7-day clawback on AE-disqualified leads — this is the Pavilion and SaaStr consensus position for series-A through series-C teams
• AE variable carries a small kicker tied to 48-hour first-touch attainment so the SLA is in their compensation, not just their playbook
• Sales-manager variable carries a kicker tied to handoff-call attendance so the AE's calendar is enforced top-down, not by RevOps email

See /knowledge/q221 for the SDR-comp clawback mechanic in detail and /knowledge/q83 on AE quota construction.

30-60-90 Rollout

• Week 1 (Days 1-5): write the three qualification criteria; build CRM validation rules (required handoff fields, "AE Owned" stage, two-attendee call record) using the Salesforce validation-rules docs or the HubSpot required-property docs; SDR + AE warm-transfer training; shadow first three live handoffs
• Day 30: dashboard live; first weekly RevOps review held; comp-plan amendment drafted; first round of CRM violations coached not punished
• Day 60: comp-plan amendment in effect for SDRs (AE-accepted basis with 7-day clawback); AE 48-hour kicker live; manager scorecard updated to include handoff-call attendance
• Day 90: stop coaching, start enforcing — repeated violations roll into PIP territory; routing rules audited for handoff-impact; first quarterly review compares pre- and post-rollout dashboard numbers

See /knowledge/q42 for founder-led variants and /knowledge/q199 for PLG-motion variants.

When This Does Not Apply

The three-touch checkpoint assumes a model where SDRs and AEs are split. It does not apply cleanly to:

• Founder-led sales before the first AE is hired — at that stage the founder is the SDR *and* the AE; the gate becomes a self-discipline question, not a handoff design
• Pure PLG (product-led-growth) motions where the "lead" is a product-qualified user and the AE is responding to in-app signal, not an SDR transfer — different playbook entirely
• High-velocity SMB with monthly contract values under roughly $500 ACV, where a live warm-transfer is uneconomical and an asynchronous notes-only handoff is correct

Bear Case: Six Ways This Fails

1. Warm transfer becomes a calendar fiction. AEs accept the handoff invite but don't actually attend the live call. The SDR ends up doing a solo "intro" and forwarding notes. *Lagging signal*: % of handoff calls with two reps logged drops below 70%. *Leading signal*: AE handoff-invite decline rate above 15%. Fix: hold AEs to handoff attendance the way you hold them to forecast-call attendance, and put attendance into the AE's quarterly scorecard.
2. 48-hour SLA is honored on paper, ignored in practice. AE logs a templated email "touch" within 48 hours, then goes silent for two weeks. *Lagging signal*: time-to-second-meeting flat after rollout. *Leading signal*: % of "first touches" that are one-line templates rising above 30%. Fix: measure *meaningful* touches (call attempted, reply received, meeting booked) and exclude one-line templated emails from the SLA counter.
3. Qualification criteria are written but not enforced. SDRs flag everything as "qualified" because their comp depends on volume. *Lagging signal*: SDR-to-AE acceptance rate above 90% combined with SAL-to-SQL conversion below 30%. *Leading signal*: AE-disqualification reasons clustering on "never had budget" or "wrong title." Fix: comp the SDR on AE-accepted leads with a 7-day clawback.
4. Handoff process exists, CRM does not enforce it. Reps free-text around the rules. *Lagging signal*: % of handoffs that pass a CRM validation rule below 60%. *Leading signal*: rising count of opportunities created without an associated handoff call record. Fix: convert the playbook into validation rules and required fields so the system blocks the bad path.
5. The dashboard exists, but no one runs the weekly review. *Lagging signal*: % change in handoff-call attendance flat for two consecutive months. *Leading signal*: dashboard load count flat or declining week-over-week. Fix: put the dashboard on the weekly sales-leadership agenda; assign a single owner to walk through misses.
6. Territory or routing rules silently break the handoff. Routing logic re-assigns the lead after the warm transfer, breaking ownership and resetting the 48-hour clock. *Lagging signal*: leads with multiple AE owners in a single week, longer time-to-second-meeting on re-routed leads. *Leading signal*: routing-rule changes shipped without a handoff-impact review. Fix: route once at handoff and freeze ownership for at least the first 30 days unless reassignment is explicitly logged with a reason code.

Disconfirming Evidence

This framework is wrong if any of the following is consistently true: (a) AE acceptance rate is already above 80% with no enforced criteria, suggesting natural alignment is doing the work; (b) the dropped-lead audit shows the failures concentrated *after* the second AE meeting, not at handoff — in which case the bottleneck is discovery or pricing, not handoff; (c) the team is so small (two reps, one AE) that the formal three-touch ceremony costs more time than it saves.

If any of those hold, simplify before you scale.

Sequence

Verified Sources

• Bridge Group SDR Metrics Report — multi-year SDR conversion benchmarks; mid-30s percent median SDR-to-AE conversion when criteria are written
• Harvard Business Review — "The Short Life of Online Sales Leads" — InsideSales / XANT lead-response data; 60x qualification odds within hour one, 100x contact odds within five minutes
• Salesforce — Validation Rules — system-enforced required-field mechanic
• HubSpot — Property Validation Rules — equivalent mechanic for HubSpot CRM
• Pavilion — operator community for sales/RevOps comp and handoff design
• SaaStr — coverage of context-gap and discovery-restart failure modes
• Challenger — "question handoff vs. answer handoff" framing
• Sandler — handoff as "introducing your problem-solver"
• Force Management — buying-stage taxonomy alignment

How to Know It Is Working

Inside 30 days you should see two pre/post deltas: AE acceptance rate holding above 70% while SDR meeting volume stays roughly flat (the gate is filtering, not just suppressing volume), and time-to-second-meeting dropping noticeably for handoffs that have a logged warm-transfer call relative to those that don't.

If you do not see those two effects within a month, the dashboard is theatre and you should revisit the comp design and CRM enforcement before adding more process.

Notes

• Challenger: coach SDRs to end discovery calls with a *question handoff*, not an answer handoff — the AE discovers alongside the prospect, not from a transcript
• Sandler: frame the handoff as "introducing your problem-solver," not "passing you off"
• Force Management: sync buying stage language between SDR and AE so both use the same stage taxonomy
• Bridge Group: reps who log a "lead context confidence" score on handoff reduce re-discovery time in the next AE call
• See also /knowledge/q156 on SLA enforcement, /knowledge/q260 on pipeline-decay reports, and /knowledge/q42 on founder-led sales handoffs

TAGS: sdrtoadhandoff,leaddrop,handoffgap,crmhygiene,pipelinemanagement,discoveryprocess,revopsmetrics,teamalignment