MQL to SQL Conversion
MQL-to-SQL conversion is the percentage of Marketing Qualified Leads that sales accepts as Sales Qualified Leads. An MQL is someone marketing decides is 'ready' (downloaded a whitepaper, attended a webinar, hit a lead score threshold). An SQL is someone sales agrees is worth their time. The gap between these two definitions is where most B2B revenue dies. Industry average is 13-25%. Best-in-class is 40%+. If your conversion is below 15%, marketing and sales are playing different games โ marketing is celebrating volume; sales is throwing the leads away. The metric is less about marketing performance and more about how well-aligned your two teams are on what 'qualified' actually means.
The Trap
The trap is incentivizing MQL volume without sales rejection accountability. Marketing hits 1,000 MQLs/month and gets a bonus. Sales rejects 850 of them as junk. Marketing claims they hit the goal; sales claims marketing wastes their time. Both are technically right โ the problem is the goal itself. Volume MQL targets reward filling the top of the funnel with anyone who fogs a mirror. The fix is jointly setting MQL-to-SQL targets so marketing only celebrates leads sales actually pursues.
What to Do
Run a monthly 'MQL audit' between marketing and sales leadership. Pull every rejected MQL from the last 30 days and tag the rejection reason: bad fit (wrong company size/industry), bad timing (no budget/not in market), bad data (wrong contact info), or bad scoring (lead score too generous). Aggregate the reasons. The top reason tells you what to fix in your scoring model. Most teams skip this audit and just argue about the metric in the abstract for years.
Formula
In Practice
Marketo (later acquired by Adobe) became a textbook case for MQL-to-SQL discipline. In their early scaling years, marketing was generating ~3,000 MQLs/quarter but sales was only accepting ~12% as SQLs โ burning 2,640 quarterly leads in the gap. They redesigned their lead scoring model with sales' direct input, raised the threshold for MQL designation (lower volume, higher quality), and instituted a monthly closed-loop review of rejections. Within 12 months, MQL volume dropped to ~1,800/quarter but SQL acceptance climbed to 38% โ meaning more total SQLs (684 vs 360) from fewer MQLs. The lesson: high MQL-to-SQL conversion is achieved by having FEWER, BETTER MQLs, not more.
Pro Tips
- 01
The single highest-leverage variable in MQL quality is whether sales had input into the scoring model. Marketing teams often build lead scoring in isolation based on engagement signals (page views, form fills) that don't correlate with sales-readiness. Have sales annotate 50 closed-won and 50 closed-lost deals with what 'readiness' actually looked like โ then build the model on that.
- 02
Service-Level Agreement (SLA) the handoff. Best-in-class B2B teams agree: marketing delivers MQLs meeting X criteria, sales contacts within Y hours, and either accepts or rejects within Z days with a documented reason. The SLA is the artifact that holds both sides accountable.
- 03
Track 'MQL aging': how long does an MQL sit before sales touches it? Anything over 24 hours leaks dramatically. The legendary Lead Response Management Study by InsideSales found that contacting a lead within 5 minutes of MQL trigger makes them 21x more likely to qualify than contacting at 30 minutes. Speed is the cheapest conversion lift.
Myth vs Reality
Myth
โMore MQLs is always better.โ
Reality
MQL volume is meaningless without SQL acceptance. A pipeline of 10,000 MQLs at 5% acceptance produces 500 SQLs. A pipeline of 2,000 MQLs at 40% acceptance produces 800 SQLs โ at a fraction of the cost-per-acceptance. Volume targets actively damage quality.
Myth
โMQL-to-SQL conversion is a marketing problem.โ
Reality
It's a definitional problem owned by both teams. If marketing and sales never agreed on what 'qualified' means, the conversion rate measures their misalignment, not marketing's competence. Fixing it requires sales involvement in the criteria, not just better marketing.
Try it
Run the numbers.
Pressure-test the concept against your own knowledge โ answer the challenge or try the live scenario.
Knowledge Check
Challenge coming soon for this concept.
Industry benchmarks
Is your number good?
Calibrate against real-world tiers. Use these ranges as targets โ not absolutes.
MQL-to-SQL Conversion Rate (B2B SaaS)
B2B SaaS, $1M-$100M ARRBest-in-Class
> 40%
Good
25-40%
Average
13-25%
Misaligned
5-13%
Broken Handoff
< 5%
Source: Salesforce State of Sales / HubSpot Annual Benchmarks
Real-world cases
Companies that lived this.
Verified narratives with the numbers that prove (or break) the concept.
Marketo (Pre-Adobe)
2012-2015
Marketo, the leading marketing automation platform of its era, faced a paradox: their own product generated thousands of MQLs but sales acceptance was only ~12%. They publicly documented their journey to fix it. They redesigned lead scoring with direct sales input, raised the MQL bar significantly (cutting volume), and built closed-loop feedback so every rejected MQL came back to marketing with a reason. MQL volume dropped from ~3,000 to ~1,800 per quarter, but acceptance climbed to 38%. Net SQLs nearly doubled, and the company's own marketing efficiency improved dramatically โ a particularly important demonstration since they were selling marketing software.
MQL Volume Change
3,000 โ 1,800 (-40%)
MQL-to-SQL Conversion
12% โ 38%
Net SQLs
360 โ 684 (+90%)
Acquired by Adobe (2018)
$4.75B
Lead volume is a vanity metric. Lead acceptance is the truth metric. Marketing teams that redesign their scoring with sales input โ and accept lower volume in exchange for higher quality โ almost always grow pipeline faster.
Related concepts
Keep connecting.
The concepts that orbit this one โ each one sharpens the others.
Beyond the concept
Turn MQL to SQL Conversion into a live operating decision.
Use this concept as the framing layer, then move into a diagnostic if it maps directly to a current bottleneck.
Typical response time: 24h ยท No retainer required
Turn MQL to SQL Conversion into a live operating decision.
Use MQL to SQL Conversion as the framing layer, then move into diagnostics or advisory if this maps directly to a current business bottleneck.