What should an SDR-to-AE handoff include?
An SDR-to-AE handoff should include account fit, the prospect’s stated problem, relevant context, the agreed purpose of the meeting, open questions, and a named owner for the next step. The account executive should not need to rebuild the conversation before speaking with the prospect.
A booked meeting is a calendar event. An accepted sales handoff is a defined transfer of responsibility. Keeping those concepts separate helps a manager diagnose whether the problem is prospecting, qualification, documentation, attendance, or closing.
This article focuses on that transfer. For sourcing, compensation, and the broader hiring process, use the existing LATAM SDR hiring guide. You do not need another general SDR hiring checklist to fix an unclear handoff.
What qualifies a meeting for your sales team?
Define the minimum evidence an SDR needs before booking or transferring a meeting. Build the standard around your sales motion, not an impressive-sounding qualification acronym. A founder-led services company may need different information from a team selling complex enterprise software.
| Area | Minimum information | How to record uncertainty |
|---|---|---|
| Account fit | Relevant company characteristics and use case | Unknown size or fit criteria are marked unconfirmed |
| Contact context | Role, involvement, and reason for engaging | Do not label a person the decision-maker without evidence |
| Problem or objective | What the prospect said they want to address | Separate direct statements from the SDR’s interpretation |
| Meeting purpose | What both parties expect to discuss | Record any mismatch before confirmation |
| Timing and next step | Agreed meeting and relevant urgency | Avoid inventing a buying deadline |
| Exclusions | Known disqualifiers or routing conditions | Route unclear cases to the designated reviewer |
Not every first conversation will establish budget, authority, and timing. Decide which unknowns are acceptable at this stage. The SDR should make missing information visible, while the AE continues discovery instead of treating the notes as a complete sales diagnosis.
What should the CRM handoff note look like?
Use one structured note that is short enough to maintain. Link to approved source records when useful, and follow your company’s policies for recording and retaining prospect information.
| Field | Example using a fictional prospect |
|---|---|
| Account and contact | Acme Services; Jordan Lee, operations lead |
| Why the account fits | Service company with an existing support team; target market fit confirmed |
| Prospect-stated need | “Our managers are still handling routine support follow-up.” |
| Current approach | Internal shared queue; no dedicated owner for unresolved requests |
| Meeting objective | Explore whether dedicated support capacity would fit the workflow |
| People involved | Jordan is gathering options; final approver is not yet confirmed |
| Timing | Wants an initial discussion this month; start date unconfirmed |
| Open questions | Volume, systems, budget, manager, and required coverage |
| Commitments and owner | AE owns discovery; SDR sends confirmation and updates the record |
The value comes from reliable distinctions: confirmed versus assumed, current process versus desired outcome, and booked meeting versus purchase intent. Do not fill every blank with an optimistic guess to make the opportunity look stronger.
Who owns the prospect before and after the meeting?
Name one accountable owner at each stage and decide what happens during absences. Shared responsibility often becomes a gap when both people assume the other sent the reminder or followed up.
| Stage | Accountable owner | Required action |
|---|---|---|
| Before booking | SDR | Confirm minimum fit and meeting purpose |
| Booked, not yet accepted | SDR | Complete notes and request AE review |
| Accepted and upcoming | AE, with agreed SDR support | Review context and confirm preparation |
| Reschedule or no-show | Named owner from your policy | Contact prospect and update next step |
| Meeting completed | AE | Record outcome and assign follow-up |
| Rejected or rerouted handoff | Sales manager or designated reviewer | Resolve reason and return clear instructions |
Set a realistic review window based on working hours. A late-night booking should not create an implied immediate-response requirement. For teams across countries, confirm the coverage schedule and account for relevant clock changes.
How should the AE reject or correct a handoff?
Require a reason that helps the SDR improve the next conversation. “Bad lead” does not distinguish poor fit from a no-show, missing notes, an existing customer, or an AE who has no capacity.
- Outside the agreed customer profile.
- Wrong route, duplicate, or an existing active opportunity.
- Missing required evidence for this stage.
- Meeting purpose was misrepresented or unclear.
- Contact has no relevant involvement for this sales motion.
- Operational problem, such as scheduling or ownership.
Use rejection as a process signal, not a competition between prospecting and closing. Review a sample of accepted and rejected meetings together. If two AEs apply different standards, fix the definition before holding the SDR to either interpretation.
Track attendance separately from qualification. A qualified contact can miss a meeting, and an unqualified contact can attend. Combining them hides the actual problem.
Which handoff metrics are useful?
Use consistent cohorts and definitions. If you review meetings booked in a particular week, allow enough time for those meetings to occur before calculating attendance. Do not mix accepted opportunities from older leads into the same denominator.
| Measure | Calculation | Result |
|---|---|---|
| AE acceptance | 16 accepted ÷ 20 submitted | 80% |
| Attendance after acceptance | 12 held ÷ 16 accepted scheduled meetings | 75% |
| Progression after a held meeting | 5 progressed ÷ 12 held | 41.7% |
These invented numbers demonstrate the calculations, not performance benchmarks. Read the reasons behind each stage: incomplete notes, wrong fit, scheduling failures, discovery outcomes, and sales capacity. Avoid evaluating an SDR solely on revenue they do not control or on raw bookings that encourage weak qualification.
How do you introduce the checklist?
If the process is clear but execution capacity is missing, explore HireLATAM’s sales talent recruiting service. Bring the handoff requirements to the search so the candidate profile reflects how your SDRs, AEs, and sales support actually work together.
Related role-specific guides
Frequently asked questions
Is a booked meeting automatically a qualified opportunity?
No. A booked meeting meets a scheduling condition. Qualification and opportunity creation should follow your documented sales-stage definitions.
Should SDRs own the prospect until the deal closes?
Usually the team should define a transfer point and an accountable owner for each stage. Ongoing SDR support can be useful, but it should not obscure who owns discovery and follow-up.
What if an AE rejects most handoffs?
Review the reasons and a shared sample of cases. The cause may be list quality, qualification, incomplete context, inconsistent standards, or sales capacity rather than one person’s effort.
Should every company use the same handoff fields?
No. Keep the minimum information that helps your closer run the next conversation. Change the template for your product, customer profile, deal complexity, and sales process.
Add sales capacity with a clear handoff from the start.
Tell us about the responsibilities, tools, experience, and schedule. Let’s explore the right match for your business.