The SDR-to-AE Handoff: How to Write It Down So It Actually Works

Most SDR-to-AE handoffs fail silently. The lead gets marked "handed off" in the CRM, the AE sees it three days later, and all the momentum the SDR spent two weeks building has evaporated. The prospect has moved on mentally. The AE starts cold.

The instinct is to blame the AE for slow follow-up or the SDR for poor qualification. But the real problem is almost always structural: the handoff process isn't written down with enough specificity for anyone to follow consistently.

This isn't a culture problem. Culture can't fix a missing SLA. Documentation can. And how well you document the handoff determines whether your pipeline stages actually reflect reality or just wishful thinking.

Here's how to write a handoff process specific enough that a rep hired on Monday can follow it without ambiguity.

---

Why Verbal Handoffs Fail

When you ask reps how the handoff works, the answer is usually some version of: "The SDR books a meeting, drops a note in Salesforce, sends the AE a Slack message, and the AE takes it from there."

Research from Forrester has found that poorly structured SDR-to-AE handoffs are one of the top contributors to pipeline leakage in B2B sales organizations.

That process has four failure points:

1. "drops a note in Salesforce": what note? How long? What format?
2. "sends the AE a Slack message": and if the AE doesn't see it for 6 hours?
3. "the AE takes it from there": when? What counts as "taking it"?
4. No feedback loop: the SDR never finds out whether the AE used their research

The result is a handoff that depends entirely on the relationship between a specific SDR and a specific AE. It doesn't scale. It doesn't survive turnover. And it can't be coached or improved because nobody agrees on what "good" looks like.

The goal of documenting the process is to make every handoff look like your best handoff, regardless of which SDR and AE are involved. It's the same logic behind writing a sales playbook new hires will actually read: if the process only lives in people's heads, it dies the moment those people leave.

---

Step 1: Define the Handoff Trigger

Before anything else, agree on what conditions must be true before an SDR can mark a lead as handed off.

This sounds obvious. It isn't. Most teams have a vague rule like "the meeting is booked," but what counts as booked? A calendar invite accepted? A verbal agreement on a call? A "yes" in a LinkedIn message with no scheduled time?

Document the trigger criteria explicitly:

Minimum handoff conditions (all must be true):

• Calendar invite accepted by at least one prospect contact
• ICP criteria confirmed (company size, industry, role level)
• Qualification threshold met (minimum score or explicit criteria from your qualification framework)
• SDR has spoken to or exchanged meaningful messages with the prospect (no cold calendar drops)

You can add deal-specific criteria (budget authority confirmed, specific pain articulated), but keep the minimum bar achievable without over-qualification that slows the pipeline. The handoff record handles the rest.

---

Step 2: The Handoff Record, Five Required Fields

The handoff record is what transfers the SDR's institutional knowledge to the AE. It's not a novel. It's not a bulleted summary of every conversation. It's five specific fields, filled out before the handoff trigger is marked complete.

Field 1: Pain stated in the prospect's own words

Not your interpretation. Not "they need better pipeline visibility." The actual sentence the prospect used: "Our reps spend 20 minutes a day updating Salesforce and still miss half the fields."

This matters because it tells the AE what language to reflect back in the first meeting.

Field 2: Next meeting details

Date, time, format (video/in-person), confirmed attendees, and the agreed-upon agenda. One sentence is enough: "30-minute Zoom on Tuesday at 2pm ET with Sarah (VP Sales) and James (Sales Ops). Agenda: walk through current reporting pain and demo pipeline dashboard."

Field 3: Stakeholders identified

Everyone the SDR spoke to or knows about in the account: name, title, role in the deal (decision-maker, evaluator, gatekeeper, end user). Even people the SDR didn't connect with but knows exist.

Field 4: Objections surfaced

What pushback came up, and how the SDR handled it. Not just "they mentioned price." Write the specific objection and the response: "Asked about cost vs. current tool. I said we'd cover ROI in the demo. Didn't push further."

Field 5: Competitor mentioned

Any competitor named by the prospect, directly or indirectly. If none came up, say "none mentioned."

That's it. Five fields. Any AE who reads a complete record should be able to walk into the first meeting prepared without a 30-minute briefing call.

---

Step 3: SLA for First AE Touch

Set a time-based SLA for when the AE must make their first substantive contact with the prospect after the handoff.

"As soon as possible" is not an SLA. It's an aspiration that looks different to every AE.

According to Harvard Business Review, companies that contact leads within an hour are nearly seven times more likely to qualify them than those that wait longer. The standard most sales operations teams recommend: 4 hours from handoff completion during business hours. Not 24 hours. Not "same day."

Document what counts as a first touch:

• Personalized reply to the SDR's warm intro email (see Step 4)
• Calendly confirmation or direct calendar invite sent
• Personal video message or note acknowledging the meeting

A calendar invite that's already on both calendars doesn't count. The AE needs to make actual contact.

SLA table:

Escalation trigger: If the SLA passes without AE acknowledgment, the SDR notifies the sales manager directly. Not passive-aggressively, not as a complaint. Just a flag: "Hey, the [Company] handoff from this morning hasn't been touched. Wanted to flag it."

---

Step 4: The Warm Introduction Email

The SDR sends a warm intro email that formally transfers the relationship to the AE. This email has a specific structure.

SDR writes:

• Subject line referencing the conversation (not a generic "Introduction")
• One sentence about what was discussed and the prospect's stated interest
• A brief, genuine statement about why the AE is the right person ("Calvin works exclusively with VP-level sales leaders navigating CRM consolidations")
• The meeting confirmation and what to expect

AE adds (within the first touch SLA):

• A direct reply to the same thread (don't start a new email)
• A personal sentence specific to the prospect's pain (shows they read the handoff record)
• Any logistical additions or agenda clarification

CC logic:

• SDR stays on the first AE email
• SDR drops off after the AE's first reply
• No internal Slack threads copied in as a reply chain (this happens more often than you'd think)

Sample subject line format: "Sarah, intro to Calvin + Thursday's agenda"

---

Step 5: AE Acceptance Criteria

"Accepting" the handoff isn't passive. It's an explicit action that signals the AE has reviewed the record and taken ownership of the next step.

Document the acceptance actions:

• Opened and reviewed the handoff record in CRM
• Updated deal owner field to AE
• Sent first touch within SLA
• Added personal prep notes to the deal record (optional but encouraged)

Some teams use a simple Slack convention: the AE replies to the handoff notification with a thumbs up or short note. Others use a CRM field the AE checks off. Either works. The point is that "accepted" means something observable, not just that the AE didn't reject it.

---

Step 6: The SDR Feedback Loop

The process doesn't end at the first AE touch. SDRs need to know whether their qualification was accurate, because that's the only way they improve.

A McKinsey study on B2B sales excellence highlights that cross-functional feedback loops between prospecting and closing roles are a hallmark of top-performing sales organizations.

Document what AEs owe SDRs after the first meeting with the prospect:

1. Outcome: meeting held, rescheduled, or no-showed
2. Qualification quality score: did the prospect match what was in the handoff record? (1-5 scale or simple yes/no)
3. Anything wrong in the record: factual errors or missing context that the AE had to re-discover

This feedback doesn't need to be formal. A two-sentence Slack message works. But it needs to happen within 24 hours of the first meeting.

Why does this matter? Because SDRs who never get feedback on their handoffs either over-qualify (slowing pipeline) or under-qualify (wasting AE time) without knowing which. Feedback is the only mechanism for calibration.

---

Common Pitfalls

According to Gartner research on B2B buying behavior, buyers now complete 57–70% of their purchase decision process before engaging a sales rep, making the quality of information captured during SDR outreach even more consequential.

Handing off too early. Some SDRs, under pressure to hit meeting volume metrics, hand off prospects who haven't confirmed a real pain or a real meeting. The AE ends up doing discovery the SDR was supposed to do. Fix: reinforce the trigger criteria and check them in your weekly pipeline review.

AEs who ignore the handoff record. If an AE routinely shows up to first meetings unprepared because they didn't read the record, that's a coaching conversation about professionalism, not a process failure. But if multiple AEs skip it, the record is probably too long or too burdensome to fill out. Simplify the five fields before adding more.

SDRs who over-qualify and slow the pipeline. Some SDRs get so thorough that they turn a 5-day qualification cycle into 15 days. The handoff record is meant to transfer information, not replace the AE's job. If your SDRs are doing full demo calls before handoff, pull the trigger criteria back.

---

Handoff Record Template

HANDOFF RECORD: [Company Name] | [Date]
SDR: [Name] | AE: [Name]

TRIGGER CONDITIONS (check all before marking handed off):
[ ] Calendar invite accepted
[ ] ICP criteria confirmed
[ ] Qualification threshold met
[ ] Meaningful contact established

1. PAIN (prospect's exact words):


2. NEXT MEETING:
   Date/Time:
   Format:
   Attendees:
   Agenda:

3. STAKEHOLDER MAP:
   Name | Title | Role in deal
   ---  | ---   | ---

4. OBJECTIONS SURFACED:
   Objection:
   How handled:

5. COMPETITOR MENTIONED:


WARM INTRO EMAIL STATUS: [ ] Sent by SDR
AE FIRST TOUCH: [ ] Completed within SLA

---

What to Do Next

Start with an audit, not a redesign. Pull the last 30 handoffs from your CRM and ask three questions for each:

1. Does a complete handoff record exist (all five fields)?
2. Did the AE make first contact within the SLA window?
3. Did the SDR receive feedback within 24 hours of the first meeting?

You'll almost certainly find the same two failure modes repeating. Fix those first. Most teams discover that the record isn't being filled out completely, and the SLA isn't being enforced at all. Those two changes alone will noticeably reduce the time between handoff and first substantive AE contact.

Once the basics are consistent, add the feedback loop. That's the part most teams skip, and it's the part that improves SDR qualification quality over time. If you're also seeing deals stall shortly after handoff, the diagnostic process in fixing stalled mid-pipeline deals applies just as well to early-stage stalls.

---

Learn More

• Designing pipeline stages that match how customers actually buy
• Qualification frameworks: BANT, MEDDIC, GPCT
• Running a weekly pipeline review that doesn't waste an hour
• Sales rep CRM training that actually sticks