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

The outcome you should expect

The point of the Reboot is not a nicer deck — it is a measurable shift in how meetings convert to Stage 2 opportunities. Roughly a third of "booked meetings" in many B2B SaaS teams never become real pipeline, and the root cause is almost never the SDR's sourcing skill. It is a missing acceptance contract between the SDR who books and the AE who owns the deal after the handoff.

After a single 60-minute session, a team should walk out with three artifacts they use Monday morning, not a pledge to "communicate better." Concretely, expect the following inside one quarter. First, accepted-SQL rate becomes a real number your team quotes weekly, replacing the vanity metric of meetings held. Second, AE-SDR conflict drops because rejection has a defined workflow instead of living in passive-aggressive Slack DMs. Third, forecast accuracy improves because the meetings that enter Stage 2 have already cleared an objective bar rather than an optimistic guess.

The counterintuitive part: your headline "meetings booked" number will usually get *worse* in week one. That is the bar becoming real. SDRs stop submitting weak meetings because they now know an AE will reject them with a reason code. What matters is the downstream metric — accepted SQLs that reach Stage 2 within 30 days — which climbs as judgment recalibrates. If you measure only volume, you will misread the Reboot as a failure in its first fortnight; if you measure accepted, pipeline-converted dollars, you will see the shift by roughly week eight.

The other outcome is cultural and harder to put on a dashboard. When the AE leader stands up and says, on the record, "once I accept your SQL it is mine, I will not hand it back," the entire incentive to sandbag or to over-promise a champion's authority quietly evaporates. That single sentence, said out loud in front of the SDR team during the Training, does more than any process document, because it removes the political game where a struggling AE retroactively blames the SDR for a deal they accepted three weeks earlier. The Handoff stops being a blame handoff and becomes an ownership transfer.

What drives that outcome

The mechanism is simple: you replace a subjective "is this a good meeting?" argument with an objective pass/fail contract, and you attach money and ownership to that contract so both sides act on it. The 7-point SQL acceptance checklist is the spine of the Reboot. A meeting is not a qualified lead, and the checklist forces that distinction before an AE spends a discovery slot on it.

The seven points, each a simple pass/fail an AE can grade in under 60 seconds: right title (a decision-maker or direct influencer, confirmed on LinkedIn — "Manager of Ops" at a 5,000-person company is not a buyer for a six-figure product); right company fit (inside ICP on headcount, vertical, tech stack, and geography, with no "we'll stretch"); stated pain (a specific problem in the prospect's own words, not "interested in learning more"); trigger event (funding, leadership change, RFP, competitor churn — a reason to act now); discovery agenda agreed (the prospect knows what the next 30 minutes covers and said yes); calendar held (on the AE's calendar with a Zoom link, not "we'll find a time"); and authority to invite others (the champion can pull the economic buyer into call two). Set the acceptance bar at all seven for high-ACV motions, or a pragmatic 5-of-7 for faster mid-market sales cycles.

The second driver is the 3-part handoff: a warm intro email the SDR sends within 60 minutes of booking, a context doc the SDR fills and the AE reads before the call, and a discovery agenda the AE sends 24 hours pre-call. Most teams do part one and skip parts two and three — which is exactly why context evaporates between the book and the call, and why the AE walks in cold and re-qualifies from scratch.

The third driver is comp. A booked-meeting comp plan rewards volume; an accepted-SQL plan rewards judgment. A workable structure is 70% base and 30% variable, with the variable split roughly 60% on accepted SQLs and 40% on pipeline that reaches Stage 2 within 30 days. Critically, there is no clawback on accepted SQLs that later die in discovery — that is the AE's job to close or kill, and protecting SDR comp there is the financial half of the no-hand-back rule that makes the whole Reboot credible to the sales floor.

Benchmarks and realistic ranges

Set expectations with ranges, not a single hero number, because ACV and motion change every figure. Use these as calibration points, then measure your own baseline before and after the Training.

Meeting-to-Stage-2 leakage. Many B2B SaaS teams see 30-40% of booked meetings fail to become a real opportunity before any acceptance contract exists. That is the pool you are recovering. If your leakage is already under 20%, the Reboot will still help, but your gains will be smaller and mostly in forecast accuracy rather than raw conversion.

Time-to-impact. Expect 6-10 weeks before SDR judgment fully recalibrates to the new bar. The realistic curve: accept rates *drop* in week one as the bar becomes real, recover by roughly week four, and exceed the old "meetings booked" rate in pipeline-converted dollars by around week eight. Plan your executive communication around that dip so leadership does not pull the plug during the expected trough.

Acceptance-rate targets. A healthy steady-state AE acceptance rate sits around 70-80% of submitted SQLs. Below ~60% suggests SDRs still don't understand the ICP, or the AE is over-rejecting to protect calendar. Above ~90% usually means the checklist is being rubber-stamped and the bar isn't real.

AE rejection rate. Track this as a two-sided metric. An AE rejecting more than ~35% of well-formed SQLs gets coached the same way an SDR does — the process cuts both ways, which is the whole reason the sales team trusts it.

SLA compliance. The 4-hour accept/reject SLA should hit 90%+ within a month. Silence should default to auto-accept so passive ghosting carries a cost: the AE owns whatever they let slide past the window.

Cost per junk meeting. Make the stakes concrete for your own numbers. At a $60K ACV and a ~22% close rate, a discovery slot wasted on an unqualified meeting represents a few thousand dollars in weekly opportunity cost per AE. Run your own ACV and close rate through the same arithmetic in the room during the Training — the figure is almost always larger than the team assumes, and it reframes the checklist as revenue protection rather than process theater.

Two caution flags on benchmarks. First, do not import another company's absolute numbers as targets; import the *shape* of the curve and measure your own deltas. Second, a small team's numbers are noisier — one bad month of five meetings swings a percentage wildly — so weight trends over four to six weeks rather than reacting to any single week.

Risks, edge cases, and failure modes

The Reboot fails in predictable ways. Name them in the room during the Training so the team spots them early instead of discovering them in month three.

AEs reject everything to game the system. The most common failure. If accepted SQLs drive AE workload but rejections carry no scrutiny, a lazy or overloaded AE will reject aggressively to protect their calendar. Counter it by tracking AE accept rate alongside SDR performance and coaching any AE over ~35% rejection, plus the 4-hour SLA with auto-accept on silence, which removes the option to simply ghost a borderline SQL.

The reject-and-rebook loophole. Without a no-second-hand-back rule, AEs reject a meeting and then quietly ask the SDR to re-engage the same prospect later — which corrupts the conversion data and creates zombie leads. The fix is a firm policy: once an AE rejects an SQL, the prospect goes into a nurture sequence rather than back to the SDR for a fixed cooldown (a 90-day hold is common). If that prospect later closes from nurture, give the SDR partial credit so morale and honest rejection both survive.

Inbound treated as a free pass. Marketing-sourced leads frequently skip "stated pain" and "trigger event," and teams wave them through because they came from a form fill. Inbound gets the *same* seven points. The SDR still confirms pain and trigger before it becomes an accepted SQL — the handoff contract does not bend for lead source.

The checklist becomes a rubber stamp. If nobody audits accepted meetings, the seven points degrade into boxes everyone ticks. Counter with a weekly retro that pulls two or three accepted SQLs that died in discovery and grades them against the checklist honestly — those become coaching artifacts, not comp clawbacks.

Over-tooling a small team. A four-person team does not need Slack workflows and RevOps automation. Skip the tooling, keep the discipline: a shared Notion or doc page for the context doc, the checklist, and the 4-hour SLA. The cost of one bad meeting is *higher* as a percentage of a small team's capacity, so the discipline matters more, not less, when you're tiny.

Treating rejection as punishment. If rejections land in the SDR's DMs as blame, trust collapses and SDRs start hiding weak meetings instead of coaching around them. Route every rejection to the SDR manager with a reason code; the manager coaches, the AE goes back to selling, and nobody's ego is on the line. The sales culture survives the Reboot only if rejection stays clinical.

A practical rollout plan

Run the Training as six tight blocks inside the 60 minutes, then operationalize it over the following four weeks. The session is the sales Reboot; the four weeks are where the Handoff behavior actually sets.

The 60 minutes. Open cold (5 min): put the leakage number on the screen and name the cost out loud. Build the checklist (15 min): walk all seven points, then run a live drill where each SDR-AE pair grades one real meeting from last week's calendar, out loud and public. Build the 3-part handoff (10 min): show the warm intro email, the context doc fields, and the discovery agenda template. Install the rejection process (10 min): the 4-hour SLA, the mandatory reason code, and the no-drama routing to the SDR manager. Cover comp and the no-hand-back rule (15 min): put two SDRs and two AEs at the front, force specifics on where last week's handoffs broke, and have the AE leader say the no-hand-back line on the record. Close (5 min): three signed commitments on a single page, photographed and posted to the GTM channel.

The four weeks after. Switch comp to accepted SQLs starting the next pay period so the incentive matches the Training. Hold a 30-minute SDR-AE retro every Friday that reads the accept and reject codes from that week aloud — the codes are the curriculum for the next week's coaching. Almost every team surfaces the same three patterns early: agenda not sent, context doc skipped, and champion authority overstated. Those become named coaching themes, not blame. Rerun the full 60-minute Training quarterly, and open each session by reading the current accepted-SQL rate out loud so the room sees the trend line, not just the process.

Related questions

How is an accepted SQL different from a booked meeting?

A booked meeting is a calendar slot; an accepted SQL is a meeting an AE has reviewed against the 7-point checklist and formally taken ownership of. The difference is a contract plus accountability — comp and pipeline credit attach to acceptance, not to the booking.

Should SDR comp really move off booked meetings?

Yes. Paying on booked meetings rewards volume and invites weak bookings. Paying on accepted SQLs and Stage-2 pipeline rewards judgment. A 70/30 base-to-variable split with the variable weighted toward accepted SQLs aligns SDR behavior with pipeline quality inside a quarter.

What does the AE send before the discovery call?

A short discovery agenda roughly 24 hours pre-call: what prompted the conversation, how the pain shows up day to day, and whether there's a fit plus what a pilot looks like. It confirms the slot and invites the prospect to swap anything they'd rather cover.

How do we keep the checklist from becoming a rubber stamp?

Audit it. Each week, pull two or three accepted SQLs that died in discovery and grade them honestly against the seven points in the retro. Turn misses into coaching artifacts, never comp clawbacks, so honesty survives the Reboot.

FAQ

What if our AEs reject everything to game the system? Track AE accept rate alongside SDR performance. An AE rejecting more than about 35% of well-formed SQLs gets coached the same way an SDR does. The 4-hour SLA with auto-accept on silence also prevents passive-aggressive ghosting — silence means the AE owns the outcome.

Does the no-hand-back rule mean AEs are stuck with bad meetings forever? No. They can disqualify a deal at any stage. But once they accepted the SQL, the SDR keeps comp credit. The rule only blocks the political game where a struggling AE retroactively blames the SDR for a deal they accepted three weeks earlier.

We're a 4-person sales team. Is this overkill? No. At a small team, one bad meeting costs a bigger share of total capacity. Skip the formal Slack channels — use a shared doc — but keep the checklist, the 3-part handoff, and the 4-hour SLA. The discipline matters more than the tooling.

How do we handle inbound SQLs from marketing-sourced leads? Same checklist, same handoff. Inbound is not a free pass on the seven points. Marketing-sourced leads often skip "stated pain" and "trigger event," so your SDR still confirms both before the meeting becomes an accepted SQL.

What's the right cadence to retrain on this? Run the full 60-minute Training quarterly, and run a 15-minute retro every Friday reading that week's accept and reject codes. The reason codes are the curriculum — they tell you exactly what to coach next.

How long before we see the accept rate move? Expect 6-10 weeks before SDR judgment recalibrates to the new bar. Accept rates typically dip in week one when the bar becomes real, recover by week four, and exceed the old booked-meeting rate in pipeline-converted dollars by around week eight.

Sources

• Bertuzzi, Trish. *The Sales Development Playbook* (2016) — https://www.bridgegroupinc.com/the-sales-development-playbook
• Ross, Aaron and Marylou Tyler. *Predictable Revenue* (2011) — https://predictablerevenue.com/
• Roberge, Mark. *The Sales Acceleration Formula* (2015) — https://www.markroberge.com/
• The Bridge Group — SDR metrics and compensation research — https://www.bridgegroupinc.com/research
• Pavilion — go-to-market benchmarks and research — https://www.joinpavilion.com/
• Weinberg, Mike. *Sales Management. Simplified.* (2015) — https://mikeweinberg.com/books/
• SaaStr — SDR-to-AE handoff commentary — https://www.saastr.com/
• HubSpot Sales Blog — SDR-AE handoff and SLA guidance — https://blog.hubspot.com/sales

Related on PULSE

• [The Inbound Lead Handoff Reboot — 60-Min Training](/knowledge/st227)
• [The Discovery-to-Demo Handoff Reboot — 60-Min Training](/knowledge/st218)
• [The Sales-to-CS Handoff Reboot — 60-Min Training](/knowledge/st188)
• [Top 10 sales enablement drills for PLG handoff reps](/knowledge/st0644)
• [Top 10 sales training workshops for PLG handoff teams](/knowledge/st0643)

Recently Added — Related

• [The BANT Qualification Reboot — 60-Min Training](/knowledge/st164)