Outbound resource

B2B discovery call agenda template

A discovery call should leave both sides clearer about the problem and whether another conversation is useful. Use this agenda to run an already-booked B2B conversation, capture what the buyer actually says and decide what needs checking. Adapt the timing to the participant; this is a working outline, not a script to race through.

Editorial update:

Copy the agenda, notes and recap

Original editable planning templates. The timings are illustrative, not a proven conversion formula. Replace brackets, remove irrelevant questions and confirm the prospect's preferred next step.

  1. 1. Shareable meeting agenda

    Topic: [agreed reason for meeting] Date, time and time zone: [details] Participants and roles: [names and responsibilities] By the end, we hope to clarify: [one practical question] Suggested discussion: - Check today's priority and adjust the agenda together - Walk through a recent example of [workflow] - Understand what needs to change and how you would recognize improvement - Check requirements and who needs to help evaluate them - Decide on a next action, or agree that no further meeting is needed Anything you would like to add or change?

  2. 2. Discovery notes worksheet

    Account and meeting reference: [ID] Participant's role in the workflow: [confirmed responsibility] Reason for meeting, in their words: [quote or faithful summary] Recent example: [steps, tools, people] Observed problem: [what was stated, by whom] Business consequence: [evidence, or unknown] Desired change and success measure: [definition, baseline if known] Constraints: [required capabilities, timing, resources] Other evaluation participants: [roles confirmed, or unknown] Our assumption to test: [clearly labeled hypothesis] Open question: [question, owner, agreed date] Decision: [continue / resolve unknowns / close] Agreed action: [deliverable, owner, date] No next step agreed: [record explicitly if applicable]

  3. 3. Post-call recap email

    Subject: Notes and next step from our [topic] conversation Hi [First name], My understanding is that you want to [stated objective], and the current issue is [confirmed workflow problem]. Please correct anything I have misunderstood. We still need to check [open question]. As agreed, [owner] will [specific action] by [date]. The purpose is to establish [decision it will support]. [Include a further meeting only if it was agreed; otherwise state the agreed closure or follow-up arrangement.] [Sender name]

Illustrative agenda
30 min
Copyable worksheets
3
Use immediately
No gate

A flexible 30-minute discovery call agenda

Scroll the table sideways to compare all columns.

A flexible 30-minute discovery call agenda
TimePurposeUseful output
0-3 minutesConfirm the reason for meeting and invite changes to the agendaA shared question to answer today
3-10 minutesWalk through one recent example of the current workflowSteps, people, tools and the point of friction
10-17 minutesExplore the consequence and desired changeThe buyer's priority and an observable success condition
17-24 minutesCheck constraints, participants and evaluation processKnown requirements plus questions for the right owner
24-30 minutesSummarize, correct misunderstandings and agree whether to continueAn action with owner and date, or a clear close

Prepare from the handoff, then test assumptions

Read the booking notes and previous replies so the buyer does not need to repeat their entire story. Separate facts from research hypotheses. A job title can suggest who to ask, but it does not establish budget authority or a problem. Bring one relevant workflow question and identify any capability you must verify before proposing a solution.

Follow one concrete example

Ask the participant to describe the last time the workflow became difficult. Who handled it, which tool or document was involved, and what happened next? Then ask what a better outcome would look like. If they cannot quantify the consequence, leave the number unknown. Do not manufacture a return-on-investment estimate from a vague complaint.

Use questions to understand, not to complete a scorecard

Possible prompts include: Where does this work move between teams? Which requirement would rule out a new approach? Who would check whether a change works? What would need to happen before evaluating it? Select the question that follows the answer you just heard. Ask about purchasing resources and timing when relevant, explain why, and allow the participant to say they do not know.

Give a direct answer before redirecting

If the buyer asks about price, a required integration or delivery scope, answer from approved facts. If you cannot answer, name who can verify it and agree when to respond. Do not make them complete the whole agenda before acknowledging a potentially disqualifying requirement. A short relevant demonstration can help clarify a question; avoid turning discovery into an unrelated feature tour.

Worked example: dispatch software discovery

Fictional example, not a customer result: a dispatch manager says each branch copies exceptions into a spreadsheet at the end of a shift. The seller asks for one recent exception and learns that finance needs the same information the next morning. The desired change is a shared exception record, but the required export format is unknown. Instead of promising integration or estimating savings, they agree that the manager will obtain a blank export specification and the seller's technical owner will review it by an agreed date. A tailored demo is considered only after that compatibility check.

Continue, investigate or close

Continue when both parties identify a relevant problem and agree a useful next action. Investigate when a material requirement is unknown: assign a question to the person able to answer it. Close when the requirement is unsupported, the buyer sees no relevant need or asks to stop. Keep attendance, qualification and opportunity stage separate in your records. A completed discovery conversation is not automatically a qualified opportunity.

Adapt when only 15 minutes are available

Agree the single most important question, explore one example, check the key constraint and reserve time to summarize. Defer secondary topics explicitly. For a complex buying group, use separate conversations with the appropriate stakeholders rather than asking one person to invent everyone else's requirements. The 30-minute outline above is a planning choice, not a required duration.

Who this helps

  • Account executives receiving outbound-booked meetings
  • Founders running early B2B sales conversations
  • SDRs preparing a useful discovery handoff

Work through the process

  1. 01

    Prepare

    Review the handoff and mark the assumptions you need to test.

  2. 02

    Explore

    Use a recent workflow example to understand the actual need.

  3. 03

    Verify

    Check hard constraints and assign unanswered questions.

  4. 04

    Agree

    Confirm a useful action or close; record the buyer's decision accurately.

Questions and answers

Is this the same as an appointment qualification checklist?
No. The qualification checklist defines evidence needed to accept an SDR handoff. This agenda helps run the conversation itself. Use the existing handoff notes as input rather than repeating every question.
Should every discovery call last 30 minutes?
No. Thirty minutes is the example used here. Agree the duration and priority with the participant, and split complex discovery across the people who can answer the relevant questions.
What if the buyer does not know their budget?
Record it as unknown and clarify the process for evaluating the purchase if relevant. Apply your team's documented qualification rules; do not guess a figure or imply funding is approved.
Does a next meeting mean the opportunity is qualified?
No. Record what was actually agreed and apply the receiving sales owner's criteria separately. A technical check may still leave fit unresolved.

Sources and editorial notes

Original AI-assisted editorial templates and planning conventions prepared for LeadFlow. Examples are illustrative; they are not independently tested results, customer evidence or performance benchmarks. Check facts and adapt the material to your own workflow before use.

Keep reading