An SDR to AE handoff note tells the AE what the buyer replied to, in the buyer's words, so the first meeting starts where the outreach left off. Copy the block below into your CRM's meeting note or your team's handoff channel. The process around it is in how to coach the SDR to AE handoff, and the outbound motion that leads up to it is in our SDR coaching guide.
The template
SDR TO AE HANDOFF
Account: [company]
Buyer: [name, title]
Meeting: [date, time, length] Booked by: [SDR] AE: [name]
1. Replied to: [the problem your outreach named, in one sentence]
2. Their words: "[what the buyer wrote or said, quoted]"
3. Also in the account: [names and roles you found, and why each matters]
4. Unproven: [what you do not know yet: owner, budget, size of problem, timing]
Touch that earned the reply: [email 1 / call 2 / LinkedIn 3 ...]
Research links: [the two or three sources behind line 1]
The four numbered lines carry the meeting. The other three fields are logistics.
- Booking dayThe SDR writes it
- The buyer's words copied exactly
- Before the meetingA ten-minute call
- The AE asks one question per line
- First meetingThe AE opens from lines 1 and 2
- Then asks about line 4
- AfterClose the loop
- Confirmed, changed or dead, and why
The test for each line
| Line | Test | Fails when |
|---|---|---|
| 1. Replied to | Could the AE say it to the buyer as the opening question? | It names your product ("interested in our platform") or a category ("efficiency") |
| 2. Their words | Is it in quotes, and did the buyer say it? | It is the SDR's paraphrase, or "seemed keen" |
| 3. Also in the account | Does each name come with a reason? | It is a list of titles from a data tool |
| 4. Unproven | Would the AE learn something from it? | It says "none" or repeats line 1 |
| Touch | Can the AE find the message the buyer replied to? | "Sequence" with no step |
| Research links | Do they back up line 1? | Links to the company homepage only |
If line 1 or line 2 fails, the handoff stays with the SDR until it is fixed.
How to use it
- Write it the same day the meeting is booked. The buyer's words are freshest in the reply thread. Copy them exactly.
- Write line 1 in your prospecting method's terms. On Gap Prospecting, it is the problem the buyer had not yet seen as a problem. On Vortex Prospecting, it is the value hypothesis the meeting will validate or kill. The AE's first stage starts from that line.
- Fill line 3 from your account research. If you used our account research template, the names and reasons are already there. Vortex Prospecting teams aim to find the economic, user and technical buyer from the first wave, so line 3 should show which of the three you have.
- Be honest on line 4. The AE plans discovery around it. A note with nothing unproven means the SDR asked too much by email or is guessing.
- Walk it through on a ten-minute call. The SDR reads the four lines; the AE asks one question about each. Typing it into a channel is the fallback for when the two cannot meet.
- The AE builds the opening from lines 1 and 2. Quote the buyer back, check it still holds, then ask about line 4.
- Close the loop after the meeting. The AE adds one line to the note: confirmed, changed or dead, and why. The SDR reads it before next week's targeting.
Filled-in example
Illustrative. A dispatch software company, a fictional freight buyer.
SDR TO AE HANDOFF
Account: Marlby Freight
Buyer: Sam Ortiz, Head of Dispatch
Meeting: Thu 2:00pm, 20 min Booked by: Maya AE: Jordan
1. Replied to: Night shift handovers break as Marlby adds depots.
2. Their words: "Yes. Nights are a mess when someone calls in sick."
3. Also in the account: Lee Park, Ops Director, posted that he is running
the new Reno depot rollout in March. He will feel
any handover problem at the new site first.
4. Unproven: Whether Sam owns the budget. How often a sick call
breaks a shift. Whether the Reno rollout has a
staffing plan already.
Touch that earned the reply: Email 1 (subject "Night handover")
Research links: three night dispatcher job posts in October; Lee's
depot post
Jordan's opening, built from lines 1, 2 and 4: "When you replied to Maya, you said nights are a mess when someone calls in sick. Is that still the main thing? How often did it happen last month?" Then, when Sam describes the cost: "Who else feels it when a shift breaks?" Sam names Lee, and the deal has a second thread in its first meeting.
The email behind this meeting ran under 100 words and asked for no meeting at first touch, which is our house standard. To check your team's first emails against that standard, talk to us.
When the note fails the test
The AE should send it back the same day, with the line that failed and the question to answer. "Line 2 is a paraphrase. What did Sam write in the reply?" takes the SDR five minutes to fix while the thread is fresh. Leaving it until the meeting means the AE opens with a guess.
If the meeting is too close to wait, the AE opens with a question: "What made you reply to Maya's note?" The buyer then supplies line 1 and line 2 in their own words, and the AE adds them to the note afterward.
Track the pattern. If the same line fails for the same SDR two weeks running, it goes into that SDR's next one-on-one with a real note as the example. If it fails across the team, the problem is usually the targeting or the first email, and the SDR manager fixes it there.
Three ways teams misuse it
Turning it into a form with required fields and no tests. Required fields get filled. "Replied to: interest in solution" passes a CRM validation rule and fails the table above. Keep the test table next to the template and have the SDR manager read a sample of notes each week.
Using it for every meeting regardless of how it was booked. An inbound demo request and a cold reply need different notes. For inbound, line 1 is what the buyer asked for and line 4 is usually larger. Keep the four lines and change what the SDR writes on them.
Writing it and never closing the loop. The note's value to the SDR comes from the AE's one-line outcome. Without it, the SDR never learns which problems hold up in a meeting.
When a team books dozens of meetings a week, nobody reads every note. An AI sales expert can review each note with the SDR on a short call before it goes to the AE and check line 1 against the team's prospecting method: Keenan on Gap Prospecting, Val on Vortex Prospecting, Caty on your own playbook. The AE then preps the opening with their own coach from the note. If line 4 on your team's notes keeps saying "none", talk to us.
FAQ
What should an SDR to AE handoff note include?
The problem the buyer replied to, the buyer's own words in quotes, anyone else in the account and why they matter, and what is still unproven. Add logistics: meeting time, who booked it, which touch earned the reply and the research behind it. Four content lines are enough when each passes its test.
Where should the handoff note live?
Put it on the record the AE works in, usually the opportunity or the meeting in your CRM. Some CRMs log SDR-booked meetings to the lead or the SDR's activity, which leaves the AE without it. Check where your notes land before rollout and post a copy in the team's handoff channel if needed.
How long should a handoff note be?
Short enough for the AE to read in two minutes before the meeting, usually 60 to 120 words. Whatever the length, check it against the tests. A short note with the buyer's real words passes them; a long one with a field for everything and nothing specific in any of them fails.
Should the handoff template be the same for inbound and outbound meetings?
Keep the same four lines and change what goes in them. For outbound, line 1 is the problem the outreach named. For inbound, it is what the buyer asked for and why now. The unproven line is usually longer for inbound, because the buyer chose the topic.