Your researcher has selected an account. Now a colleague needs to take over the conversation without inventing a promise, repeating an approach or quoting work the producer cannot deliver. That is a handoff problem.
The document that solves it is smaller than the research file. It tells the next person what to do, what they can say, which commitments are still open and what should happen after an answer. Keep the underlying research linked rather than copying it into another essay.
This article starts after the account-fit assessment. Use the company-fit guide for that earlier work and the ownership guide if the relevant function is still unclear. Here, the output is a conversation and proposal handoff that another colleague can use.
Give the next action one owner
A handoff is incomplete if two people think the other is replying. Name the owner of the next action, the person who can answer a production question and the place where the conversation will be recorded.
Include the channel and current contact status. An accepted connection is different from a reply; a request for an example is different from a request for a quote. Record what actually happened. If no one has been contacted, say so.
Use one account card as the shared record. Before taking over, the colleague checks its current history, any opt-out and whether someone else has an active approach. A copied document is a snapshot, so it should point back to the record that can change.
Hand over a scope boundary, not a package promise
The colleague needs a short description of the work you could deliver. Include the main asset, intended use and practical limits. Mark each item as proposed, confirmed or unresolved.
For example, a written customer story and a short sales summary can be a proposed scope. Customer availability, approval timing, evidence and distribution rights still need confirmation. Those dependencies belong beside the scope, not in a footnote that appears after the price.
A producer should be able to spot an accidental commitment. If filming, extra languages or unlimited revisions have not been priced and agreed, they should not slip into an enthusiastic email. Link the discovery-call questions when the colleague needs the fuller scoping conversation.
A completed handoff card
Fictional exercise: FieldHarbor is an invented maintenance-software company. This card illustrates an agency’s internal planning. It is not a real account, conversation, commission or customer result. The upstream account-fit exercise is assumed complete; it is not repeated here.
| Handoff field | Completed planning card: FH-07 |
|---|---|
| Snapshot and working record | 21 October 2026; shared account card FH-07 is the record to check before acting. |
| From → to | Research lead → account lead. Producer answers delivery and estimate questions. |
| Immediate task | Ask whether a written implementation story is relevant to the sales team’s current work. |
| Contact and channel | One customer-marketing contact selected in the fictional account record; LinkedIn is the proposed channel. Identity and current history must be checked before sending. |
| Current status | Research complete; no invitation, message or reply recorded in this exercise. |
| Proposed deliverables | One written customer story plus a shorter sales summary, in English. |
| Outside this proposed scope | Filming, travel, translation, website implementation and additional versions. |
| Still to confirm | Customer participation, intended use, evidence, reviewers and an achievable schedule. |
| Price and date commitments | No quote or delivery date offered. Producer estimate follows scope confirmation. |
| Next owner | Account lead owns the initial question and any reply. Producer joins only for a relevant scoping discussion. |
| Stop or hand back | Decline or opt-out: close the approach. Wrong owner: record the referral before another contact. Unsupported deliverable: return to the producer. |
The card is complete because it makes the next decision executable. It does not pretend that unresolved details are settled. A real card would link the actual account research and conversation rather than the fictional record above.
Include the exact opening you want the colleague to use
A brief that says “send something personal” leaves the most important part unfinished. Draft the actual opening and let the colleague correct it against the current conversation.
For the fictional exercise, a natural one-paragraph draft is:
Hi [name], I write customer stories for B2B software teams. Would a written account of a maintenance team’s implementation be useful for your sales team at the moment, or is the priority a different format?
This is an unsent writing example, not a customer quotation or a proven message. Replace the placeholders with truthful sender and recipient details. If the person has already asked a question, answer that question instead of sending a new introduction. If you promised an example earlier, send an actual permitted example with the relevant context.
Keep the requested decision small. The opening is asking whether the proposed format is relevant. It is not asking the contact to accept a full production package before the practical questions have been discussed.
Leave a decision record for the colleague after you
The next person should be able to see why an account moved forward or stopped. Record the answer, its date, the decision and the next owner separately. Do not replace the answer with a label such as “hot lead.”
For FH-07, the initial planning decision is one format-relevance question, with no priced proposal yet. Now extend the fictional exercise with a hypothetical answer: the company already has an internal writer, but interview preparation is unresolved. No actual response or customer need is claimed; this invented input tests whether the handoff changes appropriately.
| Decision record | Completed exercise update |
|---|---|
| Before the hypothetical answer | Written story and sales summary were the proposed scope. |
| What changed | Writing is covered internally; the original package would duplicate that work. |
| Decision | Withdraw the written-package angle. Clarify whether a bounded interview-preparation stage would help before involving the producer in an estimate. |
| Next owner and commitment | Account lead acknowledges the change. Producer assesses preparation only if that task is confirmed. No price, interview booking or production date is promised. |
A corresponding reply draft is: “Thanks for clarifying. I’ll leave the writing package aside. Would an interview brief and preparation session help your internal writer, or is that work already covered too?” This is an unsent exercise draft. It responds to the changed scope without turning a hypothetical answer into an approved order.
Make the proposal match the handoff
When the conversation supports a proposal, carry across the agreed deliverables, exclusions, review process and dependencies. Check that the producer’s estimate refers to the same scope the account lead discussed. Explain any change before asking for agreement.
If finding the appropriate function is still the unresolved task, a small LinkedIn profile sample may help. The Leadsforlinked team also produces this site; its profile CSV can support selected-profile research, but it cannot confirm commissioning authority or supply verified email addresses. Do not collect more contacts simply because a handoff is unclear. Finish the decision record first.