How to Prepare for a B2B Discovery Call

To prepare for a B2B discovery call, build a one-page brief that helps you decide what to learn before recommending a service. Start with the meeting invitation, available relationship notes and your relevant offer. Turn those inputs into a provisional purpose, prioritised questions, appropriate proof and conditional next steps.

Decide what this conversation needs to establish#

Write a learning objective before researching extensively. For example:

Establish whether client onboarding presents a problem worth investigating, and whether a scoped diagnostic would be useful.

This is provisional, not an agenda imposed on the buyer. At the start of the call, invite them to amend it: “Would that be useful, or is there something else you want to establish?”

Gather the minimum inputs:

• Why the meeting was arranged and what the buyer actually requested.
• Expected participants, their roles and your relationship history.
• The service that might be relevant, including where it would not fit.
• Evidence you can legitimately share.
• Your own limits on price, scope and commitments.

Do not convert willingness to meet into assumed urgency, need or buying authority. If the invitation says little, discovering the buyer’s purpose becomes your first priority.

Build your one-page discovery brief#

The brief should connect each consequential unknown to evidence you can seek during the conversation. It is not a compressed company dossier.

Separate facts, hypotheses and unknowns#

Record facts with a source and date. Keep the wording close to what the evidence establishes.

In the illustrative scenario used here, suppose a consultant’s event note says: “Prospect mentioned that client onboarding is taking longer.” That note establishes what the consultant recorded hearing. It does not establish that onboarding is failing, that the cause is a delivery bottleneck or that the buyer wants outside help.

Classify the context:

• Fact: The event note records a comment about longer onboarding.
• Hypothesis: Delays may be caused by handoffs between teams.
• Unknown: Whether the longer duration creates an unwanted consequence.

Public research is optional. Retain an item only if it changes a question, a proof choice or a possible commitment. A company announcement might suggest something worth asking about; it cannot confirm the buyer’s private priorities.

Choose the unknowns that could change your recommendation#

Prioritise gaps about the problem, its consequences, existing alternatives and ownership. Ask: What would I do differently depending on the answer?

Whether onboarding causes missed customer commitments could change whether further investigation is worthwhile. Whether the team already has an adequate remedy could change whether your service is relevant. Who owns the process could change who needs to join a follow-up.

If an answer would not affect your understanding or proposed action, give the question less call time. Leave routine background questions out when reliable information already answers them.

Write questions that allow your hypothesis to be wrong#

GOV.UK’s Using in-depth interviews guidance recommends starter and follow-up questions, open neutral wording, attention to real examples rather than generalities, and flexible use of a discussion guide. These are user-research practices adapted here to gathering buyer evidence—not proof that this sales preparation method improves conversion. (gov.uk)

Instead of asking, “How much are onboarding bottlenecks hurting revenue?”, try:

“You mentioned onboarding was taking longer. Could you walk me through a recent client’s onboarding, from agreement to being ready to use the service?”

Then follow the example: Where did time pass? What happened as a result? How was it handled?

Before the meeting, identify an answer that would weaken your hypothesis. Perhaps the additional time is deliberate, customers accept it and the team has no reason to change it. If that explanation holds and no unwanted consequence emerges, do not recommend a project to reduce onboarding time. If a material unresolved problem emerges, discuss whether a bounded diagnostic would be useful.

Copy this brief into an ordinary document#

The working method proposed here connects unknown → evidence sought → question → interpretation change → next commitment. Each priority question should have a reason to be asked and an answer that could change your direction.

Keep entries to a phrase or sentence. Repeat the priority-question block only for the few unknowns you can realistically explore in the allotted time.

B2B DISCOVERY BRIEF

Meeting: [Buyer organisation, attendees, date, duration]
Provisional purpose: [What should this conversation establish?]
Buyer context: [Why we are meeting; roles; relevant prior contact]
Relevant offer: [Potentially useful service and where it would not fit]
Known facts: [What the evidence establishes; source and date]
Hypotheses: [Possible explanations, not established diagnoses]

PRIORITY QUESTION — repeat as needed

Unknown: [What could change my recommendation?]
Evidence sought: [A recent example, consequences or other relevant detail]
Starter question: [Open, neutral wording]
Possible follow-ups: [Details needed to understand the answer]
Interpretation change: [An answer that would weaken my hypothesis]
Conditional next commitment: [If X, consider Y; otherwise, do Z]

Relevant proof: [Item → concern it addresses → scope and limitations]
Authority to clarify: [Issue owner; buyer approver; my approval needs]
Commitment limits: [Price, scope or promises I cannot authorise]
Next-step options: [Specific information / owner conversation /
diagnostic discussion / no project]

Keep relevant proof and next-step options ready#

Complete the final fields before the call, but do not turn them into a presentation sequence.

Match each proof item to a concern it can address. A scoped case might show how a comparable problem was approached. An explanation of your method might clarify what a diagnostic would involve. A targeted demonstration might answer a specific operational question.

Record limitations alongside the item: different circumstances, narrower scope or an outcome you cannot substantiate. If you lack relevant evidence, prepare to say so. An unrelated success story does not answer the buyer’s concern.

Prepare more than one possible ending:

• A bounded diagnostic discussion if the problem appears relevant and remains unresolved.
• A conversation with the process owner if essential context is missing.
• An exchange of specific information if the evidence is incomplete.
• No project if the existing approach is adequate or your offer does not fit.

Participation and approval are separate questions. Establish who can authorise expenditure and scope, and what you can commit to yourself. Do not make “send a proposal” the automatic conclusion; make it conditional on enough understanding to propose something useful.

Use the brief as a guide, not a script#

Sparse context calls for explicit unknowns, not invented certainty. A buyer with a defined requirement needs targeted questions and proof, not an extended exploration they did not request. Unexpected answers should change your direction.

Confirm attendees, meeting length, joining details and access to your prepared materials. Leave room to record corrections during the conversation, then update the brief with what the buyer actually established.

For your next scheduled discovery call, complete the one-page brief starting with the unknown most likely to change your recommendation.

Dainin CEOS connects business understanding, judgement, decision authority and execution. In discovery, its role is to preserve context, show what informed recommendations, route consequential actions through appropriate authority and retain learning—not remove human judgement.

Within an appropriate Dainin configuration, Lead Analysis, Meeting Planner and Sales Performance can help connect relevant evidence with subsequent work. The preparation discipline still matters: distinguish what is known, assumed and undecided.

For your next prospect meeting, prepare the one-page brief and decision questions. After the call, record confirmed evidence and the agreed next commitment, then decide whether to continue, change direction or stop.