SDR and AE collaboration works when the handoff is a written contract, not a calendar invite: who calls which contacts, what a booked meeting must contain, and what the AE owes the SDR back after the first call. We run outbound on this at Sonik, and the checklist below is the one we would give any team where meetings get booked but opportunities do not get created.

Why most SDR to AE handoffs leak pipeline

In our experience the leak is rarely the SDR's call quality. It is the thirty seconds after the call.

Three gaps do the damage. The SDR heard a pain, a tool in place and a budget cycle, and wrote "interested, wants a demo" in the CRM. The AE opens the meeting with a deck and re-asks the questions the prospect already answered. And nobody tells the SDR what happened next, so the next ten calls are booked the same way.

When I was an AE at Google Cloud, the SDRs I closed the most with were not the ones who booked the most. They were the ones whose notes let me skip the first ten minutes of discovery. That is the whole game.

The 9-point SDR to AE handoff checklist

Every meeting passed to an AE should carry these nine items. If one is missing, the SDR has a follow-up call to make before the demo, not after.

1. The trigger. Why this account, why now: a job change, a hiring post, a website visit, a closed-lost deal from last year. Not "fits the ICP".
2. The pain in the prospect's words. One sentence, quoted, not paraphrased into your product's vocabulary.
3. What they use today. A tool, a process or nothing. The AE's demo depends on this.
4. Who else is involved. Names and titles mentioned on the call, even in passing. "I'd have to check with our RevOps lead" is a second contact.
5. The buying window. Renewal date, budget cycle, a project already funded or not.
6. What was promised. If the SDR said "fifteen minutes, no slides", the AE shows up with no slides.
7. Objections raised and how they were handled. The AE should not be surprised by "we tried something like this in 2024".
8. The call recording or AI summary link. Two minutes of listening beats any form field.
9. The next step the prospect agreed to. A calendar slot accepted, not "sent an invite".

Pull your last ten booked meetings and count how many items each one carries. In our experience most teams score three or four. The AE fills the gap live, and the prospect feels interrogated twice.

Split the account, not the calendar

The second cause of friction is two people calling the same company without a rule.

The rule we use: the SDR owns contacts below the decision line (team leads, managers, individual users), the AE owns the line and above (directors, VPs, founders). The SDR's calls collect context; the AE's calls use it. Our benchmark of 1,000,000 French B2B cold calls shows sales and leadership personas pick up above 15%, well over the 11.3% average, so the AE is not calling into a wall.

Then put a weekly 20-minute sync in the calendar with a fixed agenda: the five accounts the AE wants opened, the five the SDR is working, and one call recording reviewed together. Not a status meeting. A planning meeting.

Once a week, call together. A shared calling block where the AE dials the same list as the SDR, from the same room or the same virtual floor, does more for alignment than any process document. The SDR hears how the AE handles "send me an email", and the AE remembers how hard a cold open is.

Pay for the meeting that happens, not the one that is booked

Incentives decide what gets handed off.

If the SDR is paid on meetings booked, the AE receives meetings that were never going to show. If the SDR is paid only on opportunities created, the AE becomes a gatekeeper and the SDR stops trusting the AE's judgement. The split that works in our experience: a smaller amount on the meeting held, a larger amount on the opportunity the AE accepts within ten days, and the AE's acceptance criteria written down and shared.

Written criteria matter more in France and in most of Europe than in the US, because teams are smaller and one AE often works with one SDR. A dispute about one meeting is a dispute between two people who sit next to each other.

Three numbers that tell you if the handoff works

• Show rate. Meetings held divided by meetings booked. Below 70% means the SDR is booking before the prospect has a reason to show up.
• Acceptance rate. Meetings the AE turns into an opportunity within ten days. Below 50% means the qualification bar is unclear, or ignored.
• Feedback lag. How many days between the AE's first meeting and the SDR knowing the outcome. More than two means the SDR is learning nothing.

Review the three together every month. One number alone can be gamed; three cannot.

How Sonik approaches the SDR to AE handoff

Sonik records and transcribes every call made from the dialer, and the AI call summary is written in the structure above: trigger, pain in the prospect's words, current setup, other names mentioned, next step. The summary lands on the contact in the CRM, so the AE reads it before the meeting rather than asking the SDR on Slack.

The AE also sees the signal that started the sequence. When half of our own pipeline comes from signals that were already in the CRM, the AE needs to know whether this was a job change or a returning website visit; the first call is different.

And because the AE's calls run through the same dialer, the SDR sees the outcome of the first meeting in the same timeline. The feedback lag drops to zero without a meeting.

Conclusion

A good handoff is nine pieces of information, a rule about who calls whom, and a payout tied to the meeting that happens. This week, pull your last ten handoffs, score them against the checklist, and show the AE the result. Then fix the item that was missing most often, which in our experience is almost always item four: who else is involved.