Which open-ended question reveals whether a rep truly understands the buyer's decision criteria?

The outcome you should expect

When a rep can answer this question with specifics, the deal behaves differently for the rest of the cycle. Discovery notes stop reading like a feature checklist ("wants better reporting," "cares about security") and start reading like a decision map: named stakeholders, the metric each one is judged on, and the internal trade-off the buyer has to make to justify the purchase. That shift shows up first in forecast quality. Reps who can articulate the buyer's 90-day outcome tend to produce deal stages that match reality — a deal doesn't sit in "commit" for two quarters because nobody surfaced that the CFO's payback threshold hadn't actually been met.

The second thing that changes is objection handling. A rep who understands the decision criteria isn't surprised in the final committee review. They already know the CTO's non-negotiable is a security certification, that the VP of Sales cares about ramp time more than feature count, and that the CFO's real question is payback period, not sticker price. When those criteria are known in advance, the rep can pre-empt the objection in the proposal instead of scrambling to answer it live in front of the full committee — which is where deals quietly die.

Third, win-loss patterns sharpen. Deals that are lost after a rep could answer this question tend to be lost for real, disqualifying reasons — budget froze, a competitor had a feature the buyer's CTO genuinely needed, the internal champion left the company. Deals lost when the rep could never answer it tend to be losses to "no decision," which is the single most preventable loss reason in B2B selling: the deal simply never had a clear enough internal case built around it, because the rep never understood what would make leadership prioritize it.

Finally, expect friction on the front end of adopting this. Reps who are used to feature-first discovery will initially get vague answers the first few times they ask it, because most buyers haven't thought this precisely about their own internal politics either. That's fine — the rep's job is to help the buyer think it through, not to expect a polished answer on the first try. The question is a starting point for a conversation, not a single prompt-and-response exchange.

What drives that outcome

The mechanism behind why this single question works better than generic discovery questions is that it collapses three things a rep normally has to ask about separately — priority, ownership, and trade-off — into one answer. "What are your priorities?" gets a list. "Who's involved in the decision?" gets a list of names. "What's your timeline?" gets a date. None of those, alone or combined, force the buyer to connect a specific number to a specific person to a specific deadline. The 90-day framing does, because it demands a concrete, time-bound outcome rather than an abstract preference.

That specificity is what separates surface-level discovery from a rep who genuinely understands the buyer's decision criteria. A rep repeating back "cost, security, ease of use" hasn't learned anything a homepage couldn't tell them. A rep who can say "the CFO needs to see payback inside 12 months to sign off before the board meeting, and the CTO's approval is contingent on a security review that takes three weeks, so the real internal deadline is six weeks out, not the quarter-end date they quoted me" has done the work of triangulating multiple stakeholders' criteria against a real internal calendar.

The RevOps function matters here because this isn't just a coaching trick — it's a data-quality problem. If the CRM field for decision criteria is a free-text box that reps fill in with "wants automation," the pipeline data is functionally useless for forecasting or for building enablement content. When RevOps structures the field to require a metric, an owner, and a deadline, the 90-day question becomes the natural prompt reps use to fill it in correctly, and forecast models built on that data get meaningfully more reliable inputs to work with.

Benchmarks and realistic ranges

B2B buying groups have grown steadily larger over the past several years; most enterprise and upper-mid-market deals now involve somewhere in the range of six to fifteen people with formal or informal input into the decision, up from a much smaller handful a decade ago. That range matters because it sets the floor for how many distinct sets of decision criteria a rep needs to hold in their head at once — a rep who can only articulate one stakeholder's priorities is, by definition, only accounting for a fraction of the committee.

Sales cycle length is the second useful benchmark. Complex B2B deals with multiple approvers commonly run somewhere between six and twelve months from first contact to signature, and a meaningful share of that time isn't spent evaluating the product at all — it's spent on internal buyer-side coordination: budget approval, security review, procurement, legal redlines. A rep who understands the buyer's decision criteria can usually identify which of those internal steps is the actual gating item, versus a rep who's still selling features while the real bottleneck sits in a legal queue three departments away.

On the coaching side, organizations that build structured discovery frameworks — MEDDIC, MEDDPICC, Command of the Message, or an internal equivalent — around explicit decision-criteria capture generally report meaningfully higher forecast accuracy and fewer late-stage surprises than teams running unstructured discovery. The specific lift varies by organization and how rigorously the framework is enforced, but the direction is consistent enough across public sales-methodology research that it's treated as a near-baseline expectation in mature RevOps orgs, not a nice-to-have.

Deal-loss data is the third data point worth tracking. A large share of B2B "losses" aren't losses to a competitor at all — they're losses to no decision, meaning the buyer never built enough internal consensus to act. Industry win-loss research consistently puts no-decision as the single largest loss category in complex B2B sales, frequently outpacing competitive losses. That's the direct cost of reps who never fully mapped the buyer's decision criteria: the deal wasn't lost, it was never actually buildable into a decision the committee could rally around.

Risks, edge cases, and failure modes

The most common failure mode is reps turning the question into a script. Asked verbatim, cold, in the first discovery call, "what would need to happen in 90 days for this to be a top priority" can come across as presumptuous or performative if there's no rapport yet. The question works because it triggers real reflection, not because the specific words are magic — a rep who fires it off mechanically without following up on the answer gets the same shallow response as any other generic discovery question.

A second failure mode is single-threading. A rep can get a crisp, specific 90-day outcome from one stakeholder — often the champion — and mistake that for having mapped the whole committee's criteria. The champion's metric might be real but secondary; the actual gating criteria could sit with an economic buyer or a security reviewer the rep hasn't even met yet. Understanding one person's decision criteria in detail is not the same as understanding the committee's, and treating it as equivalent is a common way forecasts overstate confidence.

A third risk is buyers giving an answer that sounds specific but isn't grounded — a stakeholder who names a number to satisfy the question rather than because it reflects genuine internal urgency. Reps need a way to stress-test the answer, typically by asking what happens if that 90-day outcome doesn't happen, or who else needs to agree that it matters. An outcome nobody else on the buying side would defend in a room isn't a real decision criterion; it's a placeholder answer.

There's also a coaching-scale risk. This question is easy to teach in a training session and much harder to reinforce in live calls, because it requires a manager or RevOps team to actually listen to calls or read notes closely enough to tell a real, specific answer from a vague one dressed up in confident language. Without that verification loop, reps learn to produce answers that sound structured in a CRM field without the underlying discovery actually happening — which quietly reintroduces the exact problem the question was meant to solve.

Finally, this question — like any single discovery prompt — has diminishing returns if it's the only tool in the rep's kit. It's most effective paired with a broader qualification framework that also covers economic buyer identification, decision process, and competitive landscape. Used in isolation, a rep can nail the 90-day-outcome answer and still miss that procurement requires three competing bids, or that the actual decision process routes through a committee the rep hasn't been introduced to yet.

A practical rollout plan

RevOps and enablement teams that want reps consistently using this question — rather than treating it as a one-off training exercise — generally roll it out in a sequence that pairs the question with a structural change to how criteria get captured, not just a talk track reps are told to memorize.

Start by auditing a sample of recent closed-lost and no-decision deals specifically for whether decision criteria were documented with a metric, an owner, and a deadline, or left as vague free text. This baseline makes the gap visible to sales leadership in a way that's hard to argue with, and it gives RevOps a defensible reason to change the CRM structure rather than just adding a coaching tip nobody enforces.

Next, restructure the CRM field itself. A free-text "notes" box invites vague answers; a structured object with required fields — stakeholder name, role, the metric they're accountable for, and the internal deadline tied to it — forces the discipline the question is meant to produce. If the tooling supports it, tie a validation rule to deal-stage progression so a deal can't advance past a defined qualification stage with that field left empty or generic.

Then train through real call review rather than roleplay alone. Pull a handful of recent recorded discovery calls — including ones from deals that stalled — and have reps identify, in each one, whether the 90-day outcome was ever asked and, if so, whether the answer given was specific enough to act on. Comparing what was actually said against what the deal's later outcome turned out to be is a far more durable teaching moment than an abstract script.

Finally, build a lightweight review cadence — weekly or biweekly — where a manager or RevOps partner spot-checks a small sample of deals for whether the criteria field is genuinely specific, not just filled in. This is the step teams most often skip, and it's the one that determines whether the question becomes a durable habit or a training-day artifact that fades within a quarter. Treat the review as coaching, not compliance: the goal is to help reps get better at recognizing a vague answer when they hear one, not to punish them for an early miss.

Related questions

What question tests if a rep truly understands the buyer's industry and challenges?

Ask what specific event in the buyer's market — a regulation, a competitor move, a cost pressure — made this problem urgent now rather than a year ago. A rep who can't name the trigger doesn't understand the context driving the decision.

How do you know if a rep is single-threaded on a deal?

Ask the rep to name every person who could say no to the deal, not just who said yes. A single-threaded rep can usually only name their champion and struggles to describe anyone else's stated concerns.

What question uncovers the real emotional driver behind a purchase?

Ask what happens to the champion personally if this project fails or stalls. A rep who understands the human stakes, not just the business case, usually gets a more honest, specific answer.

How do you coach reps to stop pitching features too early?

Have them answer the buyer's 90-day outcome question before they're allowed to walk through any product capability in a call. If they can't, the meeting stays in discovery instead of moving to a demo.

Why do deals stall even when the champion seems bought in?

Most stalls happen because a second stakeholder's decision criteria were never surfaced or addressed, not because the champion changed their mind — which is exactly what this question is designed to catch early.

FAQ

What makes this question better than "What are your priorities?" "What are your priorities?" invites a generic list — cost, ease of use, security — that could apply to nearly any deal. The 90-day outcome question forces a specific, time-bound answer tied to a named stakeholder and a real trade-off, which is much harder to fake and much more useful for forecasting.

Does this question work on a first discovery call? It can, but it often lands better once some rapport exists and the rep has already asked about the buyer's current process and pain. Asked cold in the opening minutes of a first call, it can feel presumptuous; asked after genuine context-setting, it reads as a natural next step.

How does RevOps operationalize this beyond a talk track? By building the answer's components — metric, stakeholder owner, deadline — into a required CRM field rather than a free-text note, and reviewing a sample of deals regularly to check that the field is filled in with real specifics rather than generic placeholders.

What's a red flag that a rep's answer isn't real? An answer with no named stakeholder, no number, and no timeframe — anything that could be copy-pasted into a different deal without changing a word is a sign the rep either didn't ask a strong follow-up or the buyer gave a placeholder response that was never stress-tested.

Can this question replace a full qualification framework like MEDDPICC? No. It's a strong single probe for the decision-criteria component specifically, but it works best layered into a broader framework that also covers economic buyer, decision process, and competition — using it alone still leaves other qualification gaps open.

How often should managers check whether reps are actually using this well? A weekly or biweekly spot-check on a small sample of deals is usually enough to keep the habit alive without turning it into a compliance exercise; the goal is catching vague answers early, not auditing every call.

Sources

• Gartner: B2B Buying Journey Research
• McKinsey: The New B2B Growth Equation
• Gong Labs: Sales Research and Benchmarks
• Forrester: B2B Buying Research
• HubSpot: State of Sales Report
• MEDDICC: Decision Criteria Framework
• Winning by Design: Sales Methodology Resources
• LinkedIn Sales Solutions: State of Sales Report

Related on PULSE

• [Top 10 questions to reveal if a rep truly understands buyer personas](/knowledge/cg0820)
• [What question do you ask to uncover the real emotional driver behind a prospect's buying decision?](/knowledge/cg0920)
• [How do you coach reps to use stage exit criteria correctly?](/knowledge/cg0109)
• [What question reveals whether a rep is effectively using social proof in their pitch?](/knowledge/cg0843)
• [How do I ask a question that reveals whether a rep is listening actively or just waiting to speak?](/knowledge/cg0835)
• [What question would you ask to test if a salesperson truly understands their buyer's industry trends and challenges?](/knowledge/cg0892)