Most sellers grew up on BANT. Most enterprise teams have moved on to MEDDIC. The reason is not that BANT is broken. It is that BANT was built for a different kind of deal.
This post covers what each framework actually asks, where the lines blur, and which one fits the kind of opportunities your team is working today.
BANT in one line
BANT stands for Budget, Authority, Need, Timing. It was created at IBM in the 1960s as a fast way for reps to disqualify weak leads early. Each letter is a yes or no gate. If a prospect has all four, the lead is qualified. If any one is missing, the rep moves on.
The framework was built for transactional, single decision maker sales. Hardware, software licenses, services with a known price and a clear buyer. It is light, easy to teach, and easy to score in a CRM.
MEDDIC in one line
MEDDIC stands for Metrics, Economic Buyer, Decision Criteria, Decision Process, Identify Pain, Champion. It was developed at PTC in the early 1990s for complex enterprise software deals. Read the full MEDDIC sales process breakdown for the field-level detail.
MEDDIC does not just ask whether a deal can close. It asks how the deal will close, who has to sign, what they will measure you against, and who inside the account will fight for you. It is heavier to fill out and harder to fake.
How they differ
| Dimension | BANT | MEDDIC |
|---|---|---|
| Origin | IBM, 1960s | PTC, early 1990s |
| Built for | Transactional, single buyer | Complex, multi stakeholder |
| Letters | 4 | 6 |
| Qualifies | Lead viability | Deal winnability |
| Stakeholders | One (Authority) | Multiple (Economic Buyer, Champion, plus committee) |
| Discovery depth | Surface | Deep |
| Time to complete | Minutes | Hours across multiple calls |
| Best fit ACV | Under 25k | 100k and up |
| Common owner | SDR or AE | AE plus deal team |
The biggest practical gap is the stakeholder count. BANT assumes one person can say yes. MEDDIC assumes a buying committee and forces the rep to map every member.
When to use BANT
BANT still works in narrow cases. Reach for it when:
- The deal is one decision maker with clear signing authority.
- The product is well understood and the buyer is comparing on price and timing, not on outcomes.
- ACV is small enough that long discovery would cost more than the deal is worth.
- The sales motion is high velocity and reps need a quick gate to triage inbound.
- You are coaching brand new SDRs who are still learning to ask basic qualifying questions.
For SMB inbound funnels and product led sales motions where the AE only enters at the end, BANT is often enough. It is also the right tool for renewals where the relationship is established and the question is really just timing.
When to use MEDDIC
MEDDIC is the right call when:
- The ACV is six figures or more and a procurement team will get involved.
- More than three people influence the decision.
- The buyer wants a business case, not a feature list.
- Sales cycles run 90 days or longer.
- You are losing winnable deals to no decision rather than to competitors.
MEDDIC is also the framework that most CROs reach for when forecast accuracy is bad. The Metrics and Decision Process letters are the ones that surface slipping deals before the slip becomes a missed quarter.
Where they overlap
The overlap is real and worth naming. BANT's Need is a thinner version of MEDDIC's Identify Pain. BANT's Authority is a thinner version of Economic Buyer. BANT's Budget maps loosely to Metrics, and Timing maps loosely to Decision Process.
You can think of MEDDIC as BANT plus the parts BANT skips. MEDDIC adds Decision Criteria (what they will compare you on), Champion (who sells you internally), and a much sharper version of process.
A team running BANT today can move to MEDDIC by adding three questions to discovery: what business metric are you trying to move, who else has to approve this, and who inside your company is going to drive this through. Those three questions cover most of the gap.
The bottom line
BANT is fine for transactional inbound. MEDDIC is required for enterprise. If your deals have more than three stakeholders, a procurement step, or a six figure price tag, BANT will let bad deals into your forecast. If you are running high velocity SMB, MEDDIC is overkill.
Pick the framework that matches the deal, not the framework you were trained on. Many enterprise teams now run MEDDPICC, the extended version, to handle paper process and competitive pressure on top of MEDDIC.
Related reading
Bring this into Salesforce with CRUSH
A qualification framework is only useful if the answers live where the deal lives. CRUSH lets your team capture Economic Buyer, Champion, Metrics, and Decision Process directly on the account and opportunity in Salesforce, then ties those fields into the relationship map and account plan.
We built CRUSH so that MEDDIC and MEDDPICC stop being a checklist and start being how the team actually runs the deal.
