What Are Sales Qualified Leads (SQLs)? Definition, Criteria & B2B Examples

Not every lead deserves a sales rep's time. That's the core reason sales qualified leads exist as a concept — and why getting the definition right matters more than most teams realize.

If your pipeline is full but your close rate is low, the problem usually isn't volume. It's qualification. Marketing sends leads over the wall, sales rejects half of them, and both teams blame each other. The root cause? A misaligned — or missing — definition of what an SQL actually is.

This guide breaks down the SQL definition, compares it to MQLs, walks through proven qualification frameworks, and shows you how to align your teams around criteria that actually predict revenue.

What Is a Sales Qualified Lead (SQL)?

A sales qualified lead (SQL) is a prospective buyer who has been vetted — by marketing, an SDR, or both — and meets specific criteria that indicate they are ready for a direct sales conversation.

The key word is ready. An SQL isn't just someone who downloaded a whitepaper or attended a webinar. It's someone who:

• Has a confirmed need your product or service solves
• Has the authority (or clear path to authority) to make a buying decision
• Has a timeline that aligns with your sales cycle
• Has a budget or funding mechanism identified

In short, SQL leads have moved beyond interest and into intent. They've been qualified against a set of agreed-upon criteria, and a sales rep has accepted them as worth pursuing.

SQL vs. Prospect vs. Opportunity

To avoid confusion, here's how SQLs fit into a standard B2B funnel:

StageDefinitionProspectA contact that fits your ICP but hasn't been engaged or qualifiedMQLA lead that has shown interest through marketing engagement (form fills, content downloads, etc.)SQLA lead that has been qualified against sales-readiness criteria and accepted by the sales teamOpportunityAn SQL that has entered a formal sales process with a defined deal stage

[INTERNAL_LINK: B2B lead generation strategies]

MQL vs SQL: Where Most B2B Teams Break Down

The MQL vs SQL distinction sounds simple on paper. In practice, it's where most sales and marketing alignment problems start.

An MQL (Marketing Qualified Lead) is a lead that marketing considers engaged enough to pass to sales. The problem? "Engaged enough" is subjective unless you define it with shared, specific criteria.

Common Symptoms of MQL-SQL Misalignment

• Sales ignores MQLs: Reps receive leads that don't match their understanding of a qualified buyer, so they stop following up.
• Marketing inflates MQL counts: To hit targets, marketing lowers the qualification bar — more volume, less quality.
• Pipeline looks full, revenue doesn't follow: Forecasts are based on bloated SQL numbers that include leads that were never truly qualified.
• Finger-pointing replaces problem-solving: Sales blames marketing for bad leads. Marketing blames sales for not working them.

How to Fix It

The fix isn't complicated, but it requires discipline:

1. Define SQL criteria together. Sales and marketing must co-own the definition. Not marketing alone. Not sales alone. Both.
2. Document the handoff process. Spell out exactly what information must be captured before a lead is passed to sales, who passes it, and the SLA for follow-up.
3. Review and recalibrate monthly. Look at SQL-to-opportunity conversion rates. If less than 40-50% of SQLs become real opportunities, your criteria are too loose.

[INTERNAL_LINK: SDR staff augmentation services]

Lead Qualification Criteria: 3 Frameworks That Work for Sales Qualified Leads

You don't need to invent your own lead qualification criteria. Several proven frameworks exist. The right one depends on your sales motion, deal size, and team maturity.

1. BANT (Budget, Authority, Need, Timeline)

The classic framework, originally developed by IBM. BANT qualifies leads based on four factors:

• Budget: Does the prospect have allocated budget or a process for securing it?
• Authority: Are you speaking with a decision-maker or someone who can influence the decision?
• Need: Does the prospect have a specific problem your solution addresses?
• Timeline: Is there a defined timeframe for making a decision?

Best for: Transactional sales, mid-market deals, teams new to formal qualification.

Limitation: Puts budget first, which can disqualify early-stage buyers who haven't yet scoped their investment.

2. MEDDIC (Metrics, Economic Buyer, Decision Criteria, Decision Process, Identify Pain, Champion)

MEDDIC is a more rigorous framework used heavily in enterprise SaaS sales:

• Metrics: What quantifiable outcomes does the prospect need?
• Economic Buyer: Who controls the budget and signs off?
• Decision Criteria: What factors will the buying committee evaluate?
• Decision Process: What steps must happen before a deal closes?
• Identify Pain: What specific pain is driving the initiative?
• Champion: Is there an internal advocate pushing for your solution?

Best for: Complex enterprise deals with long sales cycles and multiple stakeholders.

Limitation: Requires skilled reps to execute. Not ideal for high-velocity sales teams.

3. CHAMP (Challenges, Authority, Money, Prioritization)

CHAMP reorders the conversation to lead with challenges rather than budget:

• Challenges: What problems is the buyer trying to solve?
• Authority: Who needs to be involved in the decision?
• Money: Is there a budget or willingness to invest?
• Prioritization: How urgent is this initiative compared to other projects?

Best for: Consultative sales motions where understanding the problem is more important than confirming budget upfront.

Limitation: Can lead to longer discovery cycles if reps don't anchor back to commercial viability.

[INTERNAL_LINK: outbound prospecting best practices]

B2B Lead Scoring: Turning Qualification Into a System

Frameworks give you the questions. B2B lead scoring gives you the system to apply them consistently at scale.

Lead scoring assigns numerical values to specific attributes and behaviors, creating a threshold that determines when a lead becomes an SQL. There are two dimensions to score:

Fit Scoring (Firmographic + Demographic)

This measures how closely a lead matches your Ideal Customer Profile (ICP):

• Company size (revenue, headcount)
• Industry vertical
• Job title / seniority of the contact
• Technology stack (for SaaS companies)
• Geographic location

Intent Scoring (Behavioral)

This measures engagement and buying signals:

• Visited the pricing page (high intent signal)
• Requested a demo or free trial
• Opened multiple emails in a prospecting sequence
• Responded to an SDR outreach with a question about capabilities
• Downloaded bottom-of-funnel content (case studies, comparison guides)

Setting the Threshold

A lead becomes an SQL when it crosses a predefined score threshold that combines fit and intent. For example:

CriteriaPointsDirector-level or above title+15Company in target industry+10Company revenue $5M–$50M+10Requested a demo+25Visited pricing page 2+ times+15Opened 3+ emails in sequence+5SQL threshold60 points

The specific numbers will vary by your business. The point is to replace gut feeling with a repeatable, data-backed process. Review your scoring model quarterly and adjust based on which scores actually correlate with closed-won deals.

Real-World B2B Examples: SQLs in Action

Let's ground this in scenarios you'll recognize.

Example 1: SaaS Platform Selling to Mid-Market

A marketing automation company targets VP-level marketing leaders at companies with 200–1,000 employees. Their SDR team runs outbound sequences and qualifies using CHAMP:

• The VP of Marketing at a 400-person e-commerce company responds to a cold email saying they're struggling with lead attribution.
• On the discovery call, the SDR confirms they have budget earmarked for a new tool this quarter, and the VP owns the decision.
• The SDR logs the information in the CRM and converts the lead to SQL status.
• An AE receives the SQL with full context and schedules a demo within 24 hours.

Result: The deal closes in 6 weeks. The qualification data captured by the SDR gave the AE everything needed to run a targeted demo.

Example 2: Professional Services Firm Using BANT

A B2B consulting firm generates inbound leads through gated content. Marketing scores leads based on firmographics and behavior. When a lead crosses the SQL threshold:

• A Director of Operations at a manufacturing company downloads a case study and then fills out a contact form asking about implementation timelines.
• Marketing passes the lead to an SDR who confirms budget range, authority, a specific operational pain point, and a Q3 decision timeline.
• The lead is marked as an SQL and routed to a senior consultant for a strategy call.

Result: The structured handoff prevents the consultant from wasting time on unqualified conversations. Their SQL-to-close rate is 35%, compared to 12% before implementing formal criteria.

[INTERNAL_LINK: lead generation case studies]

Why Misaligned SQL Definitions Kill Pipeline Quality

Here's the uncomfortable truth: most companies define SQLs once (if at all), then never revisit the definition. Markets shift, ICPs evolve, products change — and the SQL criteria stay frozen in a dusty slide deck from 2021.

The consequences compound over time:

• Sales velocity drops because reps spend more time disqualifying leads than closing.
• CAC rises as marketing spends more to generate leads that don't convert.
• Forecasting becomes unreliable because the pipeline includes leads at wildly different stages of readiness.
• SDR turnover increases because reps feel set up to fail when they're measured on meetings booked from unqualified lists.

The fix starts with one meeting: get your head of sales and head of marketing in a room, review the last 50 SQLs, and honestly assess which ones were truly qualified. If less than half became real opportunities, it's time to rewrite the criteria.

Getting Your SQL Process Right — Without Building Everything In-House

Defining, identifying, and routing sales qualified leads properly requires three things: clear criteria, skilled SDRs to apply those criteria in live conversations, and consistent process management.

Many companies — especially those scaling fast or entering new markets — don't have the in-house capacity to build this from scratch. That's where working with a specialized partner makes sense. An outsourced SDR team trained in your ICP, your qualification framework, and your CRM can start generating properly qualified SQL leads without the 3-6 month ramp of hiring internally.

At Siete, we build and staff outbound prospecting engines for B2B companies. Our SDRs qualify leads using the frameworks that fit your sales motion — BANT, MEDDIC, CHAMP, or a custom model — so your closers only spend time on conversations that matter.

If your pipeline has a quality problem, not a volume problem, let's talk.

Book a call with our team and we'll walk you through how we build SQL-ready pipelines for companies like yours.