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

Question

Pulse RevOps · The Machine · Accepted Answer

### Direct Answer

> **TL;DR.** The SDR-to-AE handoff is the single most leaked stage in B2B SaaS pipeline — Bridge Group's 2025 SDR research shows roughly 38% of "booked meetings" never convert to a Stage 2 opportunity, and the root cause is almost never the SDR's sourcing skill. It's a missing **SQL acceptance contract**. Run this 60-minute training to ship three artifacts your team will use Monday morning: (1) a 7-point **SQL acceptance checklist** every meeting must pass, (2) a **3-part handoff template** (warm intro email + context doc + discovery agenda), and (3) an **AE rejection process** with a **"no second hand-back"** rule. Tie SDR comp to *accepted* SQLs, not booked meetings, and pipeline quality jumps inside one quarter.

---

## 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.

```mermaid
flowchart TD
    A[SDR books meeting] --> B{7-point checklist}
    B -->|All 7 pass| C[Submit as SQL]
    B -->|Any fail| D[Coach + rebook or disqualify]
    C --> E{AE reviews within 4 business hours}
    E -->|Accept| F[SQL counted, comp credit]
    E -->|Reject with reason code| G[Coaching loop — SDR Mgr owns]
    G --> H[Rebook only if pain + trigger + title fixable]
    H --> A
    F --> I[Discovery call held]
```

**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

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

Direct Answer

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

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

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

Section 4 — The AE Rejection Process (10 min)

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

Section 6 — Commitments & Close (5 min)

FAQ

Sources

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

Direct Answer

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

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

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

Section 4 — The AE Rejection Process (10 min)

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

Section 6 — Commitments & Close (5 min)

FAQ

Sources

What does the score mean?