BANT vs MQL vs SQL: how to define a qualified lead

Ask five people in a B2B company what a qualified lead is and you'll get five answers. Marketing counts form fills. Sales counts conversations with budget. Finance counts pipeline. Your lead vendor counts whatever the contract says. None of them is wrong, but if the definitions aren't written down and agreed, every report becomes an argument and every vendor becomes a disappointment.

This guide explains the common labels, BANT, MQL, SAL and SQL, what each one is good for and where it breaks, and then walks through how to write a definition that marketing, sales and any outside partner can all use.

BANT: budget, authority, need, timeline

BANT is a sales qualification checklist popularised by IBM. A lead qualifies when the buyer has budget for a solution, the person has authority to buy or influence the purchase, there is a real need your product meets, and there is a timeline for making a decision.

BANT is simple, which is why it has lasted. It works well for transactional sales and for outbound programs where an SDR needs a quick way to decide whether a call is worth a meeting. It struggles in complex B2B sales. Budgets are often created after a need is agreed, not before. Authority is spread across a buying committee rather than held by one person. And many buyers won't share their timeline with a vendor they've just met.

Treat BANT as a set of questions to answer over time, not a gate every lead must pass on the first call. A program that only accepts leads with confirmed budget will be small and slow. A program that never asks about budget will fill the pipeline with research projects.

MQL: marketing qualified lead

An MQL is a lead that marketing believes is ready for sales attention, usually based on fit and engagement. Fit covers who the person and company are: industry, size, region, role and seniority. Engagement covers what they did: downloads, event attendance, repeat visits, replies. Most teams combine the two in a lead score and set a threshold.

MQLs are useful because they let marketing hand over leads consistently and measure the quality of what it sends. They become a problem when the threshold is set to hit a volume target rather than to predict revenue. If downloading two whitepapers makes someone an MQL, you will produce plenty of MQLs and very few meetings.

SAL: sales accepted lead

A sales accepted lead is an MQL that sales has reviewed and agreed to work. The SAL stage is often skipped, which is a mistake, because it is where marketing finds out whether its definition matches what sales actually needs. A low acceptance rate is the clearest early warning that the MQL definition, the targeting or the vendor is off.

SQL: sales qualified lead

An SQL is a lead that sales has spoken to and confirmed as a real opportunity worth pursuing. In many companies this is the point where an opportunity is created in the CRM. The criteria are usually some version of BANT or a richer framework, plus a clear next step agreed with the buyer.

SQLs are the stage most closely tied to revenue, which is why finance and leadership care about them. The risk is that they're only counted by sales, so marketing has little visibility into why leads did or didn't convert. Shared reporting from MQL through SAL to SQL fixes that.

Other frameworks you will hear about

• CHAMP: challenges, authority, money, prioritisation. It puts the buyer's problem first, which suits consultative sales.
• MEDDIC and MEDDPICC: metrics, economic buyer, decision criteria, decision process, identified pain and champion, with paper process and competition in the longer version. Built for complex enterprise deals.
• GPCTBA/C&I: goals, plans, challenges, timeline, budget, authority, plus consequences and implications. Useful when the purchase is driven by a strategic initiative.

You don't need to pick one framework for the whole funnel. Many teams use fit and engagement for MQLs, a few BANT-style questions for SQLs, and MEDDIC for larger opportunities once they are in the pipeline.

How to write a definition everybody signs

A good definition is specific enough that two people looking at the same lead would make the same call. Write it as a short document with four parts, and get it signed by the heads of marketing and sales.

• Fit: the industries, company sizes, regions, roles and seniority you sell to, plus exclusions such as current customers, competitors, students and job seekers.
• Engagement: the actions that show genuine interest, ranked by strength. A demo request outranks a webinar registration, which outranks a single download.
• Qualification questions: the answers you need before a lead counts as an SQL, and which of them are required versus nice to have.
• Hand-off: who receives the lead, how fast they must follow up, how they record the outcome and what happens to leads they reject.

Turn the definition into a service-level agreement

Definitions only work if both sides keep their side of the deal. A simple SLA says marketing will deliver a certain number of leads that meet the definition each month, and sales will follow up on each one within an agreed time and record the result. Review it monthly with real numbers: how many leads were sent, how many were accepted, how many became SQLs and how many became pipeline.

Use the same definition with outside vendors

If you buy leads through content syndication, appointment setting or another program, give the vendor the same written spec your team uses. Ask them to confirm each filter, to supply the answers to any qualifying questions with every lead, and to replace any lead that falls outside the spec. A vendor that will only work to a looser definition than your own is telling you something about the quality to expect.

For appointment setting, agree the qualification questions the SDR must ask, what counts as an attended meeting, and how no-shows and unqualified meetings are handled. For content syndication, agree how many custom qualifying questions are included and how answers are captured and delivered.

A worked example

Imagine a company selling security software to mid-sized firms. Its written definition might say: fit means a US or UK company with 500 to 5,000 employees in financial services or healthcare, and a contact in IT security at manager level or above, excluding current customers and partners. An MQL is a fitting contact who has downloaded a security guide and answered one qualifying question about their current tooling, or who has attended a webinar. Sales accepts the lead if the details are correct and the company isn't already in an open deal. It becomes an SQL once a rep has confirmed a project to replace or add tooling within the next two quarters, identified who signs off the budget, and booked a second meeting. Everyone, including the lead vendor, works from that one page.

Measure what matters

• Acceptance rate: SALs divided by MQLs. The first sign that the definition or the source is off.
• Conversion to SQL: SQLs divided by SALs. Shows whether accepted leads turn into real opportunities.
• Speed to first touch: time from hand-off to the first sales activity. Slow follow-up quietly kills good leads.
• Pipeline and cost per opportunity: the numbers that connect lead programs to revenue.

A qualified lead is whatever marketing, sales and your vendors have agreed in writing. Until that exists, every number is an opinion.

BANT, MQL and SQL aren't competing ideas. They describe different moments in the same journey. Write down what each stage means for your business, attach it to your SLA and your vendor contracts, and review it with real data every month. Most of the friction between marketing and sales disappears once everyone is counting the same thing.

Every BootSoc program starts with a written spec that covers fit, qualifying questions and hand-off, and leads outside it are replaced free. If you'd like a template, ask for one on a strategy call.