Founder to SDR handoff brief that preserves buyer context
A concise handoff for moving early sales conversations from a founder to a sales development rep.
founder to SDR handoff brief
Early prospects often speak with a founder because the company is still learning how buyers describe the problem. When an SDR joins, a bare CRM transfer strips out the useful texture. The brief should preserve what the buyer said without turning the founder's interpretation into fact.
Open with the relationship: how the parties met, what has already been promised, and whether the contact expects the founder to remain involved. Then record the buyer's words about the problem, current workaround, urgency, participants, and desired next conversation. Quote only language captured in the record.
Page one: what the buyer actually said
A warm relationship is not the same as a qualified opportunity. Mark which facts are confirmed and which are assumptions. The SDR should know whether company fit, authority, timing, and practical need came from the buyer, from public research, or from the founder's working theory.
Include a clear reason for the handoff. The SDR may be gathering missing information, arranging a specialist call, or managing a defined follow up. Avoid the vague instruction to take it from here. It makes the new owner guess at both the goal and the founder's expectations.
Page two: promises and open questions
List every promised introduction, document, answer, and date. Then list what remains unknown. This pairing matters because the SDR must honor the first list without pretending the second has already been resolved. A founder's hunch can appear in the brief, but it must be labelled as a working assumption.
The transfer message
Use one shared message that names the SDR, explains their role, and restates the agreed next step. The founder should not disappear between two separate threads. A direct introduction gives the buyer a chance to correct context before the new owner begins asking questions.
The SDR confirms receipt in the system and notes any missing item. If the buyer replies only to the founder, route the response into the same record rather than creating a shadow conversation. The team needs one current history even when several people remain involved.
The first call after handoff
The SDR should begin with the agreed context and ask the buyer to correct it. Repeating every discovery question signals that the handoff was ceremonial. Skipping all questions is just as risky. The brief should show which answers are settled, which are stale, and which still need the buyer's words.
Thirty-day handoff audit
Review handoffs after the first month. Look for information the SDR repeatedly has to recover, promises that surprise the delivery team, and opportunities that stall immediately after the introduction. Those patterns should improve the brief, qualification questions, or ownership threshold.
Do not make the form longer by default. Remove fields nobody uses and keep the details that change the next action. A good handoff feels small because it carries the right context, not because it omits the uncomfortable uncertainty around the opportunity.
A compact brief template
Use six labels: relationship, buyer language, confirmed facts, assumptions, promises, and next action. Each label may hold a sentence or two. If a field needs a page, link the supporting record. The brief is the transfer cover sheet, not a replacement for the account history.
Sources
- Qualify and Route Leads to Your Reps, Salesforce Trailhead. Describes qualification inputs and the value of recording information that sales managers and reps can review.
Related GTM guides
Frequently asked questions
Should the founder stay on every call after the handoff?
Only when the buyer expects it or the conversation needs founder context. Name the founder's role in the brief so the SDR and buyer are not left guessing.
What belongs in the first handoff note?
Capture the relationship, buyer language, confirmed qualification facts, open assumptions, prior promises, and the exact next step with its owner.