The SDR-to-AE Handoff — 60-Min Training

Why the handoff is the most expensive leak in the funnel

Pipeline rarely dies in the cold call or the close — it dies in the gap between them, and most teams never measure it because they never separate the two drops. Pull last quarter's three numbers: meetings booked by SDRs, meetings actually held, and meetings that became a real, accepted opportunity. The drop from booked to held is your no-show tax; cold-sourced meetings run a 20–30% no-show rate on their own. The drop from held to accepted is your handoff tax, and it commonly runs 30–50%.

The Bridge Group's annual SDR Metrics research puts average SDR-booked-meeting to Sales-Accepted-Opportunity conversion at roughly 38% — meaning a typical team loses about 62% of booked meetings somewhere between booking and acceptance. Those are not deals lost to a competitor. They are deals lost to internal friction, the cheapest competitor in the world and the one an unstandardized handoff feeds directly. A held-but-never-accepted meeting is doubly wasted: an SDR who hit quota on paper, and an AE who burned a discovery slot for nothing.

The economics land hard because reps respond to them. At a fully loaded AE cost of roughly $150–$200 per selling hour, a 45-minute dead discovery call plus ~30 minutes of prep is a $110–$150 write-off per bad handoff. An AE inheriting eight hollow handoffs a month is burning $1,000+ monthly on calls that were never real — and the opportunity cost is worse, because every slot spent on a hollow handoff is a slot not spent on a live one. The handoff is not only a quality problem; it is a capacity problem.

The accepted-opportunity bar: one shared definition of "qualified"

The root cause is that "qualified" is a social agreement, not a fact. Most AEs vet privately, by gut, against a personal and unwritten bar — which means every AE has a *different* bar, the SDR is qualifying against a moving target, and the same lead is "accepted" by one AE and "garbage" to another. The training's core move is to have the whole SDR and AE bench co-write one bar and every AE agree, out loud, to accept any lead that clears it. Consensus, not one manager's opinion, is what moves a habit.

Keep the bar to five or six items the SDR can verify on a live call — a twelve-item bar is one nobody fills. The working set most teams land on:

• A named pain or trigger — a specific problem the buyer named, or a specific event (new hire, tool sunset, missed number, compliance deadline) that explains why they took the meeting.
• Role and authority — the prospect's relationship to a yes: user, influencer, or economic buyer. Not their title; their proximity to the decision.
• A rough timeline — when they'd act if the fit is right. "This quarter," "next budget cycle," even "just exploring." Vague is allowed; absent is not.
• Budget reality — not a confirmed number, a confirmed *awareness* that the solution costs money and the buyer isn't surprised.
• Confirmed attendees — who will actually be on the AE's call, by name, so the AE isn't blindsided by an extra stakeholder or a no-show champion.
• A reason it's happening now — why this meeting, this week: the difference between a real opportunity and a calendar accident.

Anchor the bar on an established frame so it carries credibility and new hires can map it onto something they know. BANT (Budget, Authority, Need, Timeline), which originated at IBM, fits a velocity motion — ACV under ~$10K, cycles under 30 days. MEDDIC (Metrics, Economic buyer, Decision criteria, Decision process, Identify pain, Champion), developed at PTC in the early 1990s, fits enterprise — ACV above ~$50K, cycles 90+ days. The bar is a *subset* of the chosen frame, not the whole thing; an SDR does not run full MEDDIC on a cold call.

Set one hard discipline: verification is capped at about 90 seconds of checklist talk inside the SDR call. Past that, qualification stops feeling like a conversation and starts feeling like an interrogation — and an interrogated prospect books fewer meetings. The bar is a filter the SDR carries, not a survey the SDR administers.

The handoff brief: a short artifact that gets filled

The brief is what physically carries the qualified lead across the gap. Design it as a short, structured note — target 120–200 words, fillable in under 4 minutes — not a paragraph of vibes and not a CRM essay. Both size limits are load-bearing. A brief that creeps past four minutes gets skipped under quota pressure, because the SDR has a meeting quota, not a documentation quota. A brief under ~120 words almost always drops the two most valuable fields and forces the AE to re-discover them live. The format lives in the narrow band where it's fast enough to get filled and rich enough to be worth filling.

Required fields:

• The trigger — the event or named pain that explains why the meeting exists, so the AE opens on the buyer's reason instead of a generic pitch.
• The pain in the buyer's own words — a direct or near-direct quote. This is the field most often dropped and the most expensive to lose, because buyer language is what lets the AE start the call where the SDR left off.
• Confirmed attendees — names and roles of everyone on the AE call, so the AE prepares for the actual room.
• What the SDR promised — the specific thing the SDR said the meeting would cover, so the AE doesn't contradict or under-deliver the setup.
• Any landmine — a competitor already in the deal, a bad past experience, a skeptical stakeholder, a hard constraint. The landmine field exists precisely for the bad news.

Have each AE-SDR pair draft one brief from a real recent lead, not a hypothetical. The pairing is deliberate: the SDR knows the buyer's situation, the AE knows what they wish they'd been told, and drafting together forces the two perspectives to reconcile in the artifact itself. Watch for three predictable failure patterns as pairs work: paraphrase drift (writing "some forecasting challenges" instead of the buyer's actual "our forecast was off 15% and the board noticed"), landmine omission (dropping the known competitor because it feels like bad news), and essay creep (400 words because more feels safer — it isn't, because the next SDR won't replicate it). Optimize the brief for completion rate, not completeness.

The friendly bounce-back: the hardest skill in the handoff

The bounce-back is where the whole gate lives or dies. If a rejected lead feels like a strike against the SDR, SDRs stop booking honest meetings and start padding briefs to clear the bar — and the bar becomes a thing to game rather than a thing to meet. The rule for the room: a bounce comes with exactly one specific reason and a clear path to fix it — never a shrug. "This one isn't ready" teaches the SDR nothing. "This is missing a confirmed economic buyer — can you get a quick call to confirm who signs?" is a bounce that coaches. This is the two-way rejection-with-reason loop from the SiriusDecisions/Forrester Demand Waterfall: a rejected lead returns to the SDR with a stated reason, never vanishing into a CRM status nobody reads.

Attach a hard timing rule: the bounce happens within 24 hours of the brief landing. A recyclable lead has a shelf life. Bounced within a day, it's still warm enough to call back, fix the missing item, and re-book. Left a week, the trigger fades and a quick re-qualification becomes a full re-prospecting cycle. The 24-hour SLA is the difference between a bounce-back loop and a lead graveyard.

Drill it live: at least three rounds per pair, swapping roles each time. One person plays the AE naming exactly one reason and a fix path; the other plays the SDR receiving it as coaching, restating the fix, and committing to a re-qualification step. Running both sides matters — an SDR who has had to *deliver* a bounce qualifies more carefully, and an AE who has had to *receive* one bounces more kindly. Give the listener one job: catch the moment the bounce stops being coaching and becomes a verdict. A line that names the person ("you always send me thin leads") instead of the artifact ("this brief is missing the trigger") is a verdict — flag it and rebuild the line. Critique the artifact, never the person.

The weekly sync and the two-milestone target

Stand up a 25-minute weekly SDR-AE sync — short by design, because a sync that balloons becomes admin overhead the team resents. Book the recurring invite live, in the room; a sync "we'll set up later" never happens. The agenda is fixed and tight: review every handoff from the prior week (mark each accepted or bounced), tally the acceptance rate, cluster the bounces, and inspect the bar itself. Run it as inspection, not lecture — the front-of-funnel twin of a weekly deal-inspection forecast call.

Track one number quarter over quarter, the booked-to-accepted rate, and set it as two distinct milestones so the team knows what good looks like at each stage. The first-quarter target is 65% — a realistic early win for a team that just installed the bar, measured against the ~38% industry baseline; treat it as "the process is working." The mature-state bar is above 80% — where a disciplined team converges once the brief, bounce-back, and sync are all muscle memory. Two checkpoints matter because a single target either demoralizes a new team (80% looks impossible at month one) or lets a mature team coast (65% is too easy at month twelve).

Give the sync one decision rule so it produces action, not just a number: when three or more bounces in a week land on the same checklist item, that item is next week's coaching focus. This converts the acceptance rate from a vanity metric into a diagnostic. If three of five bounces were "no confirmed economic buyer," the team doesn't need a vague "qualify harder" — it needs one specific drill on identifying and confirming the economic buyer. And if a lead that *passed* the bar keeps dying in discovery, the bar is missing a criterion and the sync revises it.

The counter-case: four ways this training backfires

A handoff process is a control, and every control has a failure mode. Name them so the room installs the method with eyes open instead of as cargo-cult ritual.

The bar becomes a blame engine. The instant acceptance rate is tied to SDR comp or stack-ranking, SDRs stop booking honest meetings and start gaming the brief — padding triggers, inventing budget awareness, coaching prospects to say the right words. Acceptance climbs while real pipeline falls. The mitigation is non-negotiable: the sync runs as coaching, never scoring, and acceptance rate never feeds comp. If you can't commit to that, don't install the bar — an informal handoff at least isn't lying to you.

Bounce latency kills more deals than the bad handoffs did. If AEs are at capacity and physically can't review briefs within a day, the gate adds latency without adding quality. The mitigation: fix AE capacity first. A gate a team has no time to operate is not a gate; it's a queue.

The artifact eats the selling time it was meant to save. A brief that creeps past four minutes, or a 25-minute sync that balloons to 50, quietly transfers cost from bad calls to admin overhead. The mitigation: audit the real time cost at the six-week mark and cut ruthlessly — tighten the brief, shorten the sync, drop any field nobody uses.

Wrong motion entirely. In a true high-velocity, sub-$5K PLG-adjacent inbound motion, a six-point bar is pure friction and speed-to-lead beats qualification depth. In a founder-led or single-rep org with no SDR/AE split, there's no handoff to standardize. The mitigation is honesty: be willing to say "not us." The skill is matching the bar to deal size, team maturity, and the management discipline available — and scaling it down, or skipping it, when the motion has no real handoff.

There's a fifth, subtler one for managers: the training can become a substitute for fixing a structural problem. If the comp plan pays purely on raw meeting volume, or the SDR-to-AE ratio is so lopsided AEs can't inspect every brief, no amount of bar-writing holds. Before committing to the bar as a quarterly ritual, check that the system *allows* a good handoff — quality in SDR comp, a ratio that leaves AEs time to inspect, and a CRM that can hold the brief. And because SDR ramp runs ~3.2 months and average tenure only ~1.5 years, the bar must be a written, teachable artifact, not a veteran's instinct — the person who learned it informally will be gone before it propagates.

Related questions

How long should the training run and who facilitates?

Sixty minutes is the standard: frame the cost, define the bar, build the brief, drill the bounce-back, install the sync, run the counter-case. The manager facilitates and the AEs participate — manager-led calibration produces the consensus a peer group actually adopts, which one-on-one coaching can't.

How is this different from an LMS certification?

An LMS teaches self-paced theory; this 60-minute session is the live working session where the team co-writes and agrees on the bar. Run both: the LMS covers the "what," the live training produces the shared vocabulary and the three artifacts nobody opens if handed down.

What cadence should we run it on?

Quarterly as a standing calibration, because the SDR bench turns over roughly every 18 months and the bar drifts back into private standards. Run it sooner after any quarter where booked meetings outran real pipeline, or when onboarding new SDRs or AEs before their habits set.

How do we know it's working?

Watch three signals weekly: acceptance rate climbing toward the 65% then 80% milestones, brief completion rate near 100%, and bounces landing within the 24-hour SLA. A passed lead dying in discovery means the bar is missing a criterion, not that the sync failed.

FAQ

What is the SDR-to-AE handoff, exactly? It's the transfer point where a prospecting-sourced meeting becomes an opportunity an AE will work. A clean handoff moves the buyer's real situation across the gap intact so the AE starts warm and the buyer never has to re-explain. Its one job is not filling a CRM stage — it's carrying a real, accepted opportunity.

What goes on the accepted-opportunity bar? Five or six items an SDR can verify live: a named pain or trigger, role and authority, a rough timeline, budget reality, confirmed attendees, and a reason it's happening now. Keep it to six — every item past that pushes the SDR past the 90-second cap and gets quietly skipped.

Should acceptance rate feed into SDR compensation? No. The moment a bounce costs the SDR money, they game the brief and the metric becomes misleading — acceptance climbs while real pipeline falls. Run the weekly sync as coaching, keep the number out of comp and stack-ranking, and inspect it as a diagnostic instead.

How long should the handoff brief be? Target 120–200 words, fillable in under four minutes. Longer and it gets skipped under quota pressure; shorter and it drops the buyer-language pain and the landmines. Optimize for completion rate, not completeness — a brief that's filled every time beats a thorough one filled once.

What if we run a high-velocity, low-ACV inbound motion? Then strip it down or skip it. A six-point bar and a brief on same-day, sub-$5K PLG deals is pure friction; speed-to-lead beats qualification depth there. Match the bar to deal size and cycle length, and be honest enough to say "not us" when there's no real handoff to standardize.

What's the single biggest mistake teams make? Letting the AE quietly drop weak leads instead of bouncing them back. A dropped lead teaches the SDR nothing, wastes a salvageable opportunity, and silently corrupts the acceptance number. Bounce better instead — one reason, a fix path, aimed at the artifact, within 24 hours.

Sources

• The Bridge Group — SDR Metrics & Compensation research: https://www.bridgegroupinc.com/
• Forrester (SiriusDecisions Demand Waterfall & B2B Buying Study): https://www.forrester.com/
• MEDDIC Academy — MEDDIC qualification methodology and its PTC origin: https://meddic.academy/
• HubSpot — sales qualification and BANT reframing: https://www.hubspot.com/
• Salesforce — State of Sales report: https://www.salesforce.com/resources/research-reports/state-of-sales/
• Gartner — B2B buying-journey and sales research: https://www.gartner.com/en/sales
• Gong — Gong Labs conversation-intelligence and speed-to-lead research: https://www.gong.io/
• Predictable Revenue (Aaron Ross) — the specialized SDR/AE split and defined handoff: https://predictablerevenue.com/
• IBM — origin of the BANT qualification frame: https://www.ibm.com/

Related on PULSE

• [The Discovery Call Reset — the 7-question framework a clean handoff feeds into](/knowledge/st0001)
• [Cold Call Openers — the SDR-side skill that earns the meeting upstream](/knowledge/st0004)
• [Demo Discipline — the same earned-right logic applied to demos](/knowledge/st0005)
• [The Forecast Call Reset — the weekly deal-inspection sync this training mirrors](/knowledge/st0037)
• [The Mutual Action Plan Co-Build — the late-stage artifact that keeps a handed-off deal from slipping](/knowledge/st0038)
• [60-Min Sales Training: AE-to-CSM Handoff That Doesn't Suck](/knowledge/st0477)