What is a sales qualified lead (SQL) in B2B?

A sales qualified lead (SQL) in B2B is a prospective customer that the sales team has contacted and evaluated and has determined meets the qualification criteria for an active sales pursuit. The SQL typically represents the transition from marketing ownership to sales ownership of a lead. Before becoming an SQL, the lead is typically an MQL (Marketing Qualified Lead) -- a lead that marketing has deemed worth passing to sales based on profile fit and engagement signals. After the rep contacts the MQL and confirms it meets qualification criteria (typically some combination of confirmed decision-making authority, an identified business problem, budget indication, and plausible timeline), the lead becomes an SQL and a formal opportunity is created in the CRM. The MQL-to-SQL conversion rate is one of the key metrics that governs the efficiency of the marketing-to-sales handoff: if this rate is below 20-30%, either the MQL definition is too lenient (passing too many unqualified leads to sales) or the SQL criteria is too strict (rejecting leads that could be valid opportunities with more nurturing). Companies with well-aligned marketing and sales teams typically achieve MQL-to-SQL conversion rates of 40-60%, indicating that the leads marketing passes are genuinely worth pursuing.

What is the difference between MQL and SQL in B2B marketing and sales?

MQL and SQL differ in who has qualified the lead, when in the lead journey the qualification occurs, and what criteria are used: MQL (Marketing Qualified Lead): qualified by the marketing team, typically before any sales contact. Qualification is based on fit signals (job title, company, industry match to ICP) and engagement signals (content downloads, webinar attendance, email engagement, website visits above a threshold). The MQL represents marketing's assessment that this contact warrants a sales outreach. SQL (Sales Qualified Lead): qualified by the sales team, after a rep has reviewed the lead and typically after an initial contact (call, email reply, or meeting). Qualification is based on conversation-derived criteria that confirm a genuine sales opportunity: confirmed business problem, budget indication, decision-making access, and plausible timeline. The SQL represents the sales team's assessment that this is a lead worth investing active sales resources in. The handoff from MQL to SQL is one of the most frequent sources of sales-marketing misalignment. Common problems: marketing defines MQL criteria too loosely, generating high volumes of low-quality leads; sales defines SQL criteria too strictly, returning too many leads to marketing as unqualified; or the two teams have never agreed on shared definitions and there is no common language for lead quality.

What is a good MQL-to-SQL conversion rate in B2B?

MQL-to-SQL conversion rate benchmarks for B2B vary by industry, business model, and lead source: Overall benchmark: 40-60% is a healthy MQL-to-SQL conversion rate for B2B companies with well-defined MQL criteria. Below 30% indicates that the MQL definition is too loose (marketing is generating volume without sufficient quality), that the SQL criteria is too strict (sales is rejecting valid opportunities), or that the MQL-to-SQL handoff process has too much friction (leads are lost in the transition). Above 70% may indicate that SQL criteria is too lenient (the sales team is accepting too many unqualified leads that will later not convert to closed-won opportunities) or that the MQL criteria are too conservative (marketing is only passing the very top tier of leads, leaving potential pipeline behind). By lead source: Inbound, high-intent leads (demo requests, free trial sign-ups, pricing page visitors): 50-70% MQL-to-SQL. These leads have demonstrated explicit purchase intent. Content download / gated content leads: 15-25% MQL-to-SQL. These leads have shown topic interest but not purchase intent. Event and conference leads: 20-40% MQL-to-SQL. Highly variable based on event type and quality of qualification at the event. The most important action is not to hit a benchmark but to understand your specific MQL-to-SQL rate, what is driving the conversion or rejection, and whether changing either the MQL or SQL definition would improve downstream pipeline quality.

B2B Sales Qualified Lead (SQL): Definition, MQL vs SQL, and How to Define SQL Criteria

A sales qualified lead (SQL) is a prospective customer that the sales team has reviewed and determined meets the criteria for active sales pursuit. Unlike a marketing qualified lead (MQL) -- which is passed to sales based on marketing-defined criteria like lead score, content downloads, or demo requests -- an SQL has been contacted by a sales rep and has met additional qualification criteria that confirm a genuine sales opportunity exists. The SQL is typically the starting point for the formal sales process and the creation of an opportunity record in the CRM.

MQL vs SQL: what is the difference?

MQL (Marketing Qualified Lead): a lead that marketing has deemed worth passing to sales, based on criteria like job title, company size, industry (firmographic fit), and engagement with marketing content (email opens, content downloads, webinar attendance, website visits). The MQL represents marketing's assessment that this contact has sufficient profile fit and interest signals to warrant a sales outreach. The MQL has not yet been contacted by sales.
SQL (Sales Qualified Lead): a lead that a sales rep has contacted (via call, email, or meeting) and has determined meets the sales team's qualification criteria. SQL criteria typically include: confirmed decision-making authority or access to the decision-maker; a specific, identified business problem that the product can address; budget indication (the company has budget or the prospect expects budget to be available); and a plausible timeline for a purchase decision. The SQL is created when the rep determines the prospect is worth pursuing in a formal sales cycle.
SAL (Sales Accepted Lead): some companies add a third category between MQL and SQL -- the Sales Accepted Lead, which represents the rep's first review of the MQL before contacting the prospect. The SAL indicates that the rep has reviewed the lead and agreed it meets basic criteria worth pursuing; the SQL follows after the initial contact confirms qualification.

How to define SQL criteria for B2B

BANT criteria (Budget, Authority, Need, Timeline): the classic SQL framework. A lead becomes an SQL when the rep has confirmed that a budget exists or can be allocated, that the contact has authority or access to the decision-maker, that a specific need aligned to the product has been identified, and that there is a plausible timeline for a purchase decision.
MEDDIC criteria (Metrics, Economic Buyer, Decision Criteria, Decision Process, Identify Pain, Champion): a more sophisticated qualification framework used in enterprise sales. An MEDDIC SQL has confirmed the key metrics the prospect wants to improve, identified the economic buyer, understands the decision criteria and process, has a confirmed business pain, and has an internal champion.
Custom SQL criteria: many B2B companies develop their own SQL definitions based on their specific product, market, and sales motion. The key principle: SQL criteria should be defined jointly by sales and marketing, documented in the CRM, and reviewed regularly against actual conversion data. SQLs that rarely convert to closed-won deals indicate criteria that are too lenient; an SQL-to-opportunity ratio below 50% indicates that too many non-qualified leads are being passed.

Frequently asked questions

What is a sales qualified lead (SQL) in B2B?: A sales qualified lead (SQL) in B2B is a prospective customer that the sales team has contacted and evaluated and has determined meets the qualification criteria for an active sales pursuit. The SQL typically represents the transition from marketing ownership to sales ownership of a lead. Before becoming an SQL, the lead is typically an MQL (Marketing Qualified Lead) -- a lead that marketing has deemed worth passing to sales based on profile fit and engagement signals. After the rep contacts the MQL and confirms it meets qualification criteria (typically some combination of confirmed decision-making authority, an identified business problem, budget indication, and plausible timeline), the lead becomes an SQL and a formal opportunity is created in the CRM. The MQL-to-SQL conversion rate is one of the key metrics that governs the efficiency of the marketing-to-sales handoff: if this rate is below 20-30%, either the MQL definition is too lenient (passing too many unqualified leads to sales) or the SQL criteria is too strict (rejecting leads that could be valid opportunities with more nurturing). Companies with well-aligned marketing and sales teams typically achieve MQL-to-SQL conversion rates of 40-60%, indicating that the leads marketing passes are genuinely worth pursuing.
What is the difference between MQL and SQL in B2B marketing and sales?: MQL and SQL differ in who has qualified the lead, when in the lead journey the qualification occurs, and what criteria are used: MQL (Marketing Qualified Lead): qualified by the marketing team, typically before any sales contact. Qualification is based on fit signals (job title, company, industry match to ICP) and engagement signals (content downloads, webinar attendance, email engagement, website visits above a threshold). The MQL represents marketing's assessment that this contact warrants a sales outreach. SQL (Sales Qualified Lead): qualified by the sales team, after a rep has reviewed the lead and typically after an initial contact (call, email reply, or meeting). Qualification is based on conversation-derived criteria that confirm a genuine sales opportunity: confirmed business problem, budget indication, decision-making access, and plausible timeline. The SQL represents the sales team's assessment that this is a lead worth investing active sales resources in. The handoff from MQL to SQL is one of the most frequent sources of sales-marketing misalignment. Common problems: marketing defines MQL criteria too loosely, generating high volumes of low-quality leads; sales defines SQL criteria too strictly, returning too many leads to marketing as unqualified; or the two teams have never agreed on shared definitions and there is no common language for lead quality.
What is a good MQL-to-SQL conversion rate in B2B?: MQL-to-SQL conversion rate benchmarks for B2B vary by industry, business model, and lead source: Overall benchmark: 40-60% is a healthy MQL-to-SQL conversion rate for B2B companies with well-defined MQL criteria. Below 30% indicates that the MQL definition is too loose (marketing is generating volume without sufficient quality), that the SQL criteria is too strict (sales is rejecting valid opportunities), or that the MQL-to-SQL handoff process has too much friction (leads are lost in the transition). Above 70% may indicate that SQL criteria is too lenient (the sales team is accepting too many unqualified leads that will later not convert to closed-won opportunities) or that the MQL criteria are too conservative (marketing is only passing the very top tier of leads, leaving potential pipeline behind). By lead source: Inbound, high-intent leads (demo requests, free trial sign-ups, pricing page visitors): 50-70% MQL-to-SQL. These leads have demonstrated explicit purchase intent. Content download / gated content leads: 15-25% MQL-to-SQL. These leads have shown topic interest but not purchase intent. Event and conference leads: 20-40% MQL-to-SQL. Highly variable based on event type and quality of qualification at the event. The most important action is not to hit a benchmark but to understand your specific MQL-to-SQL rate, what is driving the conversion or rejection, and whether changing either the MQL or SQL definition would improve downstream pipeline quality.

Keep reading

B2B Sales Qualified Lead (SQL): What It Is, How It Differs from MQL, and Why It Matters

MQL vs SQL: what is the difference?

How to define SQL criteria for B2B

Frequently asked questions

Ready to fill your pipeline?