BANT vs MEDDIC vs MEDDPICC: which qualification framework fits your deal?

How this comparison was made

Every claim on this page traces to a document one of the frameworks' own originators, or a court, published, read directly on 29 September 2026. That includes MEDDICC Ltd's own published history of MEDDIC, the federal court opinion that ruled on MEDDPICC's trademark status, HubSpot's own guide to running MEDDPICC inside a CRM, and Gartner's own 2018 report on B2B buying groups. Where a claim could not be traced to a document like that, this page says so rather than repeating what a search result implied.

Salestruct has no commercial relationship with MEDDICC Ltd, 01 Consulting LLC, IBM, HubSpot or Gartner. We qualify deals with variants of these frameworks inside client CRMs, which is the practical angle this page is written from.

Three things worth knowing before the comparison:

• BANT has no confirmed origin document. It's near-universally described as an IBM creation, and this page repeats that description because it's the consistent trade account, but nobody has produced the internal IBM material that would confirm it. That's stated plainly below rather than dressed up as sourced history.
• MEDDIC and MEDDPICC have a documented origin, and a documented legal history, because the company that now owns the MEDDIC and MEDDPICC brand names, MEDDICC Ltd, has published both and one of them has now been tested in federal court.
• "Not published" means the source doesn't say, not that we didn't look.

What does BANT actually ask?

BANT is four questions: does the prospect have a Budget, are you talking to someone with the Authority to spend it, is there a clearly articulated Need, and does the prospect have a Timeframe for solving it. A deal is traditionally treated as qualified once it clears most or all four.

It's the oldest of the three by a wide margin and the most widely attributed to IBM's sales organisation, reportedly built to give a large, dispersed sales force a repeatable way to prioritise which leads were worth a rep's time. That attribution appears consistently across sales training material, but this page could not locate an IBM-published document stating it, so the date and the internal detail should be read as trade history, not as a verified primary source.

BANT's own logic is built for a purchase that looks like a repeat order: a known budget line, one identifiable buyer, a need the prospect can already state, and a date they want it solved by. It assumes the prospect is close to a decision by the time a rep starts asking these four questions, which is precisely the assumption complex B2B buying breaks.

What does MEDDIC add, and why was it built?

MEDDIC was built inside PTC (Parametric Technology Corporation) in 1996, by Dick Dunkel, working under SVP John McMahon alongside teammate Jack Napoli. The problem wasn't abstract: PTC's sales team had grown to roughly 300 reps and was losing people faster than it could hire and train replacements. McMahon asked Dunkel and Napoli to work through the team's live and closed opportunities and answer three questions systematically: why PTC won deals, why it lost them, and why deals slipped. The pattern that held across the portfolio became six letters. PTC's sales organisation grew from $0 to $1 billion in revenue over the following decade, and MEDDICC Ltd, the company that now publishes the framework's official material, credits much of that growth to the discipline MEDDIC brought.

The six letters:

• Metrics. The quantified business outcome the deal is expected to deliver, not a generic ROI claim.
• Economic Buyer. The person who can approve the spend without asking anyone else, distinct from a champion who merely likes the product.
• Decision Criteria. The standards, technical, economic and relational, the buying committee will actually judge proposals against.
• Decision Process. The sequence of approvals the deal must clear, so a rep can tell activity apart from progress.
• Identify Pain. The specific business consequence the prospect is trying to avoid, stated in their own terms rather than the vendor's.
• Champion. An internal advocate with real influence over the decision, who has something personally to gain if the deal closes.

Where MEDDIC differs from BANT isn't the number of letters, it's the assumption underneath them. BANT assumes one buyer with a stated need. MEDDIC assumes a committee, a process with steps a rep has to name, and a pain specific enough to survive being repeated back to the prospect. That's a materially heavier qualification exercise, and it's built for a materially heavier deal.

What does MEDDPICC add on top of MEDDIC?

MEDDPICC adds two letters to MEDDIC's six: a second C for Competition (who else the prospect is evaluating, and why they might win) and a P for Paper Process (everything that happens between a verbal yes and a signature: legal review, security questionnaires, procurement sign-off). MEDDICC Ltd's federal court filing dates the addition to 2005, "built on the earlier MEDDIC acronym developed at PTC in the early 1990s." MEDDICC Ltd describes MEDDPICC as "our preferred variation" of the framework, and it's the version most enterprise sales teams mean today when they say MEDDPICC.

Paper Process is the letter that most often separates a MEDDPICC shop from a MEDDIC one in practice: deals that have cleared every technical and business hurdle routinely stall for weeks in legal or procurement, and a forecast that doesn't track that step separately can't see the risk coming until the quarter is already lost. Competition is the letter most often skipped under time pressure, and it's also the one whose absence a rep discovers latest, usually when a prospect goes dark to finish evaluating someone else.

Our companion piece walks through all eight MEDDPICC letters individually, with the specific question and CRM field for each: what MEDDPICC actually is, letter by letter.

A federal court just ruled nobody owns MEDDPICC

This is the part of the story that changed in the last five months, and it belongs in any objective comparison of these three frameworks because it settles who gets to control how MEDDPICC is taught, sold and written about.

Lahoutifard's own history with the framework goes back further than the trademark fight. Per the court's opinion, he joined PTC in 1992 after being recruited by John McMahon, and left the company in 1995 or 1996. He takes no credit for coining MEDDIC, though the opinion notes he claims some role in the iterative process that produced it. He launched MEDDIC Academy in 2017, later moved to make MEDDPICC the primary brand for that training business, and registered the trademark in September 2021. His own position, quoted in the opinion, was that "MEDDPICC functions as both a framework and a brand in my business," which is the narrower argument the case turned on: not that he invented the method, but that the term could name his training brand at the same time as it names the method itself. The court disagreed, relying in part on testimony from McMahon, the same executive who set MEDDIC in motion at PTC, that sales professionals understand MEDDPICC as a framework rather than as one company's brand.

What this means practically: no vendor can restrict who teaches MEDDPICC, writes about it, or builds software around it. Every framework compared on this page, including MEDDPICC, is free to run in any CRM, on any team, with no licence required.

BANT, MEDDIC and MEDDPICC, side by side

Where each framework breaks

Every framework fails somewhere. Stated with the same weight as what it does well:

Where BANT breaks

• It assumes a single decision-maker. Gartner's own 2017 survey found the median B2B buying group has six to 10 decision makers, which BANT has no letter for.
• "Budget" and "Timeframe" reward a prospect who is already close to a decision. By the time a lead is fully BANT-qualified, they've typically done most of their research and formed their opinions without the rep in the room.
• It has no concept of competition. A prospect can be fully BANT-qualified and still be about to sign with someone else.
• There's no step for what happens after a verbal yes. A "qualified" BANT deal can still die in procurement with no warning, because nothing in the framework tracks that stage.

Where MEDDIC breaks

• It's heavier to run than BANT, and running it badly, treating each letter as a box to check rather than a question to actually answer, produces a CRM full of confident-looking fields that nobody could defend on a call.
• Like BANT, it has no named place for competition or for the legal/procurement stage. A MEDDIC-qualified deal can still stall for weeks after the internal decision is made.
• It doesn't distinguish a deal where competition is fierce from one where you're the only vendor being seriously considered, which changes how urgently a champion needs to be built.

Where MEDDPICC breaks

• Two extra letters is two extra places for a rep to type something vague and move on. HubSpot's own MEDDPICC guide puts it plainly: it "may be overkill for transactional deals under $10 thousand," and full adoption of the framework across a team "typically takes 3 to 6 months" of training and CRM configuration.
• There's no scoring mechanism built into the acronym itself. Eight strong letters and eight weak letters look identical on a page unless a manager reads the actual notes, not just the status field.
• Its trademark history is now a matter of public record. That's not a flaw in the method, but it means any vendor claiming exclusive rights to MEDDPICC training or software after 21 April 2026 is making a claim a federal court has already rejected.

Which deal shape fits which framework?

The honest answer depends on two things: how many people have to say yes, and how much has to happen after they do.

What CRM fields does each framework actually need?

A framework that lives only in a rep's head or a slide deck isn't being run, it's being referenced. HubSpot's own MEDDPICC implementation guide is specific about what "in the CRM" means in practice: add a custom property for each letter (its example properties are "Economic Buyer Name," "Identified Pain" and "Paper Process Status"), and make the properties that matter most required before a deal can advance, so a rep literally cannot move a deal to a late pipeline stage, HubSpot's example is "Contract Sent", without a completed Paper Process field.

The same logic scales down. A BANT-run team needs, at minimum, a budget range field, a named economic contact field, a stated-need text field and a target date field, each required before a deal is marked qualified. A MEDDIC or MEDDPICC team needs one status field and one notes field per letter it runs, because the status field is what a manager scans in a pipeline review and the notes field is what makes that status defensible when someone asks why. Our CRM governance guide covers who gets to make a field required in the first place, which is usually the harder conversation than choosing the fields.

Frequently asked questions

If your team is running one of these frameworks in name only, a title in a deal-review deck with no field behind it, that's usually a CRM problem before it's a training problem.

If you want a second pair of eyes on your own setup, Salestruct runs a free diagnostic.