Published by the SELLIGNITE team. A practical operating model with examples and checks that show whether it is working. Examples are illustrative unless stated otherwise.
A good SDR to AE handoff passes six facts in the CRM within 24 hours of booking: why the account fits, the trigger, the problem in the buyer's own words, who is attending, what was promised and the agreed next step. The SDR sends a short warm intro, the account executive confirms the meeting the day before, and the handoff is judged by meetings held and accepted, not meetings booked.
- A booked meeting is only half done until the account executive accepts it and it actually takes place.
- Six facts make a complete handoff: fit, trigger, problem, attendees, promises made and next step.
- The handoff note belongs in the CRM within 24 hours, not in a chat message.
- A warm intro email from the SDR and a confirmation the day before reduce no-shows.
- Measure meetings held, meetings accepted by the AE and the reason any meeting was rejected.
- 01Book with context
- 02Write the handoff note
- 03Send the warm intro
- 04Confirm the day before
- 05Review accepted meetings
What is an SDR to AE handoff?
An SDR to AE handoff is the moment a sales development rep (SDR) passes a booked meeting to the account executive (AE) who will run it. It includes the information the AE needs to prepare, the introduction the buyer receives and the rules for what happens if the meeting is rejected, moved or missed.
The handoff exists because of specialization. In the Predictable Revenue model, prospecting and closing are separate jobs, which lets each person get good at one thing. The cost of that split is a gap in the middle: the person who earned the buyer's attention is not the person who shows up to the call. We covered why the split is still worth it in Predictable Revenue and SDR specialization. This checklist is about closing the gap.
Small teams have the same gap even without job titles. When a founder books calls and a salesperson runs them, or an AI agent books calls and a person runs them, the same six facts have to travel with the meeting.
Why do booked meetings go cold after the handoff?
Booked meetings usually go cold for one of three reasons: the AE walks in without context, the buyer forgets why they agreed, or nobody agreed what counts as a meeting worth booking. All three are process problems, and all three are cheap to fix.
- No context. The AE opens with "so tell me about your business" and the buyer, who already explained the problem to the SDR, feels they are starting over.
- No bridge. The calendar invite arrives from a name the buyer has never seen, with a generic title. A week later it looks like spam.
- No shared bar. The SDR is paid on booked meetings, the AE is measured on pipeline, and the two disagree about which meetings were worth booking. The argument happens after the meeting, when it is too late.
The fix for the third reason comes first, because it changes what gets booked. Agree in writing what a qualified meeting is. Our lead qualification framework for SMBs uses four questions (fit, problem, owner, priority) and treats a lead with no "no" and at least two "yes" answers as a qualified meeting. Use that or your own rule, but write it down and have both roles sign off on it.
The SDR to AE handoff checklist: six facts to pass on
The SDR to AE handoff is complete when the AE can read one note and know why the meeting exists. These six facts are the minimum. Each should take one or two lines.
| Fact | What to write | Why the AE needs it |
|---|---|---|
| 1. Fit | Which ICP criteria the account meets: size, model, market | Confirms the account is worth an hour |
| 2. Trigger | The event that started the outreach: new leader, hiring push, expansion | Gives the AE a natural opening line |
| 3. Problem | The problem in the buyer's own words, quoted from the reply or call | Lets the AE skip generic discovery |
| 4. Attendees | Who is coming, their role, and who else owns the decision | Shows whether a second meeting will be needed |
| 5. Promises | Anything the SDR offered: a demo, a benchmark, a short agenda | Prevents the buyer from being let down |
| 6. Next step | What the buyer expects the call to produce | Sets the goal for the meeting |
Add the full thread: the emails, the LinkedIn messages and call notes that led to the booking. The AE should be able to see the exact words the buyer used. The trigger often comes from a buying signal spotted before outreach, so it should already be on the account record.
If the SDR cannot fill in the problem line, that is useful information. It usually means the meeting was booked on curiosity rather than need, and the AE should plan a shorter, more exploratory call.
When should the handoff happen, and where should it live?
The handoff note should be in the CRM within 24 hours of booking, attached to the opportunity or meeting record. Not in Slack, not in a forwarded email, and not in the SDR's head.
Three timing rules cover most teams:
- Within 24 hours of booking: the SDR writes the note and sends the warm intro email.
- Within one working day of the note: the AE reads it and either accepts the meeting or sends it back with a reason.
- The working day before the meeting: the AE sends a short confirmation with the agenda.
Using the CRM matters for two reasons. The note survives if the SDR leaves or the meeting moves, and the fields can be required, so a meeting cannot be marked as booked without them. In HubSpot, Pipedrive or Salesforce this is a handful of required properties on the meeting or deal stage. If your stages are a mess, fix that first; it is the same discipline behind every outbound pipeline metric worth tracking.
How should the warm intro and the first call work?
The warm intro is a short email from the SDR to the buyer, copying the AE, sent the same day the meeting is booked. It reminds the buyer why they agreed, introduces the AE by name and role, and restates the agenda in one line.
On the first call, the AE should open by playing back what the SDR learned: the trigger, the problem in the buyer's words and the goal of the call. Then ask whether anything has changed. This does two jobs. It shows the buyer they were heard, and it tests whether the SDR's notes were accurate.
Should the SDR join the first call? For most small teams, no. A short intro on the call can help when the SDR built real rapport over several conversations, but two sellers on a first meeting can feel like pressure. A clean note and a warm email usually do more than a third person on the line.
Example: a handoff note and a warm intro email
Imagine an SDR at a company that sells inventory software to wholesale distributors. The SDR has booked a call with the operations manager of a regional food distributor that recently opened a second warehouse. This example is illustrative, not a client case.
Handoff note in the CRM:
- Fit: wholesale distributor, about 80 people, two warehouses, matches our ICP for size and model.
- Trigger: opened a second warehouse this quarter, announced on their website.
- Problem (her words): "We keep finding stock in the wrong building and nobody trusts the spreadsheet."
- Attendees: operations manager. The finance director signs off on software; not attending this time.
- Promises: I said the AE would show how other distributors track stock across two sites. No pricing promised.
- Next step she expects: to decide whether a proper trial is worth her time.
Warm intro email, sent the same day:
Subject: Thursday, stock across two warehouses
Hi Anna, thanks for making time. As promised, I am introducing Jordan, who works with distributors running more than one warehouse. Jordan has the notes from our call, so you will not need to repeat the spreadsheet story. Thursday's goal: see whether tracking stock across both sites is worth a proper trial. Jordan will send a short agenda the day before.
Confirmation from the AE, the day before: "Looking forward to tomorrow. I will cover how teams track stock across two sites and leave time for your questions. If it would help to have someone from finance join, they are welcome, but not needed this time."
Notice that every line can be written from the six facts. Nothing in the email is new to the buyer, and that is the point: the handoff should feel like one continuous conversation.
Where AI agents help with the handoff
AI agents are well suited to the clerical part of the SDR to AE handoff. An agent can draft the handoff note from the email thread and call transcript, pull the trigger and firmographics from the account record, flag missing fields before the meeting is marked as booked, and draft the warm intro for the SDR to approve. It can also remind the AE when a note has been waiting more than a day.
A person should still check the problem line, because agents tend to smooth a buyer's words into generic language, and the buyer's exact phrasing is what makes the first call land. We draw the same line in what an AI SDR can and cannot do. When we build outbound sales systems, the handoff is one of the first pieces we automate: agents prepare and remind, people decide and talk.
Your implementation checklist
- Write down what counts as a qualified meeting and get both roles to agree
- Add the six handoff fields to the CRM and make them required
- Send a warm intro email within 24 hours of every booking
- Have the AE accept or reject each meeting within one working day
- Send a confirmation with the agenda the day before the call
- Review held, accepted and rejected meetings with reasons every week
What to measure: Track meetings held as a share of meetings booked, meetings accepted by the AE, rejection and no-show reasons, and how many held meetings become qualified opportunities.
Frequently asked questions
What should an SDR include in a handoff note?
An SDR handoff note should include six facts: why the account fits the ICP, the trigger that started outreach, the problem in the buyer's own words, who is attending, anything the SDR promised and the next step the buyer expects. The full email and call history should be attached. Each fact should take one or two lines.
How quickly should an SDR hand off a booked meeting to an account executive?
Within 24 hours of booking. The SDR writes the note in the CRM and sends a warm intro email the same day, and the AE accepts or rejects the meeting within one working day. Faster is better, because the buyer's memory of the conversation fades quickly.
Should the SDR join the first meeting with the account executive?
Usually not. A complete handoff note and a warm intro email give the AE what they need, and two sellers on a first call can feel like pressure. A short introduction on the call can help when the SDR built a strong relationship over several conversations.
What happens when an account executive rejects a booked meeting?
The AE records a reason from a short fixed list, such as poor fit, wrong person or no clear problem, and the SDR decides whether to keep, move or cancel the meeting politely. Rejection reasons should be reviewed weekly, because a pattern usually points to a qualification rule that needs to change.
How do you measure the quality of an SDR to AE handoff?
Measure meetings held as a share of meetings booked, meetings accepted by the AE, and how many held meetings become qualified opportunities. Track rejection and no-show reasons alongside them. Meetings booked on its own is not enough, because it rewards booking calls that never happen or go nowhere.