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

The outcome you should expect from this question

The point of this question is not to hear a good-sounding answer. It is to produce a diagnostic reading of a rep's actual deal knowledge in under two minutes, so a manager can decide whether to coach, inspect, or advance. When you ask it in a one-on-one or a pipeline review, you should expect one of three responses, and each maps to a specific next action.

The first response is the surface answer: "They want better reporting" or "They're looking for a modern platform." This tells you the rep has captured the buyer's *stated wish list* and nothing about how the wish list gets converted into a signature. Wish lists are what buyers say in the first call. They are not decision criteria. A wish list has no owner, no weight, and no threshold. When a rep gives you this, the deal has not been qualified — it has been described.

The second response is the single-stakeholder answer: "The VP of Sales wants faster reporting, and she's the one who signs." This is better, because at least there's a name attached, but it is the most dangerous of the three because it *feels* like understanding. The rep has one real data point and has extrapolated it into a whole committee. When the deal stalls in legal, or a security reviewer no one mentioned kills it, this rep will be genuinely surprised.

The third response is the one you're looking for: the rep answers with criteria attached to people, with relative weights, and with at least one acknowledged tension between them. Something like: "Finance is the economic buyer and needs the payback to land inside the current fiscal year, so anything with a long implementation is dead on arrival. Engineering owns the technical veto and cares almost entirely about whether we break their existing data pipeline — they've been burned by a migration before. Sales Ops actually champions us but has no budget. The tension is that the phased rollout finance likes stretches out the timeline engineering wants, and I don't yet know how they'll resolve it."

That third answer contains four things absent from the first two: named roles, a criterion per role, a threshold or constraint attached to each criterion, and an unresolved conflict the rep is tracking. A rep who can produce that has done real discovery. A rep who cannot has been having pleasant conversations.

The practical outcome you should expect at the team level is a forecast that stops being a popularity contest. When every deal above a certain size carries a documented criteria map, the forecast conversation shifts from "how do you feel about it" to "which criterion is still unverified." That is the outcome worth chasing — not better answers in a coaching session, but a pipeline where the unknowns are explicit.

One warning on expectations: the question grades the rep, not the deal. A rep can have deep, accurate understanding of a buyer whose criteria genuinely disqualify you. That is a win — you learned it early. Do not conflate "the rep understands the criteria" with "the deal will close." They are separate readings, and managers who blur them start punishing honest reporting, which is the fastest way to get the criteria map filled with fiction.

What drives that outcome

The question works because of how it is *shaped*, not because of the specific words. Three structural properties do the work, and if you rewrite the question you should preserve all three or you will lose the diagnostic power.

It asks about the buyer's process, not the buyer's opinion. "What are your priorities?" invites a wish list. "How will leadership compare us against the alternatives?" invites a description of a mechanism — a meeting, a scorecard, a business case, an approval chain. Mechanisms have participants and steps. Opinions do not. A rep who has genuinely been inside the buyer's process can describe the mechanism; a rep who has only had good calls can only relay opinions. This is the single most important property to preserve.

It forces comparison. The phrase "against the alternatives" is doing heavy lifting. Decision criteria only exist in a comparative frame — a criterion is the dimension along which one option beats another. Ask a rep what the buyer wants and you get absolutes. Ask what makes the buyer pick *one* and you force them to name the axis of comparison, which is the criterion itself. Reps who have never asked their buyer a comparative question will visibly stall here, because they have no stored answer to retrieve. The stall is the diagnostic.

It requires a threshold, not a direction. "What has to be true" pushes toward binary conditions — a certification exists or it doesn't, payback lands inside the fiscal year or it doesn't, the integration breaks the pipeline or it doesn't. Directional answers ("they want it cheaper") are unfalsifiable and therefore useless for forecasting. Threshold answers can be tested, and a rep who supplies one has given you something you can independently verify with the buyer.

Beneath these three properties sits a fourth driver that is organizational rather than conversational: the rep can only answer well if the buying committee has actually been mapped. Enterprise buying groups have grown substantially over the past decade, and a rep working a committee purchase with one contact simply cannot answer the question correctly no matter how skilled they are. So a bad answer sometimes indicts your process rather than your rep — if your team has no motion for multi-threading, the question will produce uniform failure, and the fix is territory and access, not coaching.

The last driver is time-in-deal. Ask this in the first week after a discovery call and a weak answer is normal. Ask it at the proposal stage and a weak answer is a forecast problem. The same question means different things at different stages, which is why the diagnostic should always be paired with a stage check.

The diagram above is worth walking through with a rep rather than applying to them silently. The branch points are the coaching curriculum: naming stakeholders is an access problem, attaching thresholds is a questioning problem, and identifying tensions is a synthesis problem. Each requires a different intervention, and managers who treat all three as "do better discovery" get no improvement because they never diagnose which rung the rep is stuck on.

Benchmarks and realistic ranges

Be careful with benchmarks here, because most numbers floating around this topic are vendor marketing. What follows are ranges you can defend internally, framed as expectations to calibrate against rather than industry law.

Stakeholder count per criteria map. For a mid-market deal, expect a competent rep to name three to five people with distinct criteria: an economic buyer, a technical or security reviewer, a primary user-owner, and often a procurement or legal gate. For enterprise, five to eight is more realistic. If a rep names one, that is a red flag regardless of deal size. If a rep names twelve, check whether they are listing attendees rather than decision-makers — attendance is not authority, and padding the map with names is a common way to look thorough.

Criteria per stakeholder. One or two. A stakeholder with six criteria has not been asked what they'd trade. Real decision-makers have one thing they cannot compromise on and one or two they'd like. Reps who report long criteria lists per person usually recorded a conversation rather than analyzed one.

Answer time. A rep who understands the criteria answers this question in 60 to 90 seconds without notes. A rep reading from a CRM field is not demonstrating understanding, they're demonstrating that someone filled in a form. Ask the question in a hallway, not in a review with laptops open, at least once per quarter per rep.

How often criteria change. Expect roughly one material change per deal per quarter in a long cycle — a stakeholder leaves, budget moves, a competitor reframes the evaluation, a compliance requirement appears. If a rep's criteria map has been static for six months on a nine-month deal, either the deal is dead and nobody has said so, or the map is not being maintained. Both are worth knowing.

Coverage targets. A reasonable rollout target is documented criteria on 100% of deals above your top-quartile deal size, and on 100% of anything in your last two pipeline stages, regardless of size. Trying to enforce it on every inbound small deal generates form-filling theater and burns the credibility of the whole practice. Pick the threshold where a lost deal actually hurts.

Improvement timeline. Do not expect the diagnostic to change win rates in a quarter. What moves first — usually within four to six weeks — is stage accuracy: deals get pushed back to earlier stages because someone finally noticed the technical reviewer had never been contacted. That looks like pipeline shrinkage on the report and feels like bad news. It is the intervention working. Forecast accuracy improvements follow, and revenue effects trail by at least a full sales cycle, which for many teams means two to three quarters before anything shows up in the numbers you actually care about.

Failure rate on first exposure. When teams run this diagnostic for the first time, it is normal for the majority of reps to give wish-list or single-stakeholder answers. Managers who interpret that as a hiring problem are usually wrong. It is far more often a discovery-process problem: nobody ever told reps that the comparative question was expected, so nobody asked it.

Risks, edge cases, and failure modes

The question becomes a script. The most common failure is that reps learn the shape of the acceptable answer and start producing it without the underlying work. Within a quarter of introducing this diagnostic, you will hear reps supply named stakeholders with confident-sounding thresholds that were never spoken by the buyer. The defense is verification: on any deal that matters, one criterion per quarter gets checked directly with the buyer, ideally by the manager on a joint call. "Your team mentioned the payback window matters most — is that right, or is the integration risk the bigger issue?" Two of those a quarter keeps the whole map honest, and reps quickly learn that fabricated criteria surface.

Managers use it as a gotcha. If the question is only ever asked in front of peers, and a weak answer produces public criticism, reps will optimize for not being asked. They will stop bringing early-stage deals into review, or they will pre-write answers. Ask it privately first, treat the first weak answer as information, and coach the specific rung the rep is stuck on. The diagnostic value collapses the moment the answer carries a penalty.

Champion capture. A rep with a genuinely enthusiastic champion often produces an answer that sounds excellent but is entirely one person's model of their own organization. Champions routinely misrepresent how their leadership decides — not dishonestly, but because they aren't in the room where the comparison happens. The tell is when every criterion in a rep's map traces back to the same source. Ask "who told you that?" for each criterion. If the answer is the same name four times, the map is one person's opinion wearing four hats.

Transactional and inbound motions. For short-cycle, single-signer deals, this question is overkill and will produce a lot of noise. If the buyer is an individual with a credit card, the decision criteria are often just price and whether it works. Applying committee-grade diagnostics there wastes coaching time. Scope the practice to deals with a real evaluation.

Renewals and expansions. These need a modified version. The comparison is often against doing nothing, or against an internal build, rather than against a named competitor. The question becomes "what would have to be true for them to *not* renew, and who would raise it?" Reps who only track happy usage signals are frequently blindsided when a new leader arrives with different criteria.

Criteria that are political rather than functional. Some real criteria never appear on any scorecard: an executive has a relationship with a competing vendor, a team is protecting a project they built, a decision is being delayed until after a reorg. Reps who report only rational criteria on a deal that is obviously stuck are usually missing a political one. The follow-up that surfaces this is "if the scorecard says we win, is there anyone who'd still push back?" Ask it about the deals that don't add up.

Over-indexing on the artifact. If the CRM field becomes the goal, you will get a well-maintained field and no better understanding. The field is a byproduct. The verbal answer, given without notes, is the actual measurement. Any RevOps team that builds the reporting before building the coaching habit ends up with clean data about nothing.

The rep who understands but can't articulate. Rare, but real — some strong closers hold the criteria intuitively and stumble when asked to formalize it. Test by asking a hypothetical instead: "If they had to drop one requirement to hit the date, which goes?" A rep with real understanding answers that instantly even if they can't produce a tidy map. Don't fail someone on presentation format.

A practical rollout plan

Rolling this out well takes about a quarter and touches three groups: managers, reps, and whoever owns your CRM configuration.

Weeks one and two — establish the baseline. Managers ask the question in one-on-ones only, on two or three active deals per rep, and record which of the three answer types they got. No coaching yet, no CRM changes, no announcements. You are measuring the current state, and if you announce it first you will measure preparation instead. Aggregate the results by team, not by individual, and share the aggregate. Most teams discover the problem is broader and more systemic than they expected, which is politically useful — it reframes the initiative as a process fix rather than a performance issue.

Weeks three and four — teach the follow-ups. The question itself is easy. What reps need is the set of second questions that get a buyer to reveal criteria: asking who else has to agree before this moves, asking what happened the last time they bought something like this, asking what would make them pick a competitor, asking what the internal business case has to show. Run one session on these, then have each rep take one live deal and go re-discover it. The measurable output is not a filled form — it is a rep coming back and saying "there's a security reviewer I didn't know about."

Weeks five and six — build the lightweight artifact. Now, and only now, add the CRM structure: a small related object or a structured field capturing stakeholder, role, criterion, threshold, and how it was verified. Keep it to five fields. Every additional field halves adoption. The verification field matters most — it distinguishes "the buyer told me directly" from "my champion said so" from "I inferred it," and that distinction is where most bad forecasts hide.

Weeks seven through ten — wire it into the stage gate. Pick one stage — usually the transition into proposal or into the final stage — and make a populated criteria map with at least three verified entries a condition of entering it. Expect pipeline to visibly contract. Warn your leadership before this happens or you will spend the quarter defending it. The contraction is deals moving back to where they actually were.

Weeks eleven and twelve — start the audit. Managers verify one criterion per major deal directly with the buyer. Track the mismatch rate: how often the buyer's answer differs from what the rep recorded. That mismatch rate is the real health metric for this whole practice, and it is the number a RevOps team should report on quarterly. A rising mismatch rate means the map is drifting toward fiction and the coaching needs to restart.

The sustaining motion after the quarter is small: one unscripted verbal check per rep per quarter, one buyer verification per major deal, and a quarterly look at the mismatch rate. If the practice needs more than that to stay alive, it never took root, and adding process will not save it.

Related questions

Should the question change wording by deal stage?

Keep the structure, adjust the specificity. Early stage: "how will your team compare options?" Late stage: "what still has to be true for you to sign this quarter?" Both force comparison and thresholds; the late-stage version adds a date, which is where slippage hides.

Can this be scored consistently across managers?

Yes, with a three-tier rubric: wish list, single stakeholder, or mapped-with-tension. Avoid finer scales — managers won't apply them consistently, and the three tiers already point to three distinct coaching actions.

What if the buyer genuinely hasn't decided their criteria yet?

That's a valid and valuable answer, provided the rep can say so specifically: which criteria are unformed, who will define them, and by when. "They haven't decided" without those details is indistinguishable from not knowing.

Does this replace a qualification framework?

No. It's a diagnostic that tests whether the framework's decision-criteria section reflects reality. The framework structures what to collect; this question checks whether the rep actually collected it or filled in plausible text.

How do I use it on a deal I've inherited mid-cycle?

Ask it about the previous rep's notes: "based on what's recorded, what does the buyer compare on, and what's missing?" A strong answer identifies the gaps in the inherited record rather than treating it as complete.

FAQ

Isn't one question too blunt an instrument to judge a rep's discovery?

It isn't judging discovery in general — it's testing one specific thing, whether the rep has converted conversations into a model of how the buyer decides. That's narrow on purpose. Pair it with other checks for other skills; don't stretch it into a general competence rating.

What if a rep gives a perfect answer and then loses the deal?

Perfectly normal and not a mark against the diagnostic. Understanding the criteria tells you whether you can compete on them, not whether you'll win. Some deals are lost the moment the criteria are set, and knowing that early is worth more than a surprise loss late.

How do I stop this from turning into another CRM field nobody fills out?

Build the coaching habit before the field. If managers are asking the question verbally every week and acting on the answers, the field becomes a place to store something people already do. If you ship the field first, you get compliance and no understanding.

Should reps ask this exact wording of the buyer?

Not verbatim — it's phrased for the manager-to-rep direction. Buyer-facing versions are softer and split across a conversation: how the evaluation works, who weighs in, what would make them choose someone else. Same three properties, less interrogative.

Does this work for technical or highly regulated purchases?

Especially well, because those buyers usually have explicit written criteria — a requirements document, a security questionnaire, a formal scoring matrix. A rep on a regulated deal who can't describe the scoring mechanism has not been given real access, and that's the finding.

How does a RevOps team measure whether this is working?

Track the mismatch rate between what reps record and what buyers confirm, plus stage-regression volume in the first two months. Both are leading indicators. Win rate is a lagging indicator that will be confounded by everything else you change in the same period.

Sources

• Gartner — B2B Buying Journey research
• Harvard Business Review — The New Sales Imperative
• McKinsey — Growth, Marketing & Sales insights
• Gong Labs — sales research and call analysis
• Forrester — B2B sales and marketing research
• Winning by Design — revenue architecture resources
• SaaStr — B2B sales and go-to-market content
• Salesforce — sales resources and guides

Related on PULSE

• [What question would you ask to test if a salesperson truly understands their buyer's industry trends and challenges?](/knowledge/q14422)
• [Top 10 questions to reveal if a rep truly understands buyer personas](/knowledge/q14356)
• [How can I use open-ended questions to help a sales rep identify their own weaknesses in a deal review?](/knowledge/q14346)
• [What are the most effective open-ended questions to ask a struggling sales rep during a coaching session?](/knowledge/q14343)
• [How do I ask a question that reveals whether a rep is listening actively or just waiting to speak?](/knowledge/q14370)
• [What question reveals whether a salesperson has properly qualified a lead before entering the pipeline?](/knowledge/q14410)