MQL confirms ICP fit and content engagement. HQL adds answered questions on need and fit. BANT confirms budget, authority, need and timeline. Buy the tier that matches your sales capacity — a well-staffed SDR team profits from cheap volume, while two AEs with no SDRs need booked meetings.
What each tier actually confirms
| Tier | Confirms | Does not confirm |
|---|---|---|
| MQL | ICP match plus one content engagement | Need, budget, timeline, authority |
| 2-Touch MQL | ICP match plus two verified engagements | Need, budget, timeline, authority |
| HQL | Plus stated need and solution fit | Budget, timeline, authority |
| BANT | Plus budget, authority, need, timeline | That they will actually buy |
| Booked meeting | All of the above plus a calendar commitment | That they will attend |
Notice what none of them confirm: that the deal will close. Qualification tiers reduce wasted sales time; they do not predict revenue. Vendors implying otherwise are overselling.
The capacity calculation
This is the decision that matters and it is arithmetic rather than judgement. Work out how many raw leads one rep can genuinely work per week without quality collapsing — for most B2B SDR functions this sits somewhere between 30 and 60 contacts, depending on how much research each touch requires.
Multiply by your rep count. If that number exceeds the volume you want, buy at a lower tier and let your team qualify — you will pay less per opportunity. If it falls short, buy at a higher tier, because leads that go unworked have a conversion rate of zero regardless of what you paid for them.
Cost and conversion move together
As you move up the tiers, unit cost rises and volume falls, but conversion rises too. The interesting question is not which tier is cheapest per lead but which produces the lowest cost per opportunity given your specific follow-up capability.
For a team with strong SDR capacity, MQL volume frequently produces the lowest cost per opportunity because the qualification work is done internally at marginal cost. For a team without SDRs, the same MQL volume produces a very high cost per opportunity because most of it is never contacted.
Why definitions must be written down
MQL means something different at almost every company, and ‘BANT-qualified’ from two vendors can differ substantially in rigour. Without a written specification you are buying a label rather than a standard.
A usable specification states the exact qualifying questions asked, what constitutes a passing answer, the ICP filters applied, the disqualification criteria and the rejection window. If a vendor resists writing that down, that is the most informative thing you will learn during the sales process.
The internal version of the same problem
These tiers are not only a purchasing decision. The same definitional ambiguity causes the sales–marketing conflict inside most B2B companies: marketing reports MQLs, sales says the leads are poor, and no shared written definition exists to resolve it.
Agreeing MQL and SQL definitions internally, with follow-up time commitments and documented rejection reasons, is one of the highest-return process changes available and costs nothing but a difficult meeting. Our funnel work treats it as a prerequisite rather than an outcome.
A practical decision guide
- Large SDR team with spare capacity → MQL or 2-Touch MQL
- Small SDR function, AEs stretched → HQL
- No SDRs, AEs working leads directly → BANT
- No SDRs and AE calendars are the constraint → booked meetings
- Long technical sales requiring deep product knowledge → in-house SDRs, not outsourced tiers
- Uncertain about the ICP → pilot at a mid tier before contracting volume