Sales
MEDDPICC, MEDDIC or BANT: Choose a Sales Qualification Framework
Compare MEDDPICC, MEDDIC and BANT with an original opportunity worksheet that separates verified evidence from sales assumptions.
What you will learn
- Explain the questions covered by MEDDPICC, MEDDIC and BANT.
- Choose an appropriate level of qualification for a buying situation.
- Turn missing evidence into a useful next question.
Choose a sales qualification framework by the buying uncertainty you need to resolve. BANT offers a compact view of budget, authority, need and timing. MEDDIC and MEDDPICC give teams a more detailed way to examine value and the buying process. None of them turns an unverified assumption into a qualified opportunity.
What do MEDDPICC, MEDDIC and BANT mean?
MEDDICC's methodology guide describes MEDDIC as Metrics, Economic Buyer, Decision Criteria, Decision Process, Identify Pain and Champion. MEDDICC adds Competition. MEDDPICC adds Paper Process and uses Implicate the Pain. Spell out the version your team uses rather than assuming the letters mean the same thing everywhere.
| MEDDPICC area | Practical question |
|---|---|
| Metrics | Which buyer-relevant measure could demonstrate value? |
| Economic buyer | Who has overall buying authority? |
| Decision criteria | Against which requirements will options be judged? |
| Decision process | Which steps and people determine the choice? |
| Paper process | What approved procurement or signature steps follow the choice? |
| Implicate the pain | What consequences does the buyer connect to the problem? |
| Champion | Who has influence, credibility and a reason to support the change? |
| Competition | Which alternatives compete for the same resources? |
For BANT, Microsoft's qualification documentation defines Budget, Authority, Need and Timeline. Use that definition separately from any vendor's scoring rules or automated lead ratings.
Choose the framework that answers the buying question
A small, well-understood purchase may need a brief BANT check and a clear next step. An enterprise purchase involving operating teams, a budget owner and procurement may justify more explicit decision and paper-process mapping. The distinction is not “good framework versus bad framework.” It is enough relevant evidence versus an unnecessarily heavy checklist.
Use a consistent three-state annotation beside each answer: confirmed, working assumption or unknown. Add a source, date and next question. “Budget approved” should mean someone with the relevant authority confirmed a budget, not that a contact liked the demo.
Qualification supports discovery rather than replacing it. A conversation should still follow what the customer is trying to accomplish, not the order of an acronym.
Worked example: the same fictional opportunity, two views
A fictional reporting-software buyer says its operations team struggles to reconcile project updates. The team lead wants a demo this month. The seller has not spoken to the budget owner.
| Recorded evidence | BANT view | MEDDPICC view and next question |
|---|---|---|
| Team lead describes reconciliation work | Need partly understood | Pain recorded; ask who is affected and which baseline is available. |
| Demo requested this month | Timing for a demo, not a purchase | Decision process unknown; ask what the demo must establish. |
| No approved spending record | Budget unknown | Economic buyer and funding path unknown; ask how purchases of this type are approved. |
| Team lead offers to invite a colleague | Useful stakeholder access | Champion status unproven; learn their influence and reason to support a change. |
The appropriate next step is a bounded discovery or evaluation conversation, not a confident close forecast. The additional detail changes the questions you ask, not the facts you already have.
Copyable AI prompt
Try this with Aurora AI in Finta, Codex, or Claude. Use only material you are authorized to share, and review the draft before using it.
Review [authorized opportunity notes] with [chosen qualification framework]. Return each framework area, confirmed evidence with source/date, assumptions, unknowns and one useful next question. Distinguish a requested demo from purchase timing and a friendly contact from buying authority. Do not assign an unsupported score or forecast. Draft for a seller to review; do not contact anyone or change CRM records.Avoid checklist theater
Do not turn every blank into a made-up answer so that the opportunity looks complete. Do not treat a friendly contact as the economic buyer, a requested demonstration as purchase timing, or a seller-estimated benefit as a customer-approved metric.
Review the framework when evidence changes. Save the corrected answer and its source rather than silently overwriting the history. For a practical starting point, use Finta's sales discovery guide, buying-committee workflow and Sales Account Planner to explore the next preparation step.