What is MQL to SQL conversion rate?
MQL to SQL conversion rate is the percentage of marketing qualified leads that sales accepts as sales qualified leads. It measures how much of the pipeline marketing hands off actually clears the bar sales has set for a real opportunity. A low rate usually means the two teams disagree on what counts as qualified.
How this calculator works
The formula: MQL to SQL rate = SQLs ÷ MQLs SQLs at target rate = MQLs × target rate Extra SQLs = SQLs at target − current SQLs Extra pipeline value = extra SQLs × avg SQL value
The target rate and SQL value fields are optional. Add them to see how many more sales-ready leads, and how much more pipeline, a tighter qualification process would produce from the same MQL volume.
What's a good MQL to SQL conversion rate for B2B SaaS?
Benchmark figures for this metric vary more than most funnel metrics, because MQL definitions aren't standardized across companies the way a trial signup is. Third-party marketing analytics benchmarks put the cross-industry average around 13%, while several B2B SaaS-specific sources cite 20% to 40% as typical and 40%+ as a strong result.
| Performance tier | MQL to SQL rate | What it usually signals |
|---|---|---|
| Needs attention | Under 15% | Loose MQL definition, weak lead scoring, or a marketing-sales gap |
| Typical / average | 15% to 30% | A reasonably well-run qualification process |
| Strong | 30% to 50%+ | Tight MQL criteria, solid scoring, close alignment |
Rates also swing by channel. Leads from your own website and customer referrals tend to convert into SQLs well above the blended average, since the person already has context or trust going in, while paid and cold-outbound leads usually pull the number down. Track your own trend by channel rather than chasing one universal target.
How to improve your MQL to SQL conversion rate
Make your MQL bar harder to clear
Most weak MQL to SQL rates start with a marketing-qualified definition that's too easy to hit. A single ebook download or newsletter signup being enough to call someone qualified guarantees sales will reject the bulk of what marketing sends over.
Tightening the definition is usually the fastest lever, because it reduces the volume marketing counts as an MQL rather than asking sales to accept more of the same weak leads. The fix is combining signals, not raising the bar on just one.
- Company size and industry match your ICP, not just any visitor
- Multiple high-intent touches (pricing page, demo request, comparison page), not a single download
- A job title or seniority level that can actually buy or influence the purchase
- Recent activity, not a lead that went cold three months ago
Build lead scoring around buying signals, not just profile fit
A lead scoring model is the mechanism that turns your MQL definition into something repeatable, instead of a judgment call every rep makes differently. Points typically come from two buckets: fit (does this account match your ICP) and behavior (is this person actually showing intent to buy). Neither bucket alone is enough.
Fit without behavior gives you a long list of accounts that could buy someday, most of which sales will reject as not-yet-ready. Behavior without fit surfaces plenty of engaged visitors who were never going to be a good customer, wasting sales time on deals that were never winnable.
The score threshold that defines an MQL should be set jointly with sales and revisited quarterly against actual close data, not fixed once and left alone. If SQLs accepted at a given score keep closing, the threshold is calibrated. If they keep bouncing back, it's set too low.
Put a real SLA between marketing and sales
A service level agreement between marketing and sales turns MQL to SQL conversion from a source of finger-pointing into a shared, measurable process. It should spell out what marketing commits to deliver (lead volume and quality criteria) and what sales commits to in return (response time and a documented reason for every reject).
Without an SLA, marketing tends to measure success by MQL volume while sales measures it by how many MQLs waste their time, and both sides end up right by their own definition. A shared dashboard tracking the rate alongside reject reasons keeps both teams looking at the same number.
Send rejected leads back with a reason code
Every lead sales rejects should come back to marketing with a reason attached, not just disappear from the pipeline. Without that feedback loop, marketing keeps generating the same type of lead that keeps getting rejected, and the conversion rate stays flat no matter how much volume goes in at the top.
- Not a fit (wrong company size, industry, or use case)
- Not ready (early research, no timeline or budget yet)
- Wrong contact (no authority or budget to buy)
- Bad data (invalid email, duplicate, or already a customer)
Feeding these reason codes back into lead scoring and campaign targeting is what actually moves the MQL to SQL rate over time, rather than a single scoring tweak that fixes the symptom for one quarter and drifts back afterward.
Break your rate out by channel before you touch anything else
A single blended MQL to SQL rate hides more than it reveals, because different channels produce leads with very different intent. Organic search and referral leads tend to convert well above a paid or cold-outbound blended average, since the person is already looking for a solution rather than being interrupted by an ad.
Segmenting the rate by channel, campaign, and even content type shows exactly where the weak leads are coming from before you change your scoring model or your SLA. A channel converting at 45% doesn't need the same fix as one converting at 8%, even if they roll up to the same blended average.
This is also the fastest way to catch a channel mix shift before it tanks your overall number. If a paid campaign suddenly triples MQL volume with low intent, the blended rate will drop even though every individual channel is performing exactly as before.
Frequently asked questions
How do you calculate MQL to SQL conversion rate?
MQL to SQL conversion rate equals the number of SQLs divided by the number of MQLs, times 100. In the example on this page, 150 SQLs from 500 MQLs is 150 divided by 500 times 100, which equals 30%. Always use the same time period for both numbers, usually a month or a quarter.
What is a good MQL to SQL conversion rate for B2B SaaS?
Most B2B SaaS benchmarks put a typical rate between 20% and 40%, with top-performing teams at 40% or higher, though a broader cross-industry average sits closer to 13%. Anything consistently under 15% usually points to a loose MQL definition or a gap between what marketing and sales each consider qualified, rather than a marketing volume problem.
What's the difference between an MQL and an SQL?
An MQL (marketing qualified lead) has shown enough interest through marketing touches, like a demo request or repeat pricing-page visits, to be worth sales attention. An SQL (sales qualified lead) is an MQL that a sales rep has vetted and accepted as a real opportunity.
Sales usually vets against criteria like budget, authority, need and timeline. The MQL to SQL rate measures how many of the first group actually become the second.
Why would a high MQL to SQL rate still not translate into revenue?
MQL to SQL rate only measures whether sales accepted a lead as an opportunity, not whether that opportunity ever closes. A team can hit a 40% MQL to SQL rate by accepting leads too easily and still miss revenue targets if those SQLs stall out later.
Always read this metric alongside SQL-to-customer close rate and average deal size, not on its own. A high acceptance rate paired with a low close rate usually means the acceptance bar just moved from marketing to sales instead of getting fixed.