> ## Documentation Index
> Fetch the complete documentation index at: https://b2-b-playbook.mintlify.site/llms.txt
> Use this file to discover all available pages before exploring further.

# SDR handoff

**Published:** 2026-09-12 · **Last reviewed:** 2026-09-12 · **Reading edit:** 2026-09-12

The meeting starts, and the buyer has to repeat everything they already told your colleague. A better handoff brings that context into the room: why the buyer agreed to talk, what you promised, and what you still need to learn. This is the work behind transferring a prospecting conversation to sales.

## Agree the acceptance standard

Define with the receiving team what makes a handoff useful. Keep the requirement proportional to the conversation: an initial inquiry may not reveal budget or procurement authority yet. Missing information should be visible rather than invented to satisfy required fields.

## Transfer the conversation

1. **Confirm the buyer's expectation.** Record why they agreed to the next step and what they expect to learn. A request for documentation is not automatically a request for a discovery call.
2. **Summarize verified context.** Include the business problem, current approach, relevant roles, timing statements, and source of the conversation. Separate direct statements from the SDR's hypothesis.
3. **List commitments and open questions.** Include promised materials, technical answers, commercial caveats, and any timing constraints. Make these visible before the meeting.
4. **Assign one accountable receiver.** Check territory, availability, language, and specialization. Provide a fallback if the intended owner cannot accept in the agreed window.
5. **Close the acceptance loop.** The receiver accepts, requests clarification, or returns the handoff with a specific reason. The sender remains responsible until ownership is explicit.
6. **Feed back the outcome.** Record whether the meeting occurred, what was learned, and the next buyer-agreed step. Review rejected handoffs for qualification or routing problems, not just individual blame.

## Worked example

A fictional prospect agrees to discuss migrating two reporting workflows. The SDR knows the operations lead owns the process but has not identified the budget approver. The handoff says exactly that and includes the promised connector compatibility answer.

The account executive accepts and starts by confirming the migration goal, rather than asking the buyer to repeat every detail. After discovery, finance is added to the buying group. The original handoff was useful without pretending that every stakeholder had already been mapped.

## Handoff record

| Field                                   | Notes |
| --------------------------------------- | ----- |
| Buyer-agreed purpose and next step      |       |
| Confirmed problem/current approach      |       |
| People involved and roles still unknown |       |
| Commitments and unanswered questions    |       |
| Receiving owner and acceptance deadline |       |
| Acceptance/outcome feedback             |       |

## Inspect the system

Track acceptance, time to ownership, attendance, and progression with consistent denominators. A rejected handoff can be appropriate if the wrong team received it. Investigate patterns: repeated missing context needs coaching; repeated territory rejection needs a routing fix. Never inflate opportunity creation simply to reward meeting volume.

## Try it with your own work

Review the last meeting passed from prospecting to sales. Could the receiver find the buyer’s question and your promises before the call? Add whichever piece was missing.

## Sources and scope

* [Salesforce: sales pipeline](https://www.salesforce.com/sales/pipeline/?ref=b2b-playbook) provides a general progression reference. The acceptance contract and example here are original operating guidance.

The example is fictional; any numbers illustrate the method rather than a benchmark. Adapt the worksheet to your own situation.

## What to read next

[SDR onboarding](https://b2-b-playbook.mintlify.app/playbooks/05-outbound-and-prospecting/sdr-onboarding) · [Buying committee](https://b2-b-playbook.mintlify.app/playbooks/01-strategy-and-buyers/buying-committee) · [Pipeline model](https://b2-b-playbook.mintlify.app/playbooks/09-operations-pipeline-and-measurement/pipeline-model)

[Chapter guide](https://b2-b-playbook.mintlify.app/playbooks/05-outbound-and-prospecting) · [All playbooks](https://b2-b-playbook.mintlify.app/playbooks)

***

Copyright © 2026 Ivan Xu. All rights reserved. See the [copyright and reuse terms](https://b2-b-playbook.mintlify.app/copyright).

Canonical source: [github.com/weilun88313/B2B-Playbook](https://github.com/weilun88313/B2B-Playbook)