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

To make a salesperson reflect on whether they are selling to the right decision-maker, craft a question that forces them to map the buying committee's authority, budget, and timeline against a specific deal stage, then compare that to the actual person they are engaging. In the 2027 RevOps reality—where AI copilots (like Gong’s Deal Risk Score or Clari’s Revenue Intelligence) flag stakeholder gaps, vendor consolidation shrinks the pool of viable buyers, and buying cycles stretch beyond 12 months—the right question exposes the difference between a "champion" and a "decision-maker." The goal is to trigger a MEDDPICC audit: if the salesperson cannot name the person with budget sign-off, the economic buyer, and the technical evaluator, they are likely selling to a gatekeeper. The question must be specific, data-backed, and tied to a concrete deal outcome, not a generic "who is the decision-maker?"

The Anatomy of a Reflection-Triggering Question

A question that works in 2027 must account for the fragmented buying committee that Gartner reports now averages 11–16 stakeholders. The old "Who signs the check?" is insufficient. Instead, use a three-layer framework:

1. Authority Layer: "Who on your contact list has the budget authority to approve a deal of this size, and what is their specific MEDDPICC metric for economic buyer?"
2. Access Layer: "How many of the 11–16 stakeholders in this buying committee have you met with, and which ones are blocking access to the CFO?"
3. AI Validation Layer: "What does your Gong Deal Board or Clari Forecast say about the stakeholder coverage for this deal—are there any red flags on authority?"

This forces the salesperson to stop relying on a single champion and instead triangulate the decision-making structure. For example, if the Salesforce opportunity record shows only one contact, but the Clari AI predicts a 30% close probability due to missing executive engagement, the question becomes: "Why are you investing time here when the AI says you lack the authority stakeholder?"

The 2027 Buying Committee Complexity

In 2027, the buying committee is not just larger—it is algorithmically influenced. AI tools like Outreach’s Smart Sequence and Salesloft’s Cadence AI now score stakeholder engagement based on email opens, meeting attendance, and LinkedIn interactions. A salesperson might think they have the right contact because that person is responsive, but the AI reveals they are a technical evaluator with no budget authority.

Real numbers from Gong Labs (2026 data): Deals where the salesperson engaged the economic buyer before the demo stage close at 68% rate, compared to 22% when they only spoke to a champion. The reflection question must surface this gap: "According to your Gong call transcripts, how many conversations have you had with someone who used the word 'budget' or 'approval' in the last three meetings?"

If the answer is zero, the salesperson is selling to the wrong person.

How to Frame the Question Using MEDDPICC

The MEDDPICC framework (Metrics, Economic Buyer, Decision Criteria, Decision Process, Paper Process, Identify Pain, Champion, Competition) is the gold standard for 2027 RevOps. To make a salesperson reflect, ask a question that forces them to fill in the "Economic Buyer" and "Decision Process" fields with specific names and timelines.

Example question: "In your MEDDPICC notes for this deal, who is the Economic Buyer, and what is their specific decision process timeline? If you cannot name the person and the exact date they will make a decision, you are selling to a gatekeeper."

This works because it ties the abstract concept of "right decision-maker" to a tangible output—a named person with a deadline. If the salesperson hesitates, they know they have a gap.

Decision Tree: Is This the Right Decision-Maker?

The following decision tree helps a salesperson self-diagnose whether they are engaging the correct stakeholder. It uses real branching logic based on common 2027 deal scenarios.

This tree forces the salesperson to audit their own process in real time. If they land on "Stop selling" or "Escalate to VP," they have a clear reflection point.

The AI Feedback Loop: Using Tools to Validate

In 2027, no reflection question is complete without AI-driven validation. Tools like Clari Revenue Intelligence and Gong provide automated stakeholder maps. The question should leverage these: "What does your Clari stakeholder map show for this deal? Does it list the CFO or VP of Sales as a key contact?"

If the AI map shows a missing stakeholder, the salesperson must reflect on why they ignored the data. Forrester’s 2026 report found that teams using AI stakeholder mapping improved deal close rates by 34%. The question becomes a performance audit: "Why are you not using the AI insights your company paid for?"

The Process Loop for Continuous Reflection

The reflection should not be a one-time question. It must be part of a monthly cadence where the salesperson revisits their stakeholder map. The following loop shows how to embed this into RevOps workflows.

This loop ensures that every month, the salesperson reflects on whether they are selling to the right person. If the AI sentiment turns negative, they must ask: "Why did the economic buyer disengage?" That is the reflection trigger.

Real-World Example: A SaaS Deal Gone Wrong

Consider a $500k deal for a Salesforce competitor. The salesperson has been talking to a Director of Sales Ops for three months. The Gong transcript shows the director never mentioned budget, never asked about pricing, and never used the word "approval." The Clari forecast shows a 15% probability.

The reflection question: "Your Clari says this deal has a 15% chance. Your Gong shows zero budget conversations. Who is the actual decision-maker here, and why are you still talking to the Director?"

The salesperson realizes they are selling to a technical evaluator who will never sign. They pivot to the VP of Sales, close the deal in two weeks. The question saved 90 days of wasted effort.

Common Pitfalls in Decision-Maker Identification

• Confusing champion with decision-maker: A champion can advocate but cannot approve. The question must separate the two.
• Relying on a single contact: In 2027, buying committees are large. The question should ask for a list, not a name.
• Ignoring AI warnings: If Gong flags a stakeholder gap, the salesperson must reflect on why they ignored it.
• Not updating CRM: If the Salesforce record still shows the wrong contact, the question should force a data update.