B2B & Lead Generation · Growth problem

MQL-to-SQL conversion is low

A low MQL-to-SQL rate is where marketing and sales disagreement usually surfaces first and most visibly. The cause is sometimes lead quality, but just as often a mismatch between what marketing scores as 'qualified' and what sales actually needs to accept a lead into their pipeline, compounded by handoff speed and CRM stage discipline.

Symptoms

What this usually looks like

  • MQL volume is hitting target but SQL volume consistently falls short
  • Sales routinely disputes marketing's definition of a qualified lead
  • MQLs sit unworked or unrouted for days before a sales touch
  • SQL rate varies wildly by SDR or account executive, suggesting a process rather than lead problem
  • Leads scoring high on engagement convert no better than those scoring low

Diagnostic questions

What we would test first

  • Segment MQL-to-SQL rate by source, campaign, SDR and time-to-first-contact
  • Interview sales and SDR team on current qualification criteria versus marketing's stated MQL definition
  • Analyse lead score distribution against actual SQL/disqualification outcomes
  • Audit MQL disqualification reason codes for recurring patterns
  • Check SDR capacity and workload against current MQL volume
  • Review CRM stage hygiene for stale or inconsistently applied MQL records

Root causes

Why it happens

  1. 01

    The lead scoring model weighs intent over fit, or vice versa

    Scoring models built primarily on engagement activity (downloads, page visits) can flag highly engaged but poor-fit prospects as MQLs, while scoring models built primarily on firmographic fit can miss genuinely in-market buyers who haven't engaged much yet. Getting this balance wrong in either direction depresses SQL conversion.

  2. 02

    Handoff speed from MQL to sales contact is too slow

    The window in which a marketing lead is genuinely sales-ready is often short; if SDR capacity or routing rules mean MQLs wait days for first contact, conversion drops regardless of underlying lead quality.

  3. 03

    Sales and marketing use different qualification criteria

    Where marketing's MQL definition was set without sales input, or hasn't been revisited as the ICP or proposition changed, sales will reject MQLs against criteria marketing was never measuring.

  4. 04

    SDR or sales capacity is a hidden constraint

    If SDR headcount hasn't grown with MQL volume, MQLs get worked less thoroughly or not at all, and the resulting low SQL rate reflects capacity rather than lead quality.

  5. 05

    Nurture sequencing pushes leads to sales too early or too late

    Automated nurture flows calibrated incorrectly can hand off leads before they've shown genuine buying intent, or hold genuinely ready buyers in nurture too long while competitors engage them first.

  6. 06

    CRM stage definitions and hygiene are inconsistent

    Where SDRs apply MQL and SQL stage changes inconsistently, or leave stale MQLs unresolved rather than disqualifying them, the reported conversion rate reflects data hygiene as much as commercial reality.

Evidence

The numbers we would look at

These are the metrics that make the constraint visible, and the cuts that stop them being reassuring by accident.

Metrics for this problem
MetricWhat it tells you
MQL-to-SQL conversion rateThe core metric under investigation.Segment by source, campaign, SDR and time-to-first-contact before concluding it's a lead-quality issue.
Time from MQL to first sales touchTests the handoff-speed hypothesis directly.Compare converting versus non-converting MQLs on this measure specifically.
SQL rate by SDR / account executiveIsolates a process or capacity issue from a lead-quality issue.Wide variance between individuals with similar lead allocation points to process, training or capacity, not lead quality.
Lead score distribution vs. actual SQL outcomeTests whether the scoring model actually predicts qualification.If high and low scoring leads convert similarly, the scoring model needs rebuilding.
MQL disqualification reason codesReveals the specific, recurring reasons sales rejects marketing leads.A concentrated set of reasons points to a fixable definitional gap.
Stale MQL rate (aged, unresolved)A CRM hygiene indicator that inflates or deflates the true conversion rate.High stale-MQL rates suggest the reported conversion rate is understated by unresolved records.

Measurement traps

What can mislead you

Looks fineMQL-to-SQL rate is low, so lead quality must be poor
Slow handoff, SDR capacity constraints and inconsistent CRM stage management can each produce an identical-looking low conversion rate without any actual quality problem; disaggregate before concluding.
Looks fineSales says the leads are fine now
Anecdotal sales sentiment can lag or lead the data by a quarter or more; verify with disqualification reason codes and rate trends rather than relying on verbal feedback alone.

Outcome

What better looks like

Not a promised number. A clearer basis for the next investment decision.

  • Marketing and sales jointly own and periodically review a single MQL definition
  • MQL-to-SQL rate is reported alongside time-to-first-contact, not in isolation
  • SDR capacity is planned against expected MQL volume, not treated as fixed
  • Disqualification reasons feed back into scoring model adjustments on a regular cycle

Where a Growth Diagnostic would start

A three to four week senior review across demand, discovery, acquisition, conversion, retention, measurement and capability — sequenced so this problem is either confirmed as the constraint or ruled out early. Read alongside the b2b & lead generation model page for how we frame the wider system.

B2B & Lead Generation growth consultancy

Questions about this problem

Is this always a lead scoring problem?
No — in our experience it's roughly as often a handoff-speed or SDR-capacity issue as a scoring issue, which is why the diagnostic looks at all three before recommending changes to the scoring model.
Do we need a marketing automation platform to fix this?
No specific platform is required; the fix is usually a shared definition and process change, though the analysis is easier with reliable timestamp data on lead stage changes.
How do we know if it's a capacity problem rather than a quality problem?
Comparing SQL conversion rate against SDR workload and time-to-first-contact usually separates the two; a capacity constraint shows up as slower response times correlating with lower conversion, consistent across lead sources.