Sales guides

How to prepare for a B2B discovery call

A practical discovery call checklist: clarify the buyer's problem, separate facts from assumptions, choose useful questions, and agree on a next step.

Good discovery preparation gives you something useful to draw on when the buyer asks a question or challenges an assumption. Prepare enough context to listen and respond, while leaving room for the buyer to correct you. A focused brief is easier to use during a live conversation than a script that tries to predict every answer.

Write the purpose in one sentence

Choose what you need to understand by the end of the conversation. 'Learn how the team handles handoffs and who owns improving them' is a usable goal. 'Show every feature' says little about whether the buyer has a problem you can solve.

Record why the conversation is happening now: a request from the buyer, a process change, or a specific issue they mentioned. If you do not know the reason, make that an opening question. Keep the source beside each fact so an old assumption does not become the basis of your pitch.

Prepare a brief you can scan

Use a few short entries instead of copying every piece of research. Keep confirmed facts and open questions visibly separate. You want a reminder that helps you listen, not another screen demanding your attention.

In Sales Copilot, the Prospect brief and relevant Library materials supply context for suggested answers during the live call. Attach those materials to preparation and choose the Playbook that fits the conversation. Check that the materials are ready to use before the session; a file that has not finished processing should not be treated as available evidence.

  • Buyer role and the reason for this conversation.
  • Their current process, using their own language where possible.
  • The problem they have confirmed and its known impact.
  • Assumptions you need to test, including ownership and urgency.
  • The product material relevant to this problem.
  • The outcome that would make the call useful to both sides.

Build questions around a concrete example

Start with how the work happens today. Asking for a recent example often gives you a clearer picture than asking whether the buyer has a broad category of pain. Follow the sequence: what triggered the work, what happened next, where it slowed down, and who was affected.

Explore impact without supplying numbers for the buyer. If they cannot quantify a cost yet, ask how they would measure it. A discovery call can end with an agreed way to investigate impact; it does not need a manufactured return-on-investment claim.

Understand the decision without interrogating

Ask how the organization evaluates a change like this, who needs to contribute, and what evidence would make the decision easier. A contact can understand the problem deeply without owning the purchase. Treat those as separate questions.

If timing is unclear, explore the event behind it. 'What happens if the process stays the same this quarter?' is more informative than pressing for an arbitrary deadline. When the buyer has no reason to act, record that honestly.

Close with a shared next step

Summarize the problem in the buyer's words and invite a correction. Identify what remains unknown. Suggest a next conversation only when you can explain what it will resolve and who should attend.

After the call, check your notes against the transcript. Update the Prospect with confirmed facts, then review the Debrief and Account Action Plan. Carry one unanswered question into the next preparation so you and the copilot have relevant context when that topic comes up again.

  • What did the buyer confirm or correct?
  • What information is still missing?
  • Who owns the agreed next step?
  • When will it happen, and what should each side bring?