Strong discovery is not a warm-up for the demo. It is where a rep determines whether the opportunity has enough business impact, executive support, and decision clarity to deserve the next 90 days. If those conditions are missing, a polished presentation only makes a weak deal look healthier than it is.
MEDDIC discovery questions help sales reps test whether a deal is real, winnable. And worth pursuing by connecting measurable outcomes to the buyer's pain, authority, requirements, approval path, and internal advocacy.
That standard changes the rep's job from collecting agreeable answers to building a verifiable deal picture. The framework below breaks each component into practical questions, signals to listen for, and diagnostics that expose stalled opportunities before they reach procurement. Start with why this discipline matters.
Let's Meet! to see how a sharper MEDDIC discovery call can save weeks on every qualified deal.
Why MEDDIC Discovery Questions Decide the Deal Before You Ever Present
Discovery is not the polite opening before the real sales conversation. It is where the deal is qualified, shaped, or quietly lost. The first call establishes future leverage, forecast credibility, and the path to the Economic Buyer. Research on MEDDIC discovery notes that much of this is decided in the first 30 minutes of the first real call.
That changes the outcome you should pursue. A buyer feeling heard is valuable, but it is not a qualification result. By the end of a disciplined call, you should know whether the opportunity is real and whether it deserves continued investment. If the evidence is missing, disqualify the deal. MEDDIC exists to prevent "happy ears" opportunities from surviving until procurement exposes the gaps.
Discovery is a qualification test, not a demo with questions
Many AEs reverse the sequence. They open the product, add a few questions between features, and call it discovery. That is a product demo with questions sprinkled on top. It lets the seller explain before understanding the business problem. The prospect may like the presentation while the opportunity stays commercially undefined. This pattern is associated with deals that stall late.
Use the call to test the deal's structure. Ask what prompted the change, how the problem is measured, who owns the business outcome, and what must happen internally before a signature. Listen for specifics, not agreeable language. "This is a priority" is a claim to examine. Which metric is off? Who is accountable?
Talk less, inspect more
The seller's job is not to fill every pause. Stalled deals repeatedly trace back to discovery calls where the AE talked more than the prospect. Let the buyer explain the operating reality in their own terms, then test the answer with precise follow-up questions. Summarize only to confirm the evidence and identify what is still unknown.
This is how we approach DISCOVERY in real calls through RevCentric's Sellers Teaching Sellers model. The MEDDIC sales methodology is not a script to perform. It is a way to inspect whether the opportunity can advance. A strong presentation then becomes a response to verified priorities, rather than an attempt to manufacture urgency after the fact.
Metrics: Questions That Ground the Deal in Operating Reality
Metrics are where discovery stops being a discussion about interest and becomes a test of business value. A prospect may agree that a problem matters, but agreement is not qualification. You need to understand how the organization measures the problem, what outcome would count as a win, and whether that outcome is important enough to change priorities.
Quantify Before You Qualify
Ask questions that force the conversation toward the numbers already used to run the business:
- What are you and your team measured on this year?
- What would a real win look like by the end of the year?
- How is the current problem measured today?
- Which existing KPIs should this solution influence?
- What business impact do you expect if the problem is solved?
- What is the current benchmark, and what would need to change for the investment to be considered successful?
Do not accept "improve efficiency" as the finished answer. Follow up with, "Which metric would move?" and "From what baseline to what target?" If the buyer cannot answer. Identify who owns that number and bring them into the next conversation. A useful Metrics answer contains two or three numbers a board would recognize, observable, owned, and connected to an operating decision.
Separate the current state from the expected impact. A symptom sounds like "we lose deals late." Impact sounds like "our win rate falls from 32% to 18% after security review. Costing roughly $2 million a year." Those examples give the team something to investigate and the buyer something to defend. If the prospect has no baseline, mark the gap rather than inventing precision.
This discipline matters when technology is part of the answer. Sales organizations invest in technology to transform sales processes and improve revenue growth. But the investment only has strategic weight when the outcome is defined in the organization's own measures (academic research on sales technology and revenue outcomes).
How to Surface the Economic Buyer: Questions That Reveal Budget Authority and Sign-Off
The person who feels the problem is not automatically the person who can fund its resolution. A day-to-day contact may understand the operational impact and still lack the authority to approve an investment. Treating that contact as the economic buyer creates a late-stage surprise when someone with budget authority sees the deal for the first time.
In MEDDIC, the Economic Buyer is the person with authority to authorize the investment, or the person who can give final approval. The question sequence below moves you from the working-level problem to the person who controls the decision without making your contact feel bypassed. The point is not to ask, "Who is the economic buyer?" and wait for a name.
Use the questions in sequence
- Start with ownership of the outcome. Ask, "Who owns the business outcome this project is meant to improve?" Then clarify what that person is accountable for and how the result will be judged. If the project affects pipeline conversion, implementation speed, retention, or another operating outcome, identify the executive responsible for that result. This distinguishes the person experiencing the pain from the person answerable for solving it.
- Trace the budget. Ask who holds the budget for this category of investment. Then ask whether the budget sits with the function experiencing the problem or with a separate executive. The answer may expose a shared budget or a central procurement pool. MEDDIC Economic Buyer questions should establish budget authority and who must authorize the investment (source guidance on Economic Buyer discovery).
- Find the trigger for formal sign-off. Ask, "What has to be true for this investment to receive formal approval?" Probe for the business case. Threshold, forecast, or executive review that turns interest into an approvable request. Ask what evidence the approving leader expects and when it must be ready.
- Confirm every approval before money moves. Ask, "Who must approve this before funds can be committed?" Then test the answer. "Whose approval could still stop the project?" Map the final approver separately from legal. Security, and procurement. They may influence the route without owning the economic decision.
Do not postpone this conversation until the proposal is complete. If you do not help establish the economics early, the prospect will set them for you, often by reducing the discussion to price (why economics must be set early). By the end of the sequence, you should know who owns the outcome and who controls the budget.
Decision Criteria: Questions That Map the Formal and Informal Requirements
Decision Criteria is where a buyer's stated evaluation process meets the requirements that may never appear in an RFP. MEDDIC discovery questions should uncover both. If you only respond to the published scorecard, you may satisfy the procurement checklist while missing the concerns that determine who gets confidence, access, and ultimately the signature.
Start by establishing how the organization will define a successful solution. Requirements definition starts with the goals, needs, and objectives of the end product. Undocumented requirements create ambiguity, which gives every stakeholder permission to change the standard late in the deal.
Separate the scorecard from the real buying standard
Use questions that make the evaluation concrete:
- What formal requirements will the evaluation use: an RFP, vendor scorecard, technical checklist, or a defined set of must-haves?
- Which requirements are absolute, and which are preferences the team can trade off?
- How will each vendor be scored, and who owns the scoring process?
- What would cause a vendor to be removed from consideration before the final presentation?
- When the shortlist is narrowed, what evidence will separate the remaining options?
Then ask what the formal process does not capture. "What matters to the team that will not appear in the scorecard?" often surfaces implementation risk. Executive confidence, prior vendor experience, internal politics, or a stakeholder's preference for a particular approach. Follow with, "Who is most concerned about that issue, and what would they need to see to support a decision?"
Map the evaluation team individually rather than treating it as a single buyer. Ask who participates, what each person is accountable for, and how each person will define a good outcome. A security leader may prioritize control and risk, while an operations leader may care about adoption and workflow. If you cannot explain each evaluator's criteria, you do not yet understand the decision.
Finally, test the negative case. Ask what has disqualified vendors in the past and what concern could stop this project even with a strong business case. Record the answers and confirm them with the buyer. When requirements remain informal, deals often look healthy until a late-stage stakeholder raises a criterion no one prepared to address.
Decision Process: Questions That Map the Path to Signature
The decision process is the buyer's real, lived path from today's conversation to a signed agreement. It is not the sequence in your sales process, and it is rarely captured completely in a procurement checklist. MEDDIC treats it as a specific discovery responsibility: map the internal steps, approvals, stakeholders, and timeline that stand between the current stage and signature.
Start by asking the buyer to describe what happens next in their own organization:
- What are the internal steps between where we are today and a purchase decision?
- What meeting, review, or business case comes next?
- Which approvals are required, and in what order?
- Who influences each approval or decision gate?
- What does each person need to see or believe before they support moving forward?
Do not accept "we just need leadership approval" as a complete answer. Ask which leader, what approval means in practice, how that person evaluates the investment, and whether the buyer has worked through this process before. The goal is not to interrogate the prospect. It is to replace assumptions with a shared operating map.
Trace the timeline backward from the required outcome
Once the gates are visible, work backward from the date the buyer says they need the solution in place. Ask:
- What is the target date for a signed agreement?
- What has to be completed before procurement gets involved?
- When do legal, security, finance, or executive reviews enter the process?
- How long does each review normally take?
- What could push the timeline, and what would you do if that happens?
That last question exposes whether the date is a business requirement or an optimistic estimate. It also surfaces dependencies that may not appear on the formal plan. A security review may require technical validation first. Finance may need a quantified business case. Each dependency creates a potential stall point, and each needs an owner and a next action.
Document the process with the buyer, then test it in the next conversation: "We believe the path is validation, security review, finance approval, executive sign-off, and procurement. What have we missed?" Their correction is valuable. It tells you which steps are real, which are assumed, and who actually controls progress. For a deeper reference, see this guide to the MEDDIC decision process.
A strong map also tells you when to stop selling. If no one can name the approvals, stakeholders, or required business event, the opportunity may not have a decision process yet. Qualify that gap openly instead of treating a friendly meeting or requested demo as evidence that a deal is advancing.
Identify Pain: Questions That Reveal the Measurable Cost of the Status Quo
Prospects rarely begin with a business case. They begin with symptoms: missed targets, slow handoffs, unreliable forecasts, or a team compensating for a broken process. Your job is to connect the visible problem to the operational and financial cost of leaving it in place. Identify Pain means uncovering the why behind the initiative and the cost of inaction.
Move from frustration to consequence
Start with the current condition, then keep narrowing until the buyer can describe its effect in measurable terms. Questions that help include:
- How is this problem showing up in the team today? Which workflows, deals, or customers are affected?
- What has this already cost the business this quarter or year in lost revenue, delayed revenue, staff time, or additional headcount?
- How many people are involved in managing the problem, and what higher-value work are they unable to complete?
- Which target does this put at risk, and how will leadership recognize the impact?
- If nothing changes by the end of the year, what is the likely operational or financial outcome?
Do not accept an answer such as "it is inefficient" and move on. Ask how the buyer knows, what baseline they use, and which number would change if the problem were solved. If the buyer cannot quantify the impact, document that gap rather than manufacturing precision.
Timing is equally important. Ask, "Why does this need to change now?" Then follow up with, "What changed?" A new executive mandate. Missed forecast, product launch, hiring plan, acquisition, or customer escalation can turn a persistent issue into an active initiative. Without a compelling reason for action, even serious pain can remain a budgetless priority.
Finally, identify who experiences the pain most directly and how it affects their targets. The person describing the problem may feel the daily burden, while a revenue leader owns the missed number and finance owns the economic exposure. Ask, "Who is carrying the consequence today?" and "Whose goals are affected if this continues?"
For a deeper framework and follow-up prompts, use this MEDDIC pain discovery guide. A well-qualified pain statement should make the cost of waiting visible, establish why the initiative exists. And give the buyer language to defend action when you are not in the room.
Champion: Questions That Test Whether Your Internal Advocate Can Really Sell
A friendly contact is not automatically a Champion. In MEDDIC, a Champion is an internal advocate with enough influence to sell on your behalf when you are not in the room. That means your contact must do more than attend meetings, share documents, or praise your solution. They must be willing and able to create movement inside the account.
Test that distinction directly. You are not interrogating the buyer. You are finding out whether this person can help you win, or whether you are mistaking access for influence.
Questions that separate an ally from a Champion
- Advocacy history. Have you advocated for a vendor or internal initiative like this before, and how did it go? Their example shows whether they can navigate resistance and follow through.
- Relationship to the economic buyer. How do you work with the economic buyer on decisions like this? Listen for the nature of the relationship, not merely a name. Can this person get the budget owner's attention, or do they only know the buyer by reporting line?
- Access to the decision team. Would you be comfortable putting us in front of the decision team, and what would need to happen first? A Champion may need help preparing, but should be able to explain the path to it. Evasion or indefinite timing are qualification signals.
- Stakeholder concerns. What objections are you hearing from finance, security, or operations? An effective advocate surfaces concerns you cannot hear directly. "Everyone likes it" is not insight.
- Personal stake. If this project succeeds, what changes for you personally or for your team? A Champion needs a meaningful reason to spend political capital, such as a strategic objective or a painful operational problem they are accountable for.
Use these questions during the call, then assign a testable next action. Ask the contact to arrange a meeting, validate a business case with the economic buyer, or return with the stakeholder objections by a defined date. Make the action proportional to the stage of the deal, but make it observable.
Do not accept "I will champion this internally" as proof. Ask what they will say, to whom, and by when. After the call, check whether the promised action occurred. A contact who cannot or will not create access may still be useful, but should not carry the Champion qualification in your forecast.
For a deeper framework on how to identify and test a MEDDIC champion, examine the advocate's influence, access, credibility, and willingness as separate evidence points. The goal is not to label the most enthusiastic person in the account. It is to verify who can move the decision when your team is absent.
Competition and the MEDDPICC Variant: Questions That Close the Back End of the Deal
MEDDPICC extends the MEDDIC spine with two areas that often decide whether a qualified opportunity reaches signature: Paper Process and Competition. Paper Process covers procurement and legal workflow. Competition covers the alternatives shaping the buyer's decision, including the incumbent or no change. A deal can have real pain, a capable champion, and a compelling business case, yet still stall when someone asks how the contract gets approved.
Expose the competitive decision before the buyer does
Do not wait for a competitor's name to appear in a late-stage evaluation. Ask questions that reveal the buyer's reference point and the internal preference behind it:
- Who else are you evaluating, and what role will each option play in the decision?
- What is the incumbent doing well enough that your team would hesitate to change?
- What would make you switch from the current approach?
- Who on your team prefers the current solution, and why?
- If every option met the stated requirements, what would separate the winner?
The answers tell you whether the competition is a named vendor, a comfortable status quo, or an unspoken stakeholder preference. They also give your champion material to address internally. If the buyer cannot explain how the decision will be made or what could change it, the opportunity may not be as advanced as its stage suggests.
Map the paper process while there is still time to influence it
Paper Process questions should identify the route from commercial agreement to an executable contract, not simply confirm that procurement exists. Ask:
- What does procurement require before it can issue or approve a purchase order?
- Which legal review applies, and who owns security, privacy, or risk approval?
- What contract terms matter most to your legal or procurement team?
- Are there approved vendors, purchasing thresholds, or preferred templates we need to work within?
- What has caused similar agreements to stall after the business decision was made?
Then convert the answers into named steps, owners, dependencies, and dates. A verbal commitment is not a paper process. If no one can identify the next approval or the person responsible for it. Treat that gap as a qualification issue and build an advance plan before investing more selling time.
This is where MEDDIC differs from BANT. BANT checks basic budget and authority. MEDDIC inspects how the buyer will decide, who can change the outcome, and whether the path to signature is real. The framework's qualification distinctions and MEDDPICC's added coverage are useful references. Some teams spell the variant MEDDICC, but the principle is the same: inspect the back end before it becomes a surprise.
Build Your Own MEDDIC Discovery Question Checklist
A useful checklist should help a rep test deal quality, not simply collect answers. Use these prompts to prepare, guide the call, and identify the evidence still missing before advancing the opportunity.
| MEDDIC Component | What You Are Testing | One Signature Question |
|---|---|---|
| Metrics | A measurable business outcome leadership would recognize | Which metric would move, and from what baseline to what target? |
| Economic Buyer | A person with authority to approve the investment | Who must approve before funds can be committed? |
| Decision Criteria | Formal and informal requirements behind the choice | Which requirements will not appear in the scorecard? |
| Decision Process | The real steps, approvals, and timeline to signature | What happens next in your organization, and who approves it? |
| Identify Pain | The measurable cost of the status quo | What does this problem cost if nothing changes this year? |
| Champion | An advocate with influence who sells when you are absent | What will you say, to whom, and by when? |
- Metrics: What business outcome is the team measured on? What is the current baseline? What would a meaningful improvement look like in a number the board or executive team recognizes? Capture two or three measurable outcomes, not a collection of positive-sounding benefits.
- Economic Buyer: Who owns the budget for this initiative? Who has final authority to approve the investment? What does that person need to see before signing off, and how will we earn direct access to them?
- Decision Criteria: Which formal requirements will be scored or documented? Which informal requirements will influence the decision even if they do not appear in the RFP? Who defines the criteria, and how will the team compare competing options?
- Decision Process: What steps must occur from this conversation to signature? Which people or committees approve each step? What is the target decision date, and what could move it? Confirm the sequence rather than accepting a vague statement that the project is a priority.
- Identify Pain: What is the operational or financial cost of the current situation? Who experiences that cost, and how is it measured? Why does the problem need to change now? If nothing changes this quarter or year, what does the business lose?
- Champion: Who has the influence to move this internally? Will this person coach us on the account, give us access to stakeholders, and sell our case when we are not in the room? Test willingness with a specific request, such as arranging an executive meeting or reviewing the internal business case.
- Competition and Paper Process: What alternatives are being considered, including doing nothing or keeping the current approach? What makes each option attractive? Once a decision is made, what procurement, security, legal, and contracting steps remain? These back-end details are essential when the team uses the MEDDPICC variant.
Keep the checklist in your opportunity record and mark each answer as verified, assumed, or unknown. That simple discipline makes the next action visible and prevents a promising conversation from being mistaken for a qualified deal. Teams that want reps coached live on these questions can explore MEDDIC training for tech sales with RevCentric's practitioner-led coaches.
Let's Meet! to put MEDDIC discovery into practice live with your sellers.
Frequently Asked Questions
How do you use MEDDIC discovery questions in a sales call?
Use them as a progression, not a script. Start with the operating problem, then connect it to measurable impact, the people involved, the requirements, and the path to approval. Ask an open question, listen for evidence, and follow up until you can determine whether the opportunity is real and winnable. Make unverified gaps the next action rather than assuming they are covered.
What are the key discovery questions for Metrics in MEDDIC?
Ask, "How are you measuring this today?" and "What would a meaningful improvement look like this year?" Then clarify the baseline, owner of the number, and business consequence. Strong Metrics are tied to operating reality and outcomes that leadership recognizes, not a vague promise to work more efficiently.
How can MEDDIC discovery questions identify the Economic Buyer?
Ask who owns the budget, who must authorize the investment, and whose approval is required before the team can commit. If your contact is not that person, ask how they evaluate the decision and what access or evidence the Economic Buyer will need. Treat an introduction as a deal action, not a courtesy.
What questions reveal Implied Pain in MEDDIC?
Ask what the problem is costing the organization, what happens if it remains unresolved, and why action is necessary now. Connect the answer to measurable operational or financial consequences, such as missed targets or delayed growth. Frustration establishes interest; a quantified cost of inaction establishes urgency.
Ready to Put MEDDIC Into Practice?
Strong discovery is easier to build when your team can apply the framework to real opportunities, not just memorize questions. RevCentric Partners brings a practitioner-led perspective to MEDDIC, helping sales leaders and reps turn discovery into clearer qualification and next steps. Let's Meet! to discuss where your team needs sharper execution.






















