SQL (Sales Qualified Lead)

What is an SQL (sales qualified lead)?

A sales qualified lead (also called sales-accepted lead, SAL, or sales-ready lead) is a prospect that has passed marketing qualification and been reviewed by a sales rep who confirms the lead is worth pursuing. The SQL stage sits between MQL and opportunity in the revenue funnel.

The distinction matters because marketing and sales define "qualified" differently. Marketing scores leads on engagement — downloads, page views, email opens. Sales qualifies on buying readiness — budget exists, authority is confirmed, the need is real, and the timeline is defined. A lead can be highly engaged with your content and still be a poor SQL if they have no budget or decision-making authority.

For B2B SaaS companies, healthy MQL-to-SQL conversion rates range from 25-40%. Below 20% signals that marketing is passing leads that sales does not consider viable. Above 50% may mean marketing is holding leads too long and missing the buying window.

SQL is not the same as an opportunity. SQL means "I agree this is worth a conversation." Opportunity means "I have had a discovery call and confirmed a real deal exists." The conversion from SQL to opportunity is a separate metric with its own benchmarks (typically 40-60% for mid-market B2B).

Why SQL matters for operators

The MQL-to-SQL handoff is where marketing and sales alignment either works or breaks. When alignment is poor, two things happen: sales ignores marketing leads (follow-up rate drops below 50%), or sales spends time on leads that never convert (SQL-to-opportunity rate falls below 30%).

Both are expensive. An operator running a 10-person sales team at an average fully loaded cost of $120K per rep is spending $1.2M annually on selling capacity. If 40% of that time goes to leads that fail SQL qualification, the company is burning $480K per year on unqualified outreach.

Operators who track SQL conversion rates by source channel find the problem fast. Paid search SQLs might convert to opportunity at 52%, while webinar SQLs convert at 18%. Without SQL tracking by channel, the marketing team optimizes for MQL volume — producing more webinar leads that sales rejects. The SQL metric forces source-level accountability.

A $12M ARR SaaS company that improved MQL-to-SQL alignment from 24% to 36% added $1.8M in qualified pipeline in one quarter — not by generating more leads, but by generating the right ones.

SQL conversion rate formula

MQL-to-SQL Conversion Rate = SQLs / MQLs x 100

Example:
- MQLs generated in March: 342
- SQLs accepted by sales in March: 108

MQL-to-SQL Rate = 108 / 342 x 100 = 31.6%

SQL-to-Opportunity Rate = Opportunities Created / SQLs x 100

Example:
- SQLs in March: 108
- Opportunities created from March SQLs: 54

SQL-to-Opp Rate = 54 / 108 x 100 = 50.0%

What counts as an SQL:

• Included: Leads that a sales rep has reviewed and accepted for outreach. The rep confirms fit and intent.
• Excluded: Leads auto-routed but not yet reviewed. Leads rejected during sales review (these are "sales-rejected leads," or SRLs).

Important: Track SQL acceptance rate (SQLs / total leads routed to sales) separately from MQL-to-SQL rate. They measure different things — routing efficiency versus marketing qualification quality.

SQL benchmarks by company segment

How SQL conversion rates vary across B2B company types and sales motions.

Sources: Forrester B2B Marketing Benchmark 2025, SiriusDecisions Demand Waterfall 2025, industry-observed ranges.

Common mistakes when tracking SQLs

1. No agreed SQL definition between marketing and sales

Marketing says "they downloaded the pricing PDF." Sales says "they have budget and authority." Without a shared definition, the MQL-to-SQL handoff becomes a territory dispute. Document the specific criteria a lead must meet before it becomes an SQL. Write it down. Both teams sign off.

2. Auto-converting MQLs to SQLs without sales review

Some CRM workflows automatically promote MQLs to SQL status based on score thresholds. This inflates SQL numbers and skips the human judgment that makes the SQL stage valuable. The rep must review and accept the lead — that is the entire point of the SQL stage.

3. Not tracking SQL response time

An SQL accepted but not contacted for 72 hours is a wasted SQL. Research from InsideSales.com shows that leads contacted within 5 minutes convert at 8x the rate of leads contacted after 30 minutes. Track time-to-first-touch from SQL acceptance, not from MQL creation.

4. Measuring SQL volume without SQL quality

A team that generates 200 SQLs per month with a 22% opportunity conversion rate outperforms a team that generates 400 SQLs with a 9% conversion rate. Report SQL-to-opportunity rate alongside SQL volume. Volume without conversion context is a vanity metric.

5. Not segmenting SQLs by source

Paid search SQLs, organic SQLs, event SQLs, and referral SQLs convert at different rates. Blending them into one number hides which channels produce sales-ready leads and which produce marketing-qualified leads that sales rejects.

How Fairview tracks SQLs automatically

Fairview's Pipeline Health Monitor connects to your CRM and tracks every lead through the MQL-to-SQL-to-opportunity funnel. Conversion rates are calculated by source channel, time period, and rep — updated weekly without manual reporting.

The Operating Dashboard displays SQL conversion rates alongside pipeline coverage and win rate, so you see how lead quality flows through to closed revenue. The Forecast Confidence Engine factors SQL-to-opportunity conversion rates into its weekly forecast — when SQL quality drops, the forecast adjusts before the pipeline shows it.

When MQL-to-SQL conversion drops below historical norms, the Next-Best Action Engine surfaces the source: "MQL-to-SQL rate fell from 33% to 21% over 4 weeks. Paid social MQLs are converting at 11% versus 38% for organic search. Review paid social targeting criteria."

→ See how Pipeline Health Monitor works

SQL vs MQL

An MQL says "this person is engaged with our content and fits our target profile." An SQL says "a sales rep has reviewed this lead and confirmed it is worth pursuing." The SQL stage adds human judgment to algorithmic scoring — and that judgment is what makes the number meaningful for forecasting.

FAQ

What is an SQL in simple terms?

A sales qualified lead is a prospect that a sales rep has reviewed and accepted as worth pursuing. It means the lead has moved past marketing scoring and a human has confirmed buying signals — budget, authority, need, and timing. SQLs sit between marketing qualified leads and opportunities in the sales funnel.

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

For mid-market B2B SaaS, 25-38% is healthy. Below 20% means marketing is passing leads that sales rejects — the scoring model needs recalibration. Above 50% may mean marketing is holding leads too long. The benchmark depends on your ICP definition and how strictly you gate MQL status.

How do you calculate SQL conversion rate?

Divide the number of SQLs by the number of MQLs in the same period, then multiply by 100. For example, 108 SQLs from 342 MQLs equals a 31.6% MQL-to-SQL conversion rate. Track this by source channel to see which marketing programs produce sales-ready leads versus leads that get rejected.

What is the difference between SQL and MQL?

An MQL is scored by marketing automation — engagement signals like downloads, page views, and email clicks. An SQL is reviewed and accepted by a sales rep who confirms buying readiness. The key difference is human judgment. MQL is algorithmic. SQL is a rep saying "I will work this lead."

How often should you track SQL metrics?

Weekly for conversion rates by source. Monthly for trend analysis and marketing-sales alignment reviews. If SQL volume is low (under 30 per month), use a rolling 60-day window to avoid noise. The weekly cadence catches source-quality problems before they waste a full month of sales capacity.

What happens to leads that fail SQL qualification?

Leads rejected by sales should be tracked as "sales-rejected leads" (SRLs) with a rejection reason: wrong ICP, no budget, no authority, bad timing. SRLs with timing issues go back to marketing nurture. SRLs with ICP mismatch inform lead scoring model updates. Never delete rejected leads — the rejection data is what improves qualification.

Related terms

• MQL (Marketing Qualified Lead) — The lead stage before SQL, scored by marketing automation on engagement and fit signals
• Win Rate — Percentage of opportunities that close, directly affected by SQL quality upstream
• Pipeline Coverage Ratio — Pipeline relative to quota, dependent on SQL-to-opportunity conversion for accuracy
• Sales Velocity — Revenue throughput of the pipeline, where SQL quality affects number of opportunities and win rate
• Discovery Call — The first structured sales conversation, typically the step that converts an SQL into an opportunity

Fairview is an operating intelligence platform that tracks SQL conversion rates by source and rep — alongside pipeline coverage, win rate, and sales velocity. Start your free trial →

Siddharth Gangal is the founder of Fairview. He built funnel conversion tracking into the platform after seeing operators discover that their "lead quality problem" was actually a lead definition problem — marketing and sales were using different criteria for the same word.