MQL-to-SQL Ratio Calculator
The MQL-to-SQL rate is the truest read on whether marketing and sales actually agree on what a good lead is. Enter your MQLs and SQLs — then see whether the handoff is working or just busy.
MQL-to-SQL rate = SQLs ÷ MQLs × 100%. It measures the share of marketing-qualified leads that sales accepts as worth pursuing, which makes it less a funnel metric and more an alignment metric: a low rate almost always means marketing’s MQL bar is looser than sales’s SQL bar. Common B2B rates land between 13% and 40%. The fix for a poor rate is rarely more volume — it is a single shared, written definition both teams agree to.
MQL-to-SQL Ratio Calculator inputs and result
| Rate | What it suggests |
|---|
How to use this calculator
- Use a written MQL definitionAn MQL-to-SQL rate only means something when both teams agree on what an MQL is. If marketing and sales carry different bars in their heads, the rate measures the disagreement, not the funnel.
- Count SQLs as sales-accepted, not auto-promotedAn SQL should be a lead sales actively accepted, not one a scoring model flipped automatically. Auto-promotion inflates the rate and hides the very misalignment this metric exists to catch.
- Match the period to the handoff lagAllow time for sales to review MQLs before counting SQLs. Measuring SQLs too soon after a batch of MQLs undercounts acceptances still in the queue.
- Read the rate and MQLs-per-SQL togetherThe tool shows both. MQLs-per-SQL is handy for capacity planning — it tells you how many MQLs marketing must deliver to feed a target number of sales-ready leads.
- Use a low rate as a conversation, not a scoldingA poor rate is a definition problem, not a blame exercise. Bring both teams to one written MQL standard, then re-measure — and export the before-and-after.
RGM Expert Says
Of every funnel ratio we track, MQL-to-SQL is the one that most often reveals an organizational problem rather than a marketing one. When the rate is low, marketing usually is not failing at volume — it is being measured against a private, stricter bar that sales never wrote down. The number is a symptom; the disease is two teams optimizing different definitions of the same word.
So the first deliverable in almost any alignment engagement is boring and decisive: one written MQL definition, with firmographic and behavioral criteria, that both the CMO and the CRO sign. The moment that exists, the MQL-to-SQL rate stops being a finger-pointing stat and becomes a shared scoreboard. We have watched the rate double in a quarter with zero change to lead volume, purely from agreeing on the bar.
The subtle trap is celebrating a high rate. A rate above 40% can mean tight alignment, but it can equally mean marketing has set the MQL bar so high it is throttling pipeline to protect the percentage. We always read MQL-to-SQL next to absolute SQL count and downstream win rate, because a pristine handoff rate on too few leads is alignment that has quietly become a bottleneck.
How it works
The MQL-to-SQL rate divides accepted SQLs by the MQLs marketing handed over; its inverse is MQLs-per-SQL.
- MQLs — leads that met marketing’s qualification bar and were passed to sales.
- SQLs — MQLs that sales actively accepted as sales-ready, not auto-promoted.
- MQLs per SQL — the inverse; how many MQLs are needed to produce one SQL.
This rate measures alignment, not just conversion. A low number usually signals a definition mismatch between marketing and sales rather than a volume problem.
Why this is an alignment metric in disguise
Most funnel ratios measure how well a stage performs; the MQL-to-SQL rate measures how well two teams agree. An MQL is marketing’s judgment that a lead is good; an SQL is sales’s judgment that the same lead is real. The conversion between them is therefore a direct read on whether those two judgments line up. When the rate is low, the usual culprit is not lazy follow-up but a marketing bar set looser than the sales bar — a disagreement, not a deficiency.
That is why the fix is structural rather than tactical. Adding more MQLs to a broken handoff just produces more rejected leads and more friction. The durable solution is a single written MQL definition — firmographic fit plus behavioral intent — that marketing and sales both sign. Once the definition is shared, the rate becomes a trustworthy scoreboard, and teams routinely see it climb sharply with no change in volume at all.
The rate also feeds capacity planning through its inverse. MQLs per SQL tells you how many MQLs marketing must deliver to produce the SQLs sales needs to hit pipeline targets, which connects this metric to coverage and velocity upstream. Read alongside lead-to-customer rate, it shows where in the funnel quality is gained or lost — and whether the problem to fix lives before the handoff or after it.
Typical MQL-to-SQL rates
These ranges depend heavily on how strict each team’s definition is, so they are orientation rather than targets. A stricter MQL bar raises the rate without necessarily meaning better performance.
| Rate | Read | MQLs per SQL |
|---|---|---|
| Below 13% | Low — loose MQL bar or weak handoff | 8+ : 1 |
| 13% to 25% | Common B2B range | ~4 to 8 : 1 |
| 25% to 40% | Healthy marketing-sales alignment | ~2.5 to 4 : 1 |
| Above 40% | Strong — or a very strict MQL bar | Under 2.5 : 1 |
What revenue leaders say about lead handoff
Marketing and sales have to share one definition of a qualified lead, in writing, or every handoff metric just measures the argument between them.
Predictable revenue starts with a specialized, agreed handoff between lead generation and sales — ambiguity at that seam is where pipeline leaks.