What specific question helps a rep realize they are not asking enough discovery questions during the first call?

The two self-check questions reps confuse

There are really two different diagnostic tools reps reach for after a first call, and mixing them up is why so many reps think they're doing enough discovery when they aren't.

Option A: the outcome-and-stakeholder question. This is the question above — "what specific outcome, by when, and who signs off?" It's a *content* check. It tests whether the rep understands the deal, not whether they talked enough. A rep can ask fifteen questions on a call and still fail this test if none of those questions touched the buying committee or the timeline. This is the harder, more valuable check because it can't be gamed by volume — you either know the answer or you don't, and if you don't, it's obvious within seconds of trying to answer it out loud.

Option B: the question-count self-audit. This is a *volume* check — literally counting, from a call recording or a CRM activity log, how many discovery questions the rep asked versus how many they should have asked. It's faster to run (a manager can eyeball a transcript in two minutes) and it's the metric most call-intelligence tools default to because it's mechanically easy to score. But it has a blind spot: a rep can hit a "good" question count by asking five variations of the same shallow question ("What's your timeline?" "So when are you hoping to have this live?" "Any deadline on your end?") without ever getting to outcome, budget, or committee structure.

The trade-off is speed versus depth. Question-count audits scale — a sales manager running 1:1s with eight reps a week doesn't have time to interrogate the content of every discovery question, so a count-based scorecard gives them a fast first pass. The outcome-and-stakeholder question doesn't scale the same way; it requires the rep (or a coach) to actually sit with the answer and judge whether it's specific enough. But it's the one that catches the failure mode that matters most in RevOps: a rep who *sounds* thorough because they talked a lot, but never surfaced who actually controls the budget or what "success" is measured against.

The practical answer is to use both, in sequence. Run the count first because it's cheap and catches the most obvious gaps — a rep who asked three questions on a forty-minute call has a volume problem, full stop, and no amount of outcome-question sophistication fixes that. Once volume clears a minimum bar, move to the outcome-and-stakeholder question as the depth check, because that's the one that predicts whether the deal actually has a path to close.

How to decide which one to run first

Use the decision below immediately after a first call, before the notes go cold. It routes a rep toward the count-based check when volume is clearly the problem, and toward the outcome-and-stakeholder question when volume looks fine but the deal still feels vague.

The routing logic matters because it stops managers from treating every discovery gap the same way. A rep with a volume problem needs a different fix (a longer question bank, more practice pacing the call) than a rep with a depth problem (who needs to learn *which* questions to ask, not more of them).

Concrete numbers behind each option

The question-count check works off benchmark ranges that most sales training programs converge on, even though the exact number varies by deal complexity and industry. A first call in the 30-45 minute range that produces fewer than 5 open-ended discovery questions is a near-universal red flag across MEDDIC, MEDDPICC, and Challenger-style training — it usually means the call drifted into product demo or rapport-building too early. The commonly cited target band is 8-12 well-structured questions on a first call, front-loaded with open-ended framing ("walk me through...", "what happens if...") rather than closed yes/no questions. Closed questions aren't worthless, but a call that's mostly closed-ended questions caps out the amount of context a rep can gather, because closed questions don't invite elaboration.

The outcome-and-stakeholder question doesn't have a numeric score in the same way — it's pass/fail on specificity — but it decomposes into a small number of required elements that map directly onto MEDDPICC's own categories: Metrics (the specific number that defines success), Economic Buyer (who controls the budget and who personally bears risk if this fails), Decision Criteria and Decision Process (how the choice gets made and in what order), and Identify Pain (why this outcome matters now rather than later). A rep's answer needs to touch at least three of those four categories with a specific name, number, or date attached — not a role description, but an actual answer. "The VP of Sales wants faster reporting" fails because it names a role and a vague want, not a metric or a decision process. "The CFO needs onboarding time cut from three weeks to one before the Q1 board review, and procurement won't move without a security sign-off from IT" passes because it has a name-equivalent, a number, a deadline, and a second gating stakeholder.

A useful cross-check number for RevOps teams: buying committees on mid-market and enterprise B2B deals commonly run 6-10 people by the time a deal reaches procurement, even when only one or two of them show up on the first call. If a rep's stakeholder answer names only the person on the call, that's a strong signal the rep hasn't asked "who else has to say yes" — which is itself a discovery question that belongs in the first-call script, not something to backfill in week six.

Implementation: building the check into the call routine

The mechanism that makes this stick is a short, mandatory self-audit run immediately after every first call, before the rep moves to the next task. It should take roughly 90 seconds and should live in the CRM as a required field, not a separate document that gets skipped under time pressure.

The sequence: in the first 30 seconds, the rep writes down their answer to the outcome-and-stakeholder question from memory, without checking notes — this simulates what they'd have to say if asked cold in a pipeline review. In the next 30 seconds, they score that answer against the three-of-four MEDDPICC categories described above: does it name a metric, an economic buyer with a personal stake, a decision process or timeline, and a reason the timing matters now. In the final 30 seconds, if the answer is missing a category, the rep writes down the exact follow-up question they'll ask on the next call to fill that gap — not a vague reminder like "ask more about budget," but the literal sentence they'll say.

That output — the score and the specific follow-up question — should be logged as a CRM field tied to the opportunity, because it turns a one-off self-check into a pattern a manager can see across a rep's whole pipeline. A rep who consistently scores low on the "economic buyer" category across ten different deals has a specific, coachable skill gap, and that's a very different conversation than a rep who's inconsistent deal-by-deal.

Sequencing matters here too. Don't introduce the outcome-and-stakeholder question in isolation during a coaching session — it lands better when a rep has just failed to answer it on a real deal, because the gap is concrete rather than hypothetical. The recommended rollout order is: first, run the question-count audit across a sample of recent calls to establish whether volume is even adequate; second, for reps who clear the volume bar, introduce the outcome-and-stakeholder question as the next-level check; third, once both are running, fold the 90-second self-audit into the standard call-wrap-up workflow so it becomes automatic rather than something a manager has to remember to assign.

Related questions

How many discovery questions should a rep ask on a first call?

Most training programs target roughly 8-12 well-structured, mostly open-ended questions on a 30-45 minute call. Fewer than 5 is a near-universal signal the call skipped discovery in favor of product talk or rapport-building.

What is MEDDPICC and why does it matter for discovery coaching?

MEDDPICC is a qualification framework covering Metrics, Economic Buyer, Decision Criteria, Decision Process, Paper Process, Identify Pain, Champion, and Competition. Each letter maps to a discovery question a rep should be able to answer after a first call.

How do I know if a rep talked to the wrong stakeholder?

If the rep's outcome answer names only the person who took the call, and that person can't authorize budget or isn't the one who'll use the product daily, the rep likely missed the actual decision-maker or end-user.

Should discovery questions be scripted or improvised?

A rep needs a planned bank of 8-12 open-ended questions going in, but should improvise the order and follow-ups based on answers — a rigid script that ignores what the buyer just said produces shallow, checkbox-style discovery.

FAQ

What's the single best question to check if a rep did enough discovery? "What specific outcome does this need to produce in the next 90 days, and who besides you has to agree it happened?" It fails a rep instantly if they only have a vague want and one name, which is the most common gap after a rushed first call.

Is a low question count always a problem? Usually, but not always — a call where the buyer volunteers detailed answers unprompted can be thorough with fewer explicit questions. Still, fewer than 5 distinct discovery questions on a standard first call is worth reviewing, because it often means the rep moved to pitching too early.

Can this replace call scoring software? No — call-intelligence tools are good at counting questions and flagging talk-time ratios automatically, which is faster than manual review. The outcome-and-stakeholder question adds a judgment layer software can't fully automate: whether the answer given is actually specific.

How does this connect to RevOps, not just sales coaching? RevOps owns the systems that make discovery gaps visible — the CRM fields, the call-recording integration, the pipeline-review cadence. Without a RevOps-built process to log and surface the self-audit score, the check stays a one-off habit instead of a measurable program.

What if the rep genuinely can't get stakeholder names on a first call? That's a valid outcome, but the rep should still be able to name the *role* and explain why they haven't reached that person yet, plus a plan to get there. "I don't know" with no follow-up plan is the failure mode; "I know IT security has to sign off, I haven't identified who yet" is not.

How often should this self-audit run? After every first call, ideally, since discovery quality on call one predicts a large share of downstream deal risk. For teams that can't sustain that cadence, running it on a rotating sample each week still surfaces coaching patterns without adding much overhead.

Sources

• Gong: Sales call and discovery research
• Gartner: B2B buying journey and buying committees
• Salesforce: MEDDPICC for enterprise sales
• Challenger Inc: tension-based discovery
• HubSpot: sales discovery questions
• Forrester: B2B sales research
• MEDDICC: framework overview
• Richardson Sales Performance: SPIN Selling

Related on PULSE

• [What question can I use to uncover a rep's fear of asking for the close?](/knowledge/cg0837)
• [How can I phrase a coaching question that helps a rep realize they are over-promising on delivery timelines?](/knowledge/cg0815)
• [Can you give an example of a reflective question that helps a salesperson realize they are over-engineering solutions?](/knowledge/cg0862)
• [What question would you ask during a pipeline review to force a rep to prioritize deals based on probability, not hope?](/knowledge/cg0902)
• [What specific questions can I ask during a one-on-one to uncover a sales rep's biggest skill gap?](/knowledge/cg0813)