Let us say you are an SDR and you have just spent three weeks getting a meeting with the operations head of a packaging company in Rajkot. You got the slot. You feel good. Now think about what happens next: an account executive, who has never spoken to this person, opens the calendar invite at 9:50 for a 10:00 call. What does that AE know?
If the answer is “a name and a company”, you have wasted most of your three weeks. The handoff is the moment where the work of prospecting turns into the work of selling, and it fails more often than any other step in the early funnel. Here is how to make yours good.
Start from what the AE needs in the first minute
Imagine the AE has two minutes. What do they most want to know? Roughly this: who exactly is attending and what is their role; why did they agree to the meeting; what problem did they mention, in their own words; what is already in place today; and is there any time pressure. Everything else is secondary.
That is why I would keep the note to a handful of lines. A wall of text will not be read. One sentence on the reason for the meeting, quoted as closely as you can remember. One on the current tool or process, if you learned it. One on what is driving the timing, such as a new plant, a contract renewal, a recent hire. One on who else is involved in the decision, if you know. And one line about anything awkward: the contact is sceptical, or was referred by someone, or asked specifically not to be sent brochures.
Be honest about what you do not know
This is the hardest bit. There is pressure to make a meeting sound promising, because meetings count and opportunities pay. Resist it. If the contact accepted mainly to get you off the phone, say so. If you do not know their budget, write “budget not discussed”. An AE who walks in expecting a hot lead and finds a polite stranger will lose confidence in your notes, and then in you.
Separate what the prospect said from what you inferred. “He said the dispatch team uses spreadsheets” is a fact. “They probably need a new system” is your guess, and it should be labelled as such.
Agree the definition of a good meeting beforehand
Handoffs go wrong most often because the two sides never agreed what “qualified” means. If the SDR is paid on meetings booked and the AE is paid on closed deals, the SDR will drift toward booking easier meetings with the wrong people. The fix is a written, shared minimum: the right kind of company, a person with a relevant role, a stated problem, and some reason to talk now. Meetings that do not meet it should not be passed on as qualified, and the AE should be able to push back on a poor one without it becoming a quarrel.
Many teams track not only how many meetings were booked but how many actually took place and how many became real opportunities. That last figure is what tells the SDR whether the handoff is working. If meetings are held but few progress, something about the qualification or the preparation is off.
What the AE owes back
The handoff is not one-way. After the meeting, the AE should tell the SDR what happened, even in a line or two. Did it go well? Was the contact the right person? Was the pitch relevant? Without that, the SDR is working blind and cannot improve. Some of the best SDR teams have a standing fifteen-minute review each week where AEs comment on the quality of meetings. It costs almost nothing.
Also decide who owns the follow-up in the first days. If the AE is travelling and the prospect replies to the SDR’s email, what happens? Silence at this stage is how interested people go cold. Settle it in advance: who responds, and within what time.
Where it lives
Put it in the CRM record, in fixed fields, not in a chat message that vanishes. If the AE has to hunt through Slack, the handoff has already failed. Fixed fields also make it possible to look back later and see which kinds of meetings turned into deals, which is very useful to learn from.
A last thought for the SDR. The AE’s success is yours too, so write the note you would want to receive. If you would not want to read it in two minutes before a call, rewrite it.
Figures and names in the examples are illustrative.
Leave a Reply