Lead Qualification and Scoring
Lead qualification and scoring: MQL, SQL, BANT. How to qualify leads and build a lead scoring model.
Lead qualification is how you decide which leads are ready for sales. Lead scoring assigns points based on behavior and fit so you prioritize the best prospects. MQL (marketing qualified lead) and SQL (sales qualified lead) are common labels; BANT (Budget, Authority, Need, Timeline) is a classic qualification framework.
Done well, qualification and scoring mean your sales team spends time on leads most likely to close — and marketing knows exactly when to hand them off. Done poorly (or not at all), every lead gets the same treatment and your best opportunities get buried.
MQL vs SQL
An MQL has shown interest (download, form fill, webinar) but may not be ready for a sales call. Marketing nurtures them until they meet criteria. A SQL has been vetted: they have need, budget, authority, and timeline. Sales takes over. Clear definitions prevent leads from falling through or sales from wasting time on cold contacts.
MQL vs SQL scoring criteria
| Criteria | MQL Signals | SQL Signals |
|---|---|---|
| Engagement | Downloaded guide, attended webinar, visited 3+ pages | Requested demo, visited pricing page multiple times, replied to sales email |
| Fit | Right industry or company size | Right industry, company size, job title, and confirmed budget range |
| Intent | Researching solutions | Actively evaluating vendors, has timeline |
| Next step | Continue nurture sequence | Hand to sales for direct outreach |
The key distinction: MQLs are interested, SQLs are ready. Your scoring model should reflect that difference with clear thresholds — for example, an MQL might need 40+ points to qualify, and 70+ to become an SQL.
MQL lead scoring models
MQL scoring focuses on identifying which marketing leads deserve more attention and resources. There are three common approaches:
- Point-based scoring — Assign numeric values to actions (e.g., +10 for ebook download, +20 for pricing page visit, +5 for email open) and demographics (+15 for decision-maker title, +10 for target industry). When a lead crosses your threshold, they become an MQL. Simple to set up and explain to stakeholders.
- Tiered scoring — Group leads into tiers (cold, warm, hot) based on a combination of engagement and fit. A lead must meet both a minimum engagement score and a minimum fit score to advance. This prevents high-engagement but poor-fit leads from clogging your pipeline.
- Predictive scoring — Use your CRM or a dedicated tool to analyze which past leads converted and build a model that scores new leads on the same patterns. More accurate than manual scoring but requires enough historical data to be meaningful (typically 500+ closed deals).
Whichever model you choose, review and adjust quarterly. Scoring models drift as your market and offer change. We have a free lead qualification scorecard template to get started.
SQL lead scoring
SQL scoring determines which sales-qualified leads get priority from your sales team. While MQL scoring is about marketing efficiency, SQL scoring is about sales efficiency — your closers should spend time on the deals most likely to close, at the highest value.
An SQL scoring model typically weights:
- Budget confirmation — Have they indicated budget or asked about pricing? (+25 points)
- Authority — Are they the decision-maker or an influencer? Decision-makers score higher (+20 vs +10)
- Need urgency — Is the pain acute or are they browsing? Active RFPs and stated timelines score highest (+30)
- Engagement recency — A lead who visited pricing yesterday is hotter than one who downloaded a guide last month. Weight recent actions more heavily.
- Deal size indicators — Company size, number of locations, team headcount — signals that correlate with higher contract values
Set a clear handoff threshold (e.g., SQL score of 70+) and a follow-up SLA. Leads above the threshold should get a sales touch within 4 hours. Below the threshold, route back to marketing nurture.
Lead scoring
Scoring adds points for actions (visited pricing page, opened five emails) and for fit (job title, company size, industry). Thresholds trigger handoff to sales or a different nurture path. You can use a simple scorecard or a model in your CRM.
Example scoring model
| Action / Attribute | Points | Category |
|---|---|---|
| Visited pricing page | +20 | Behavioral |
| Downloaded resource | +10 | Behavioral |
| Opened 5+ emails | +15 | Behavioral |
| Requested demo or consultation | +30 | Behavioral |
| Decision-maker title (Owner, VP, Director) | +20 | Fit |
| Target industry | +15 | Fit |
| Company size 10-200 employees | +10 | Fit |
| No engagement in 30+ days | -20 | Decay |
Thresholds: 0-39 = Cold (nurture), 40-69 = MQL (marketing qualified), 70+ = SQL (hand to sales). Adjust based on your conversion data.
MQL / SQL Lead Scorer
Check every signal that applies to this lead. Your score and classification update in real time.
BANT qualification framework
BANT (Budget, Authority, Need, Timeline) is the most widely used sales qualification framework. It gives your team a repeatable checklist for every lead conversation:
- Budget — Can they afford your solution? This doesn't mean asking "what's your budget?" on the first call. It means understanding whether the investment is realistic for their business. For B2B, look at company size and revenue signals. For services, ask about current spend on the problem you solve.
- Authority — Are you talking to the decision-maker? If not, who is, and how do you get in front of them? Many deals stall because the champion can't get internal buy-in. Identify the decision-making process early.
- Need — Is there a real, quantifiable pain? "We should probably improve our lead follow-up" is different from "we're losing 40% of leads because nobody responds for 3 days." The second is a need. The first is a thought.
- Timeline — When do they need this solved? A lead with a 6-month timeline is worth nurturing; a lead evaluating vendors this week is worth a same-day call. Timeline determines urgency and resource allocation.
SQL qualification with BANT
BANT maps directly to SQL scoring. A lead that checks all four boxes — confirmed budget, talking to the decision-maker, clear need, and defined timeline — is your highest-priority SQL. Leads with 3 of 4 are strong candidates. Fewer than 3, and they likely need more marketing nurture before sales invests time.
Integrating BANT into your CRM is straightforward: add custom fields for each criterion, score them during discovery calls, and use automation to flag leads that meet your threshold. Most CRMs (HubSpot, Salesforce, Pipedrive) support this natively or with minimal configuration.
Other qualification frameworks
BANT isn't the only option. Other frameworks work better depending on your sales motion:
- MEDDIC (Metrics, Economic buyer, Decision criteria, Decision process, Identify pain, Champion) — Better for enterprise sales with long cycles and multiple stakeholders
- CHAMP (Challenges, Authority, Money, Prioritization) — Leads with the pain instead of the budget, better for solution selling
- GPCTBA/C&I (Goals, Plans, Challenges, Timeline, Budget, Authority, Consequences & Implications) — HubSpot's framework, more thorough but heavier to implement
Use the framework that fits your sales process. The point is consistency: marketing and sales need to agree on what "qualified" means so handoffs are clean and no good leads get dropped.
Back to lead generation, types of leads, and lead funnel. Free audit.