Sales Qualified Lead (SQL)
Marketing FundamentalsA sales qualified lead is a lead that sales has actively engaged, qualified against a defined framework, and accepted into pipeline. Where MQL is a marketing-side judgment of fit and engagement, SQL is a sales-side judgment that the lead is worth active pursuit toward closed-won.
The SQL definition is the most important alignment artefact between marketing and sales after MQL. A sales team that rejects MQLs as not yet SQL signals that the criteria are too loose; a sales team that accepts every MQL as SQL signals that the qualification is happening too late.
Contents
Key takeaways
- An SQL has been touched by sales, qualified against a defined framework (BANT, MEDDIC, or equivalent), and added to active pipeline. MQLs become SQLs only after a sales conversation.
- Median SQL-to-closed-won conversion is 15 to 20% in B2B SaaS. Above 25% is strong; below 10% suggests over-qualification at the SQL stage.
- SQL handoff timing matters: median sales response time on inbound MQLs is 47 hours, but conversion drops 80% if the first touch happens after 5 minutes for high-intent leads.
What is a sales qualified lead?
An SQL is a lead that has met the criteria sales uses to determine pipeline-readiness. Typical SQL criteria require:
- Confirmed fit (the lead is at an ICP-fit company, in a relevant role).
- Confirmed need or interest (the lead has expressed a problem the product solves).
- Confirmed pursuability (timeline, authority, and ability to advance the conversation are at minimum present).
The SQL definition is established jointly between marketing and sales, applied by sales after a discovery touch (call, email exchange, or qualifying meeting). Most B2B teams require sales to actively touch the lead before classifying it as SQL; a lead cannot become SQL by automation alone.
Some teams add a stage between MQL and SQL called sales accepted lead (SAL): the MQL has been reviewed and accepted by sales as worth a discovery touch, but discovery has not yet happened. SAL → SQL is the conversion that captures whether sales' qualification of MQLs holds up.
MQL vs SQL
The MQL-to-SQL transition is where most B2B funnels leak. The two stages serve different purposes:
- MQL is a marketing judgment based on fit and engagement signals. It does not require a human sales touch.
- SQL is a sales judgment based on actual conversation. It requires the seller to have spoken with the buyer and confirmed pipeline-readiness.
Median MQL-to-SQL conversion in B2B SaaS is around 13% per HubSpot research, with strong programs converting 25% or more. Below 5% suggests MQL criteria are too loose. Above 40% suggests they are too strict and qualified leads are being overlooked.
The most common failure mode is the silent rejection: sales receives an MQL, never touches it, and the lead expires unworked. Closing this loop requires service-level agreements (response time commitments) and reporting that flags untouched MQLs as a sales-process problem rather than a marketing-quality problem.
From SQL to pipeline
Once a lead becomes an SQL, it enters active pipeline. Standard B2B opportunity stages from SQL to closed-won:
- 1.Discovery. Initial qualifying conversation completed. SQL formally accepted.
- 2.Demonstration. Product demo or workshop held. Buyer can articulate the value.
- 3.Proposal or evaluation. Pricing shared, deal scoped, evaluation underway.
- 4.Negotiation. Pricing and terms in active discussion.
- 5.Closed-won or closed-lost.
Median SQL-to-closed-won conversion in B2B SaaS is around 15 to 20%. Strong programs convert 25% or higher. Below 10% suggests over-qualification at SQL (deals are entering pipeline that should not have) or weak late-stage execution.
Velocity matters as much as conversion. The median B2B SaaS sales cycle from SQL to closed-won is 30 to 90 days for SMB, 60 to 180 days for mid-market, and 6 to 18 months for enterprise. Cycles longer than the segment median typically reflect a qualification or process problem rather than a buyer problem.
Common SQL mistakes
Three patterns:
- No SLA on response time. Sales response time on inbound MQLs averages 47 hours, but conversion drops 80% if the first touch happens after 5 minutes for high-intent leads (Harvard Business Review research). Service-level agreements with response-time commitments are the highest-leverage fix.
- Inconsistent SQL definitions across reps. If different sellers apply different SQL thresholds, pipeline becomes non-comparable and forecasting breaks. Documented criteria, training, and call reviews keep the bar consistent.
- SQL count as the primary KPI. Sales teams judged on SQL count will accept marginal MQLs to hit the number. The healthier metric is SQL-to-closed-won conversion: it forces qualification quality alongside volume.
The healthy practice is monthly review of MQL-to-SQL conversion (marketing's quality signal) and SQL-to-closed-won conversion (sales' qualification signal), with quarterly tuning of criteria when either drifts.
Activate your team on LinkedIn
Heyoo helps marketing teams turn employees into authentic, on-brand storytellers, with personalised drafts, a shared calendar, and pipeline-grade analytics.
Frequently asked questions
What's the difference between an SQL and an opportunity?
SQL is the qualification stage; opportunity is the pipeline stage. Some teams treat them as the same (SQL automatically becomes an opportunity); others maintain a separate opportunity creation step that confirms additional pipeline criteria. The terminology varies, but the underlying motion is the same.
How fast should sales respond to an MQL?
As fast as possible. Response time under 5 minutes lifts conversion roughly 9× compared to response time over an hour, per Harvard Business Review research. Most healthy B2B teams commit to response within 5 minutes for high-priority MQLs (demo requests, pricing-page conversions) and within 24 hours for lower-priority ones.
Should every SQL go through the same sales process?
No, in most B2B teams. Self-serve and SMB SQLs typically run a high-velocity sales process (single rep, faster cycle, smaller deal). Mid-market and enterprise SQLs run a multi-stakeholder process with multiple touches, demos, and evaluation steps. Routing SQLs to the right process is part of qualification, not separate from it.