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

Section 1 — Open & Frame the Problem (5 min)

Open cold. Put one number on the screen: "38%." Then say verbatim:

> *"Thirty-eight percent of the meetings we booked last quarter never became real opportunities. That isn't an SDR problem. That isn't an AE problem. That's a handoff problem — and we're fixing it in the next 55 minutes."*

Set the three deliverables on the whiteboard:

• SQL acceptance checklist — the bar every meeting must clear before an AE owns it.
• 3-part handoff — warm intro, context doc, discovery agenda.
• Rejection + no-hand-back rules — how AEs push back without breaking trust, and why a rejected SQL never bounces a second time.

Name the cost out loud. At a $60K ACV and a 22% close rate, every junk SQL that eats a discovery slot costs roughly $2,900 in opportunity cost per AE per week (Roberge's *Sales Acceleration Formula*, ch. 6). This isn't process theater. It's revenue.

---

Section 2 — The 7-Point SQL Acceptance Checklist (15 min)

Trish Bertuzzi's *Sales Development Playbook* makes the point bluntly: "A meeting is not a qualified lead." Walk the room through the checklist below, then have every SDR and AE sign it at the end of the meeting.

The SQL Acceptance Checklist — all 7 must be true:

• Right title. Decision-maker or *direct* influencer. "Manager of Ops" at a 5,000-person company is not a buyer for a $120K ACV product. Confirmed on LinkedIn at time of book.
• Right company fit. Inside ICP — headcount, vertical, tech stack, geography. No "we'll stretch."
• Stated pain. SDR captured a specific problem in the prospect's own words. Not "interested in learning more."
• Trigger event. Funding, leadership change, RFP, competitor churn, new initiative — a *reason now*.
• Discovery agenda agreed. Prospect knows what the next 30 minutes covers and said yes to it.
• Calendar held. On the AE's calendar with a Zoom link, not "we'll find a time."
• Authority to invite others. Champion can pull in the economic buyer for call two.

Drill (5 min). Pair SDR + AE. Each pair takes one real meeting from last week's calendar and grades it against the 7 points. Score out loud. Public.

---

Section 3 — The 3-Part Handoff Template (10 min)

Aaron Ross's *Predictable Revenue* called this "the seamless handoff." Most teams do part one and skip parts two and three. All three are mandatory.

Part 1 — Warm intro email (SDR sends within 60 minutes of booking):

> *"Hi [Prospect], introducing [AE Name], who'll lead our conversation Thursday at 2pm ET. [AE] has worked with [2 named customers in same vertical] on [the specific pain you mentioned: e.g., revenue leakage across CS handoffs]. Ahead of the call, [AE] will send a short agenda. Anything you want us to dig into beyond what we discussed? — [SDR]"*

Part 2 — Context doc (SDR fills, AE reads before the call):

• Account snapshot: company, headcount, ARR if known, funding stage.
• Buyer: name, title, tenure, LinkedIn link, reports to whom.
• Pain in their words: direct quote, dated.
• Trigger: what changed, when.
• Tools they use: stack named on the call.
• Objections raised: what the SDR already heard.
• What they asked for: demo, case study, pricing range, references.
• Champion read: how engaged on a 1-5 scale, why.

Part 3 — Discovery agenda (AE sends 24 hours pre-call):

> *"Hi [Prospect] — confirming Thursday 2pm ET. Plan for our 30 minutes: (1) 5 min on what prompted the conversation, (2) 15 min on how [pain] shows up in your day, (3) 10 min on whether we're a fit and what a pilot would look like. Reply if you'd swap anything. — [AE]"*

---

Section 4 — The AE Rejection Process (10 min)

Pavilion's 2025 RevOps benchmarks are explicit: teams without a formal SQL rejection workflow report 2.3x higher SDR-AE conflict and 40% worse forecast accuracy. Rejection is not punishment — it's the only way the checklist has teeth.

The rejection rules:

• 4-hour SLA. AE accepts or rejects every SQL within four business hours. Silence = auto-accept, and the AE owns the outcome.
• Reason code required. Pick one of seven: wrong title, wrong ICP, no pain, no trigger, no agenda, no calendar hold, no authority. Free-text optional, code mandatory.
• No drama. Rejections go to the SDR manager, not the SDR's Slack DMs. Manager coaches; AE goes back to selling.
• The "no second hand-back" rule. Once an AE *accepts* an SQL, it is theirs. No bouncing it back at hour 25 because discovery went sideways. If the meeting reveals it shouldn't have passed, it becomes a coaching artifact for next week's training — not a comp clawback.

---

Section 5 — Comp, Conflict, and the "No Second Hand-Back" Rule (15 min)

Mark Roberge's HubSpot data — and every Bridge Group report since 2021 — points the same direction: pay SDRs on accepted SQLs, not booked meetings. A booked meeting comp plan rewards volume; an accepted-SQL plan rewards judgment.

Recommended structure (adjust to your ACV):

• 70% base, 30% variable.
• Variable splits: 60% on accepted SQLs (the 7-point bar cleared and AE accepted), 40% on pipeline sourced (SQLs that reach Stage 2 within 30 days).
• No clawback on accepted SQLs that later die in discovery — that's the AE's job to close or kill. This is the comp half of the no-hand-back rule.
• Accelerator: once SDR exceeds quota, accepted-SQL rate above 75% triggers a 1.25x multiplier on incremental SQLs.

Run this conversation live (10 min). Put two SDRs and two AEs at the front. Ask each pair: *"Last week, where did the handoff break?"* Force specifics. Write the patterns on the board. Almost every team will surface the same three: agenda not sent, context doc skipped, champion's authority overstated. Those become next week's coaching themes — not blame.

End the section with the rule said out loud, by the AE leader, on the record:

> *"Once I accept your SQL, it's mine. I will not hand it back. If it falls apart in discovery, that's on me to close or kill — and on us together to learn from. Your comp is safe."*

That sentence, said by the AE leader in front of the SDR team, is worth more than any deck.

---

Section 6 — Commitments & Close (5 min)

Walk out with three signed commitments on a single page:

• SDR commitment: every SQL submitted with the 7-point checklist filled and the 3-part handoff completed within 60 minutes of booking.
• AE commitment: accept or reject within 4 business hours with a reason code; once accepted, no hand-backs.
• Manager commitment: weekly 30-min SDR-AE retro reviewing rejection codes, comp paid on accepted SQLs starting next pay period.

Put the page on the wall. Photo it. Send it to the GTM Slack channel by EOD. Next week's training opens by reading the accepted-SQL rate aloud.

---

The 7-Point SQL Acceptance Checklist

This is the core artifact your team will use daily. It forces AEs to accept or reject a meeting within 2 hours of booking, using objective criteria:

1. Contactability — SDR confirmed the prospect answered a live call or replied to a same-day email (voicemail-only doesn't count).
2. Budget authority — Prospect mentioned a budget range or confirmed they can influence purchasing decisions.
3. Need clarity — Prospect articulated a specific pain point that matches your product's top 3 use cases.
4. Timeline — Prospect has an active initiative or known pain within the next 90 days.
5. Decision process — Prospect named at least one other stakeholder or the buying group structure.
6. Fit flags — Company size, industry, and tech stack match your ICP (no more than 2 disqualifiers).
7. Meeting readiness — Prospect agreed to a 30-minute calendar slot with a specific agenda.

Each criterion is a simple pass/fail. A meeting must pass 5 of 7 to be accepted. Train your team to score meetings in under 60 seconds.

The No Second Hand-Back Rule

AEs often reject a meeting, then later ask the SDR to re-engage the same prospect. This kills pipeline trust and creates "zombie leads." Your training should establish a firm no second hand-back policy: once an AE rejects an SQL, the SDR is prohibited from re-contacting that prospect for 90 days. The prospect goes into a nurture sequence instead.

This forces AEs to be honest about rejection upfront. If an AE rejects a meeting that later closes from nurture, the SDR still gets partial credit (typically 10–15% of the commission). This protects SDR morale and prevents the "I'll just reject and rebook later" loophole that destroys conversion data.

The Warm Intro Email Template

Your handoff template should include a 3-sentence warm intro the AE sends within 1 hour of acceptance:

*"Hi [Prospect], [SDR Name] mentioned you're exploring [specific pain]. I've been helping [similar company] solve this with [your approach]. Would love to spend 25 minutes on [day/time] to explore if there's a fit — here's what I've prepared based on our chat."*

The AE copies the SDR on the email. This preserves context, shows the prospect the handoff is seamless, and gives the SDR visibility into whether the AE actually followed through. Train your team to send this within 60 minutes of acceptance — any delay drops conversion by roughly 20%.

FAQ

Q: What if our AEs reject everything to game the system? A: Track AE accept rate alongside SDR accept rate. An AE rejecting more than 35% of SQLs gets coached by the VP of Sales the same way SDRs get coached. The rejection process cuts both ways — and the 4-hour SLA with auto-accept on silence prevents passive-aggressive ghosting.

Q: Does the no-hand-back rule mean AEs are stuck with bad meetings forever? A: No — they can disqualify a deal at any stage. But the SDR keeps comp credit for the accepted SQL. The rule prevents the political game where a struggling AE retroactively blames the SDR for a deal they accepted three weeks ago.

Q: We're a 4-person sales team. Is this overkill? A: No. At a small team, the cost of one bad meeting is *higher* as a percent of total capacity. Skip the formal Slack channels — use a shared Notion page — but keep the checklist, the 3-part handoff, and the 4-hour SLA. The discipline matters more than the tooling.

Q: How do we handle inbound SQLs from marketing-sourced leads? A: Same checklist, same handoff. Inbound is *not* a free pass on the 7 points. Marketing-sourced leads often skip "stated pain" and "trigger event" — your SDR still has to confirm both before passing.

Q: What's the right cadence to retrain on this? A: Run the full 60-min training quarterly. Run a 15-min retro every Friday reading the accept/reject codes from that week. The codes are the curriculum.

Q: How long before we see the accept rate move? A: Bertuzzi and Bridge Group both put it at 6-10 weeks before SDR judgment recalibrates to the new bar. Expect accept rates to *drop* in week 1 (the bar is real now), recover by week 4, and exceed the old "meetings booked" rate by week 8 in pipeline-converted dollars.

---

Related on PULSE

• [The SDR-to-AE Handoff — 60-Min Training](/knowledge/st0040)
• [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)

Sources

• Bertuzzi, Trish. *The Sales Development Playbook* (2016) — chapter 5, "Service Level Agreements," and chapter 7, "Specialization."
• Ross, Aaron and Marylou Tyler. *Predictable Revenue* (2011) — "The Seamless Handoff" section, ch. 4.
• Roberge, Mark. *The Sales Acceleration Formula* (2015) — ch. 6 on SDR-AE economics and comp design.
• Bridge Group. *2025 SDR Metrics & Compensation Report* — bridgegroupinc.com/sdr-metrics-2025.
• Pavilion. *2025 Sales Development Benchmarks* — pavilion.com/research/sdr-benchmarks-2025.
• Weinberg, Mike. *Sales Management. Simplified.* (2015) — chapter on accountability cadences.
• Konrath, Jill. *Agile Selling* (2014) — handoff rituals in fast-cycle B2B SaaS.
• SaaStr. "The SDR-to-AE Handoff: What Actually Works" — saastr.com/sdr-ae-handoff-2024.