Sales Discovery Call: Six-Stage Plan and QA Rubric

A discovery call fails when the CRM says “interested” but nobody can explain what the buyer is changing, why it matters, who is affected, or what evidence would justify another meeting. The remedy is not a longer script. It is a disciplined conversation in which every important conclusion can be traced to something the buyer said, showed, or agreed to verify.

This guide preserves a six-stage structure while making it adaptable. The stages are coverage areas, not a stopwatch. You can loop backward when an answer exposes a new branch, skip a branch the buyer says is irrelevant, or stop when fit is absent. Research on everyday conversations found that follow-up questions can signal responsiveness and increase liking, but it did not test B2B conversion. Treat that research as support for attentive follow-up—not as a promise of sales performance. The original study is available through Harvard Kennedy School.

Printable sales discovery call plan

Copy this block into a meeting note before the call. Fill what you know from reliable account research, label hypotheses clearly, and leave room for correction. Do not quietly promote a guess into a CRM fact.

Preparation should make questions more relevant, not make the conclusion inevitable. Review the account, prior interactions, inbound source, and public context. Then write one disprovable hypothesis: “We think manual handoffs may be delaying follow-up; we need the buyer to confirm the process and provide an example.” For a deeper preparation routine, use the discovery call checklist. For a larger question bank, keep the discovery questions guide nearby.

Question-to-evidence map

Stage 1: earn consent and set the time box

Open by checking context and permission. A usable opener is: “We have 30 minutes reserved. I would like to understand what prompted the conversation, how the process works today, and whether another step would be useful. I will save the final five minutes to summarize. What would you change about that agenda?” This makes the buyer a participant in the design of the call.

Confirm who is present, how much time they actually have, whether any topic is off limits, and whether the meeting is being recorded. Conversational permission is not a substitute for legal recording consent or company policy. If recording is proposed, follow the applicable policy and platform controls; do not assume attendance equals consent.

If the buyer has ten minutes rather than thirty, branch. Ask for the trigger, one concrete example, and the desired decision, then agree whether a longer session is warranted. If they expected a demo, acknowledge the mismatch: offer a short orientation and ask permission to schedule proper discovery, or mutually choose a few questions that make the remaining demo relevant. The observable pass condition is simple: the buyer accepted or edited the purpose, topics, and time box.

Stage 2: establish context and the trigger

Start with what changed, not a biography questionnaire. Ask, “What happened that made this conversation useful now?” Then follow the answer: “Who first noticed it?” “What have you already tried?” “What would happen if nothing changed?” A follow-up should connect visibly to the prior answer; otherwise the call feels like form completion.

Separate three types of information in your notes. A fact has an attributable source: “Operations changed the routing rule in June.” A buyer estimate is explicitly approximate: “The manager estimates reviews take two to four hours.” A rep hypothesis remains unverified: “Possible impact on response time.” This distinction prevents later teams from treating speculation as a committed business case.

If there is no trigger, do not manufacture one. The branch may be education, future monitoring, referral to another resource, or disqualification. If the request came from a colleague or campaign, ask whether the participant shares the original goal. A booked meeting proves only that a meeting was booked.

Stage 3: map the current state with evidence

Move from general labels to a recent example. “Walk me through the last opportunity where the handoff failed” is more useful than “Do you have handoff problems?” Record the sequence, actors, systems, handoffs, decision points, exceptions, and what “done” means. Ask the buyer to correct your summary: “I heard that the SDR logs the note, the AE recreates it, and operations checks missing fields on Friday. What did I miss?”

Use open questions for narrative and closed questions for confirmation. Closed questions are not inherently bad; they are poor substitutes for exploration. “Does Salesforce hold the approved record?” can confirm a system of record after the buyer has described the workflow. Avoid stacked questions such as “How does it work, who owns it, and what does it cost?” because the answer rarely covers all three.

High-quality listening research has tested how listening affects conversations during disagreement, including four experiments summarized in the PubMed research record. That is not a sales-outcome benchmark. Its relevant operational lesson is narrower: managers can coach visible listening behaviors such as accurate paraphrase, non-defensive follow-up, and correction. The pass condition for this stage is a current-state map that the buyer recognizes, plus a list of gaps still requiring evidence.

Stage 4: test impact and priority

Impact is not synonymous with revenue. It may be delay, rework, risk exposure, customer effort, missed learning, or management attention. Ask what changes downstream, who experiences it, how they notice it, and whether a baseline exists. If the buyer cannot quantify the effect, record “unmeasured” and agree how it could be measured. Never invent a dollar value to make the opportunity look qualified.

Use a traceable chain: observed condition → operational effect → affected measure → business relevance. For example: “Required fields are missing in sampled handoffs” → “operations returns records for correction” → “median time from meeting to accepted record” → “leaders want reliable follow-up before the next planning cycle.” Each arrow needs buyer confirmation or a verification owner.

Then test priority without coercion. Ask what else competes for the same people and budget, what deadline is external versus preferred, and what evidence could change the priority. A one-to-ten urgency score is ambiguous unless you define its anchors; “must act before the renewal because the current contract ends” is better evidence than “eight out of ten.” The SPICED framework guide can help teams organize situation, pain, impact, critical event, and decision evidence, but the label is never a substitute for the evidence itself.

Stage 5: map the decision and qualification

Qualification is a continuing evidence review, not a single question about budget or authority. Salesforce’s own qualification material describes qualification as ongoing discovery and validation rather than a one-time binary judgment. See the official Salesforce qualification guide. Your organization should still define its own required fields and exit criteria.

Ask how a comparable decision was made, who supplies input, who approves security or legal terms, which system owner controls integration, what evidence each participant needs, and what can stop the project. Do not infer power from seniority or assume the current participant can recruit others. Ask permission before naming absent stakeholders as blockers.

Branch according to the evidence. If fit is absent, say so and explain why. If the problem is real but not prioritized, document a buyer-chosen revisit condition. If fit is plausible but technical or regulatory claims require expertise, pause the answer and assign a qualified owner. Objective product claims should be supportable; the FTC’s business guidance says advertising claims must be truthful, nondeceptive, and evidence-based. That guidance is not a universal discovery-call script, and specialized products or jurisdictions may require additional review.

Stage 6: agree on an evidence-based next step

First summarize the evidence and invite correction: “You described the current routing process, two recent failures, and a review needed before renewal. We have not yet verified the baseline or security requirements. Is that accurate?” A corrected summary is more valuable than a polished pitch.

Then design the smallest next action that resolves uncertainty. A good next step names the question, artifact, participants, owner, date, and exit rule. Example: “By Tuesday, Maya will provide five de-identified handoff records. On Thursday, operations and the CRM owner will test whether the proposed workflow captures the required fields. We proceed to a scoped pilot only if all required fields write correctly and reviewers can trace changes.” A calendar invitation alone is not evidence of progress.

Possible outcomes include advance, verify, nurture, refer, or close. “No next meeting” can be the correct result when there is no fit or priority. If advancing to a demo, pass the evidence into a sales demo checklist so the demonstration tests the buyer’s actual workflow. If a pilot is needed, define success and rollback before it starts.

Branching and the qualification handoff

A rigid script assumes every answer leads to the same question. A branch map preserves rigor while respecting the conversation:

• No concrete problem: clarify the educational goal; share an appropriate resource; do not force an opportunity.
• Problem, no evidence: agree on a sample, baseline, or stakeholder interview that could verify it.
• Problem, low priority: record the competing priority and a buyer-defined trigger for revisiting.
• Problem and priority, incomplete fit: name the gap and seek technical, security, legal, or product review.
• Problem, priority, plausible fit: choose a next step that tests the highest-risk assumption.
• Explicit no: confirm whether the buyer wants the loop closed, then respect the answer.

The handoff should carry evidence, not enthusiasm. Use this record: buyer-stated trigger; current-state example; affected people and measures; verified priority or critical event; decision participants and gates; fit evidence; risks; unknowns; exact next action. Mark every field as confirmed, estimated, hypothesis, or unknown. The receiving rep should be able to trace each material statement to a speaker, artifact, or assigned verification.

For a methodology-specific view, see the discovery call framework. For pipeline hygiene after the call, use the sales qualification checklist. These supporting pages should deepen the work without replacing this canonical six-stage plan.

Call QA rubric and manager calibration

Score what a reviewer can observe. Use 0 for absent or harmful, 1 for partial or inconsistent, and 2 for complete and evidenced. Do not award points for confidence, charm, or a manager’s belief that the opportunity is attractive.

Calibrate before using the rubric for coaching or evaluation. Two or more reviewers should independently score the same small, policy-approved call set. Compare scores dimension by dimension, discuss the exact evidence behind disagreements, and revise anchors that permit conflicting interpretations. Re-score another shared sample. Track agreement by dimension rather than hiding disagreement inside one total score.

Use the rubric diagnostically. If reviewers agree that impact evidence is weak, coach impact mapping with short role-plays and review the next sample. If reviewers disagree, fix the rubric or training examples before judging the rep. Recalibrate after material process, product, market, or policy changes. The sales call scorecard template provides a broader coaching artifact.

Finally, audit downstream fidelity: did the CRM preserve the buyer’s language, were unknowns still marked unknown, did the next meeting test the stated risk, and were unsupported claims corrected? A discovery call is high quality when another person can inspect the record, understand what is known, and reproduce the decision about what happens next.