How do you craft a question that makes a salesperson reflect on whether they are selling to the right decision-maker?

A deal that looked healthy right up until it wasn't

A rep on a mid-market team has been working a six-figure platform deal for eleven weeks. Every signal on the surface looks strong. The Director of Sales Operations replies within an hour, has taken four calls, built an internal slide on the rollout plan, and asked for a security questionnaire. The opportunity sits at "Proposal" in the CRM with a close date fourteen days out. The forecast call comes and the rep commits it.

Now read the same deal through a different lens. Across four recorded calls, nobody has said the words "budget," "approval," "procurement," or "board." No one has been added to the opportunity beyond the original contact and one engineer. The rep has never spoken to anyone with a VP or C-level title. The security questionnaire came from the contact, not from an actual security team, which means it is a hygiene exercise, not a gate.

The generic coaching question here — "Do you think you're talking to the decision-maker?" — produces a defensive yes. The rep has invested eleven weeks; the sunk-cost pull is enormous, and the question invites a one-word denial that costs nothing to give. It is a yes/no question about the rep's own competence, which is the least productive shape a coaching question can take.

The question that actually breaks the frame is specific, mechanical, and about the *deal*, not the rep: "Walk me through the last time this company bought something in this price range. Who signed it, how long did it take, and how do you know?" Three things happen. First, the rep has to produce facts, not opinions. Second, the frame moves from "are you good at your job" to "what do we know about this account," which lowers the defensive cost of admitting a gap. Third, the answer is verifiable — either the rep can recount a prior purchase or they cannot, and both of those are useful.

In practice the rep usually answers something like, "I think it goes through their CFO but I haven't asked." That is the moment of reflection. Not because the manager delivered a verdict, but because the rep heard themselves say "I haven't asked" out loud. The design goal of every question in this article is to engineer that sentence.

What makes a question trigger reflection instead of defense

Reflection is a cognitive event with preconditions. A question triggers it when the rep discovers a gap in their own reasoning while answering — not when a manager announces the gap. That distinction drives every design choice below.

Ask for artifacts, not assessments. "Is this the right person?" asks for a judgment the rep has already made and defended internally. "Show me where in your notes the approval path is written down" asks for an artifact. Missing artifacts are undeniable in a way that missing judgment is not. Good artifact prompts: the name in the economic-buyer field, the date of the internal approval meeting, the email where the contact described their sign-off limit, the org-chart screenshot, the prior-purchase precedent.

Make the question about the account, not the rep. Grammatical subject matters more than managers expect. "Why haven't you met the CFO?" makes the rep the subject and triggers justification. "What does this company's approval process look like for spend at this level?" makes the company the subject; the gap surfaces as a fact about the account rather than a failure of the rep. Same information, radically different defensive posture.

Force a number or a name. Open-ended questions get open-ended answers, and open-ended answers hide gaps. Anything that terminates in a specific token — a dollar threshold, a title, a date, a headcount of stakeholders met — either gets filled or visibly does not. "Who's involved?" gets "a few people." "List every person who has been in a meeting or on an email thread about this, with their title" gets a list you can count.

Ask for the counterfactual. "If this deal dies, what kills it?" is one of the highest-yield reflection prompts in existence because it bypasses the rep's optimism entirely. A pre-mortem asks the rep to argue against their own forecast, and reps are usually shockingly accurate when given permission to be pessimistic. If the answer is "someone above my contact says no," the authority gap has just been self-diagnosed.

Use silence after the question. The single most common coaching failure is the manager answering their own question after four seconds of quiet. Reflection needs the pause. If the rep is thinking, the question worked; interrupting it converts a discovery into a lecture.

Do not stack. "Who's the economic buyer, and have you met them, and what's their budget cycle?" is three questions, and the rep will answer the easiest one. One question, one pause, one answer, then the follow-up.

A bank of questions that work, organized by what they expose

Different gaps need different probes. Keep a short list per gap type rather than one universal question, because a repeated question stops producing reflection after the third time a rep hears it.

Authority ceiling. "What is the largest purchase your contact has personally approved, and how do you know that number?" A rep who answers "they told me they handle all vendor decisions for the team" has an unverified claim, not a fact. Follow-up: "Would you bet your commission on that being true above your deal size?"

Approval path. "Between a verbal yes and a signed contract, how many humans touch this, and what does each one need?" The count is the payload. A rep who says "just legal" on an enterprise deal has almost certainly missed procurement, security review, and a finance approval tier.

Precedent. "When this company bought their last comparable tool, what did the process look like end to end?" This is the highest-value question in the bank because the past process is the best available predictor of the future one, and the champion usually knows it and will happily explain it if asked.

Multi-threading depth. "Name every person at this account who could stop this deal, and mark the ones you have spoken to directly." Reps consistently under-count blockers. The exercise of listing veto-holders surfaces the security lead, the sysadmin who owns the integration, and the finance analyst who owns the renewal calendar.

Champion strength. "What has your champion done for you that cost them something internally?" Real champions spend political capital — they book the meeting with their boss, forward your business case, defend the line item. A contact who only takes your calls is a coach, not a champion, and the distinction predicts outcomes better than title does.

Consequence framing. "If this slips two quarters, what changes for your contact personally?" No personal consequence means no urgency, and no urgency usually means you are talking to someone for whom the status quo is comfortable.

Reverse pitch. "Say the pitch back to me the way your contact would say it to their CFO." This one is brutal and effective. If the rep cannot produce a version of the story in the economic buyer's language — cost, risk, time-to-value, headcount — then the champion cannot either, and the deal is stuck below the authority line no matter how many meetings get booked.

Numbers worth arguing with, and the ones you should measure yourself

Be careful with borrowed benchmarks. Published figures on buying-committee size vary widely by segment and methodology, and industry research has consistently shown enterprise B2B purchases involving roughly six to more than ten stakeholders depending on deal size and category. Use these as a prompt for curiosity, not as a target: the number that matters is the one in *your* closed-won deals.

Instrument your own funnel instead. These are cheap to compute from CRM and calendar data and far more persuasive in a coaching conversation than any external stat:

Contacts-per-won-deal versus contacts-per-lost-deal. Pull the last fifty closed opportunities, count distinct contacts with at least one logged activity, and split by outcome. Almost every team finds the won deals carry meaningfully more threads. Once you know your own delta, the coaching question becomes concrete: "Our won deals average X contacts. This one has two. What's the plan to get to X?"

Title depth of highest-ranked contact engaged. Tag every opportunity with the seniority tier of the most senior person who has actually attended a meeting — not been CC'd. Compare win rates across tiers. This is usually the single most predictive field a RevOps team can add, and it takes an afternoon.

Days-since-last-executive-touch. A rolling counter on every open opportunity above a dollar threshold. When it crosses your stage-length norm, the deal flags automatically. This turns a coaching question into a system prompt rather than something dependent on a manager remembering to ask.

Stage-to-stage slip rate by threading depth. Single-threaded deals slip more. Quantify by how much for your business and the argument stops being philosophical.

Verified-authority coverage. Percentage of committed pipeline where the economic-buyer field is populated *and* someone has met that person. Most teams discover this number is under half the first time they measure it, which is a far more useful thing to discuss on a forecast call than a probability slider.

Set thresholds from your own distribution rather than from a blog. If your median won deal has four engaged contacts and one director-plus meeting by the proposal stage, then a proposal-stage deal with one contact and no director meeting is your definition of at-risk. Write that definition down, put it in the stage exit criteria, and the reflection question becomes a checklist item instead of an act of managerial courage.

Where these questions cost more than they return

Reflection questions are not free, and treating them as universally good produces its own failure mode.

Small, fast, self-serve deals. If the average contract is a few thousand dollars and the buyer genuinely has a card and authority, a full authority audit is theater. The cost of asking — call time, rep cognitive load, a slower cycle — exceeds the value of the information. Scope the practice by deal size, and say so explicitly, or reps will correctly conclude the process is bureaucratic and quietly stop.

Deals where the gap is known and unfixable this quarter. Sometimes the economic buyer is genuinely unreachable until a budget cycle opens. Asking the question a fourth time does not change the answer; it just teaches the rep that the ritual is performative. Better to move the close date, drop the forecast category, and set a calendar trigger for the cycle.

Public forums. These questions expose gaps, and exposing gaps in front of peers converts a diagnostic into a status threat. Run them one-to-one or in a small deal-review with an explicit norm that finding gaps is the point. Once a rep believes the question is a trap, they will pre-sanitize their CRM, which destroys the data quality the whole system depends on.

Over-frequency. The same question at every stage gate becomes noise the rep learns to answer on autopilot. Rotate the bank.

The alternatives are worth weighing honestly. A structured qualification framework — MEDDPICC, MEDDIC, or a homegrown variant — gives you consistency and a shared vocabulary, at the cost of turning into a form-filling exercise that reps complete after the call from memory. Automated CRM validation rules that block stage advancement without a populated economic buyer are cheap and never forget, but they produce garbage input the moment reps learn which field to fake. Conversation-intelligence tooling that scans call transcripts for authority language scales to every call without manager time, but flags correlation rather than fact — a contact can say "budget" constantly and still hold no purse. Manager-led reflection questions cost real calendar time and depend on manager skill, which is unevenly distributed, but they are the only option that changes what the rep *thinks* rather than what the rep *records*.

The workable combination is layered: automation flags, framework structures, questions change behavior. Skipping the third layer is why so many teams have immaculate CRM hygiene and the same single-threading problem they had two years ago.

The pitfalls that quietly undo the whole practice

Confusing responsiveness with authority. The most dangerous contact in any pipeline is the one who answers fast. Responsiveness feels like progress, and it is genuinely correlated with interest — but people with real budget authority are usually the hardest to reach, precisely because they are the ones with a full calendar. Reps optimize for the pleasant conversation. The coaching question that counters it: "Who at this account has been hardest to get time with, and what does that tell you?"

Treating the champion as the enemy. The reflex after discovering an authority gap is to go around the contact. That burns the one asset the rep has. The better move is to make the champion the vehicle: "What would make you comfortable introducing me to your CFO?" or "What does your VP need to see before this gets funded — can we build that together?" Champions almost always know the path and will walk it with you if the ask is framed as helping them win internally rather than bypassing them.

Asking too late. An authority audit at the negotiation stage is a post-mortem with extra steps. By then the rep has burned a quarter and pivoting means restarting discovery with a stranger. Put the authority question at the *first* stage gate after discovery, when the cost of a wrong answer is a week rather than a quarter.

Accepting hearsay as verification. "My contact says they can approve it" is a claim from the person with the strongest incentive to overstate their own influence — nobody enjoys admitting they need permission. Verification means a second source: a prior-purchase precedent, a procurement policy, or the approver saying it themselves.

Letting the answer die in conversation. Reflection without a written next step evaporates by the next call. Every one of these conversations should end with a name, a channel, and a date. "I'll try to get higher" is not a plan; "I'll ask my champion on Thursday's call to introduce me to the VP of Finance, and if that stalls by the 15th I'll go direct via the CFO's exec assistant" is.

Manager asymmetry. If one manager runs this discipline and three do not, RevOps gets inconsistent data and reps get inconsistent standards. Make the question set part of the deal-review template, not a personal habit.

Punishing the honest answer. The fastest way to kill the entire practice: a rep admits the authority gap, and the response is a public downgrade and a lecture. Do that once and every rep on the team learns that the safe answer is "yes, I've got the decision-maker." The whole system depends on the honest answer being cheaper than the false one — which is a management choice, not a process design.

Related questions

What if the rep genuinely cannot get above their champion?

Then the champion becomes the project. Arm them with a one-page internal business case in their CFO's language, ask what objection they expect, and rehearse it. If three attempts over a full cycle produce nothing, the honest move is to downgrade the forecast rather than keep committing it.

How is this different for renewals and expansions?

Authority often shifts on renewal — the original buyer may have moved on, and the budget may have consolidated under a different function. Ask "who owns this line item now versus when we signed?" Existing-customer deals fail on stale stakeholder maps more often than on product dissatisfaction.

Should this question live in the CRM as a required field?

Populate a field, but do not rely on it alone. Required fields get filled with whatever unblocks the save. Pair the field with a verification flag — "has anyone met this person?" — and audit a sample monthly against calendar data.

Does the same approach work in a founder-led sale?

Yes, and it matters more, because founders over-index on rapport with whoever is most enthusiastic. The precedent question — "how did you buy the last tool like this?" — is the single highest-yield one to carry into founder-led deals.

How do you ask this without sounding like an interrogation?

Frame it as building the plan together: "Let's map who has to say yes so we can sequence it." Shared-artifact language turns an audit into planning, and you get the same information.

FAQ

What is the single best question to ask a salesperson about decision-makers?

"If your contact said yes today, what could they approve on their own, and who signs above that?" It forces a number and a name in one answer, and it is answerable in a sentence when the rep knows and impossible to fake when they do not.

How do I handle a rep who insists the champion is the decision-maker?

Do not argue the title. Ask for precedent: "What's the largest purchase they've personally signed, and how do you know?" If the source is the champion's own claim, the follow-up is "how would we verify that without making it awkward?" — which turns the disagreement into a shared task.

Can automated tools identify the right decision-maker for us?

They can surface strong signals — org data, engagement patterns, which titles appear on calls — and they are excellent at flagging deals with thin stakeholder coverage. What they cannot do is confirm authority; that requires a human asking a direct question. Use tooling to decide which deals to examine, not to conclude the examination.

What if the economic buyer refuses to meet?

Treat the refusal as data. Sometimes it means the deal is not a priority; sometimes the champion has not framed it in terms worth the executive's time. Ask the champion what would make the meeting valuable to their boss, and rebuild the ask around that. Persistent refusal on a large deal is a forecast signal, not an access problem.

How often should this be asked on a given deal?

At each stage gate, with a rotated question, plus any time the deal size, close date, or primary contact changes materially. Weekly repetition on a long-cycle deal produces autopilot answers and teaches reps the ritual is empty.

What's the most common mistake teams make here?

Building the detection layer and skipping the conversation layer. Flags, required fields, and dashboards tell you which deals are single-threaded; only a question asked well changes what the salesperson does about it next quarter.

Sources

• https://hbr.org/2017/03/the-new-sales-imperative
• https://www.gartner.com/en/sales/insights/b2b-buying-journey
• https://www.gartner.com/en/sales/topics/sales-enablement
• https://www.salesforce.com/resources/articles/sales-qualification/
• https://blog.hubspot.com/sales/sales-qualification
• https://www.challengerinc.com/blog/
• https://hbr.org/2012/07/the-end-of-solution-sales
• https://www.mindtools.com/a5xu9y3/spin-selling

Related on PULSE

• [Can you walk me through the exact steps you take to map out a decision-maker's influence map in a large enterprise?](/knowledge/cg0910)
• [How do you coach a rep to handle 'we don't have budget right now'?](/knowledge/cg0075)
• [What question reveals whether a salesperson has properly qualified a lead before entering the pipeline?](/knowledge/cg0880)
• [How do you phrase a coaching question to uncover whether a salesperson is truly listening to a prospect or just waiting to pitch?](/knowledge/cg0858)
• [Can you give an example of a reflective question that helps a salesperson realize they are over-engineering solutions?](/knowledge/cg0862)
• [Top 10 questions to evaluate a rep's use of social selling](/knowledge/cg0853)