Lead qualification is the process of deciding whether a lead deserves your sales team's time, by checking whether they fit the companies you sell to, whether they have a real need, and whether they're in a position to buy. It sits between a lead arriving and a rep committing hours to it.

The reason it matters is that selling time is short. In Salesforce's sixth State of Sales report, reps said they spend 70% of their time on non-selling tasks. Whatever is left over shouldn't go to people who were never going to buy.

Most qualification problems we see have little to do with which framework a team picked. They come from a bar nobody wrote down, so marketing and sales each apply their own, good leads slip through the gap, and weak ones clog the queue.

TL;DR

• Qualification checks three things: fit with your ICP, a real need, and the ability to buy (budget, authority and timing). A lead that fails one of them waits, however keen it looks.

• Lead scoring ranks the queue automatically. Qualification is the decision, often made by a person in a conversation, that a lead is worth real sales effort.

• Leads pass three gates, MQL, SQL and opportunity, and each needs written criteria. HubSpot's lifecycle stages give you the labels but leave the criteria to you, and speed counts: in HBR's research, firms that tried to reach a lead within an hour were nearly seven times as likely to qualify it as firms that waited an hour longer.

• BANT is a quick four-question read for simple deals. MEDDIC (or MEDDPICC) maps a buying committee for complex ones. Most teams do best with the light check early and the deep one at opportunity stage.

• Marketing and sales need one written definition of qualified, a required rejection reason whenever sales sends a lead back, and a monthly look at those reasons.

• Your bar is too low if sales ignores most MQLs, and too high if deals keep coming from leads you marked unqualified.

What lead qualification actually checks

Every framework you'll come across is a different way of asking the same three questions.

Do they fit? The company matches your ideal customer profile on industry, size, region and the tools they run, and the person has a role that buys or influences a purchase like yours.

Do they need it? There's a real problem behind the interest, not just curiosity. A pricing page visit, a reply asking about integrations or a demo request points to need. A single ebook download usually doesn't.

Can they buy? Someone with budget and authority is involved, or reachable, and the purchase could happen in a time frame that matters to your forecast.

The first two questions map closely onto the split between fit score and intent score. Fit is who they are, intent is what they're doing, and a lead with only one of the two isn't ready for a rep. Signs of active research, the raw material of signal-based selling, tell you a fitting lead is also looking now.

Product-led companies often swap the second question for usage. Someone who has invited three colleagues to a free workspace has answered "do they need it?" more clearly than any form could, which is the idea behind the product-qualified lead.

Scoring ranks, qualification decides

People mix these two up constantly, and it causes real confusion about who owns what.

Lead scoring is the automated layer. It gives every lead a number from fit and behavior, recalculated all the time, so the queue sorts itself before anyone looks at it. At company level, account scoring does the same job for the whole account.

Qualification is the decision on top. It's the call that this lead gets an SDR's time, or that this opportunity goes into the forecast. A score informs that call, but it can't hear that the prospect's budget was frozen last week or that the contact is leaving the company.

You need both. Scoring without qualification passes noise to reps at speed. Qualification without scoring buries the people doing it in raw volume. If you run HubSpot, our guide to HubSpot lead scoring covers how to set the score up so it feeds qualification instead of replacing it.

Following one lead from form fill to opportunity

Stage names make more sense with a real lead attached, so here's one moving through a typical B2B setup.

On a Monday morning, a Head of RevOps at a 220-person software company downloads a guide and, an hour later, looks at your pricing page twice. Enrichment confirms the company sits in your best segment. Fit and engagement both cross the agreed bar, so the contact becomes a marketing qualified lead.

An SDR picks it up before lunch. That timing isn't a detail. Research published in Harvard Business Review found that firms that tried to contact a lead within an hour were nearly seven times as likely to qualify it as firms that tried even an hour later. The same study's audit of 2,241 US companies found an average response time of 42 hours among those that replied within a month. This is the practical case for speed to lead and lead routing that puts the record in front of the right person straight away.

On the call, the SDR learns the team is replacing a patchwork of spreadsheets, the CFO signs off on anything above a set amount, and they want a decision before the next quarter. That's enough for sales to accept it as a sales qualified lead.

Two weeks later the account executive has met the CFO, mapped who else is involved and agreed next steps in writing. A deal record is created with an amount and a close date, and the lead becomes an opportunity. From here, the forecast depends on it.

HubSpot's lifecycle stages follow the same order. Its documentation defines an MQL as a record marketing has qualified as ready for sales, an SQL as one sales has qualified as a potential customer, and an opportunity as a record associated with a deal. Notice what the definitions leave out: what makes a lead qualified in the first place. Your team has to write that part.

BANT or MEDDIC: which qualification framework fits your deals?

BANT, the quick read

BANT asks about Budget, Authority, Need and Timeline. Can they pay, can this person decide, is the problem real, and is it happening soon? It's usually credited to IBM, and IBM's own partner paperwork still spelled it out as Budget, Authority, Need, Timeframe and rejected deal registrations that didn't describe all four.

It holds up well for transactional and mid-market deals, where an SDR has a few minutes per lead and a single buyer often controls the money. Its weak spot is the committee. Many purchases no longer have one tidy budget holder, and a rep who stops at "the person I spoke to says they have budget" often finds out late that they don't decide.

MEDDIC, for deals a committee buys

MEDDIC stands for Metrics, Economic buyer, Decision criteria, Decision process, Identify pain and Champion. MEDDPICC adds Paper process and Competition. It asks for far more evidence: the measurable result the customer expects, the economic buyer who signs, how the decision will be made, and a champion inside the account who wants you to win.

That depth fits how bigger deals actually happen. In 2021, Forrester reported that more than 80% of purchases now involve complex buying scenarios, and a framework that maps the whole buying committee stops a team from spending six months on a deal that one unknown stakeholder can kill.

Light early, deep later

Forcing one framework on every lead serves nobody. Asking an inbound lead for its decision process on the first call is overkill, and forecasting a six-figure deal on four BANT boxes is reckless.

The setup we'd recommend for most B2B teams is a BANT-style check at the MQL to SQL handoff and MEDDIC or MEDDPICC once a deal becomes an opportunity. Teams with a consultative motion sometimes prefer SPICED, which leans harder on the customer's situation and pain. Which one you choose matters less than writing the required fields into the CRM, so a stage can't move until the answers exist.

Getting marketing and sales to agree on what "qualified" means

The classic argument goes like this. Marketing reports three hundred qualified leads this month. Sales says ten were real and stopped opening the rest. Both are telling the truth, because each team is using its own definition.

The fix is unglamorous and it works. Write one definition with both teams in the room, covering the fit criteria (industry, size, region), the exact actions that count as engagement, and the response time sales commits to once a lead arrives.

Then make rejection cost a few seconds. Every lead sales sends back needs a reason picked from a short list, such as wrong size, student, competitor, no project, or already a customer. Once a month, look at those reasons together. If one reason dominates, the definition changes, not the people.

Leads that fall between the two teams, accepted by nobody and worked by nobody, are a major source of lead leakage. Our write-up on the marketing to sales handoff in HubSpot shows how to build the definition, the rejection reasons and the follow-up tasks into the CRM itself.

Is your qualification bar too high or too low?

A qualification bar is never set once. Here are the symptoms that tell you which way to move it.

Signs the bar is too low:

• Sales accepts only a small share of MQLs, and reps have quietly stopped opening the MQL view.

• Calendars are full of first calls that end with "we're just researching".

• Pipeline looks healthy in volume, but the pipeline conversion rate from opportunity to won keeps sliding.

Signs the bar is too high:

• Won deals keep turning up from leads that were marked unqualified or left in nurture.

• Marketing can't produce enough MQLs to hit target, even though inbound volume is fine.

• SDRs spend more time filling in qualification fields than talking to prospects.

The bar also depends on what comes in at the top. Lead generation that targets well-fit accounts from the start means a larger share of leads qualify, so tighter targeting upstream saves work downstream. Much of that targeting, from building lists to enriching and scoring them, is the kind of work you can automate sales prospecting around.

When the bar sits in the right place, the effect shows up in more than one number at once. Reps spend their week on prospects who can buy, win rates climb, and the forecast stops swinging from week to week.

Wrapping up

Lead qualification is a judgment about where finite selling hours should go. The frameworks help, but the hard part is agreeing on what counts as qualified, writing it down where the CRM can enforce it, and checking every month whether reality still agrees.

The pieces fit together in a simple order. Scoring sorts the queue, the MQL and SQL gates check fit, need and the ability to buy, and a deeper framework takes over once real money is in play. Fast follow-up makes each gate more accurate, and rejection reasons tell you when to move the bar.

Getting this right is one of the highest-return parts of a working go-to-market system, because every rate after it depends on it.

When reps tell us they're buried in leads that never close, what we build is mostly plumbing: written criteria, required fields at each stage, a picklist of rejection reasons and routing that respects all of it, set up in the client's own CRM. Then it's theirs, and their sales leader decides when the bar moves.

Frequently asked questions