Worked planning example
B2B account research and sales handoff example
An account-research handoff should give the next person the account rationale, the evidence behind it, the unanswered questions, the prospect's response and an agreed next step. Keep a booked meeting separate from a held or qualified conversation.
This entire example is fictional. The company, source notes, reply and timeline are training material, not a Beespoke client case, a real campaign or evidence of results.
Start with a narrow account hypothesis
In this fictional scenario, a software seller is assessing whether multi-location service businesses might need a shared scheduling process. That is a hypothesis to test, not a claim that any real business has this problem.
- Account
- Fictional Company A
- Inclusion criterion
- The scenario describes two operating locations.
- Exclusions to check
- Existing customer, active sales conversation, or a requirement outside the seller's supported scope.
- Unknown
- Current scheduling process, business impact, decision authority and timing.
Separate source notes from interpretation
S1 and S2 below are invented scenario notes, not live sources. Real research must replace them with an accessible source, a check date and the exact fact observed. Leave missing information unknown.
| Scenario note | Hypothesis | Question to verify |
|---|---|---|
| S1 says there are two locations. | Coordination across locations may matter. | Are schedules managed together or separately? |
| S2 lists an operations role. | This role may understand the workflow. | Who owns the process and who approves a change? |
| No note establishes a current operational problem. | Need and urgency remain unknown. | Is there a problem worth investigating at all? |
Review the proposed message against the evidence
Exclude an unsupported assertion such as ‘your team is losing time because scheduling is fragmented.’ Neither fictional source establishes that claim. A suitable research question would ask how the locations coordinate their schedules.
Before real outreach, check that the underlying observation is current and that the message describes only what the evidence supports. A plausible interpretation does not become a fact because it appears in a draft.
Write the handoff so the next owner can act
The fictional operations contact asks for a short overview. That response establishes a request for information; it does not establish purchase authority, a confirmed problem or an accepted opportunity.
- Response summary
- Asked for a short overview of the proposed scheduling approach.
- Evidence to include
- The scenario's S1 and S2 notes, clearly separated from the unverified problem hypothesis.
- Open questions
- Current process, impact, stakeholders and whether a further conversation would be useful.
- Next owner and action
- The seller's assigned sales reviewer prepares the overview and confirms the appropriate next step.
- Record state
- Keep the response, original booking date, current meeting date and qualification outcome in separate fields.
Count the original booking once
The fictional timeline continues with one booking and one reschedule. These are events for the same example record, not two new leads.
| Scenario day | Event | New first booking |
|---|---|---|
| Day 1 | The contact asks for an overview. | No |
| Day 3 | A meeting is booked for this example record. | Yes — one |
| Day 4 | The same meeting is rescheduled. | No |
This scenario contains one first booking. There is no record that the meeting was held, that the account qualified, or that sales accepted an opportunity. Those outcomes stay unknown. Do not use the reschedule date as the first booking date or turn a calendar entry into proof of attendance.
Use the example with your own evidence
Start with a blank worksheet. Replace every invented note with authorized current research, record what is missing and assign an owner to the next action. A planning score helps organize a decision; it is not a validated prediction of results.