Low MQL to SQL Conversion Starts With the MQL Definition

The monthly report shows MQLs up for the third month in a row, and the pipeline hasn't moved. Sales says most of those leads aren't worth a call. Marketing blames follow-up, and the CEO starts wondering what the budget is actually buying.

Most B2B leaders read that as a lead quality problem or a sales effort problem, so they ask for better leads or push reps to call faster. I'd look at something else first, which is what your company actually counts as an MQL. When MQL-to-SQL conversion stays low, the definition is usually where revenue is leaking. In most companies, it's built on downloads and email clicks, and sales never helped write it.

In Revenue Rewired, the framework we use at StringCan to find where B2B revenue leaks, this is a Metrics Misfire. The team gets measured on a number that doesn't predict revenue, so it gets very good at producing that number.

Direct answer

Low MQL-to-SQL conversion usually means your MQL is defined by marketing activity instead of fit and buying intent. Before you blame lead quality or sales effort, pull the last 90 days of MQLs and check which action pushed each one over the line. If most qualified through content downloads, email clicks or page visits, the definition is the problem. Don't assume more leads or a new scoring tool will fix it, because both feed the same definition. This is a Metrics Misfire, often paired with a Volume Trap. The business cost is marketing spend that never becomes pipeline, rep time burned on bad-fit contacts, and a CEO who starts cutting the wrong budget.

What's the difference between an MQL and an SQL?

An MQL, or marketing qualified lead, is a contact marketing believes is ready for sales attention. An SQL, or sales qualified lead, is one that sales has accepted as a real opportunity. The rate between them tells you how much your teams agree on what a good lead looks like.

In many companies, the MQL was set up years ago inside the marketing automation platform. Nobody revisited it when the ICP shifted, so the platform keeps promoting contacts that look engaged while sales quietly ignores them.

Signs your MQL definition is the leak

Answer these from the CRM, not from memory.

• MQL volume rises while SQLs and pipeline stay flat.
• Students, job seekers, and vendors show up as MQLs.
• Most MQLs qualified through a download or email click.
• Sales has its own private rules for which MQLs it actually calls.
• Nobody knows when the scoring model was last changed.
• Rejected leads go back to marketing with no reason logged.

If three or more sound familiar, fix the definition before anyone asks for more volume. Teams skip this because the MQL feels like plumbing the platform handles. It's actually the agreement your whole handoff runs on.

Why MQL counts climb while pipeline stays flat

When marketing's goal is an MQL count, the fastest way to hit it is to lower the bar by gating another ebook or broadening the targeting. Each move looks like progress in the monthly report, and none of them changes who buys.

That's how a Metrics Misfire turns into a Volume Trap. Nothing corrects it, because sales rejects leads without logging why, and marketing never learns which signals predict a deal.

Most agencies won't tell you this, but more leads pushed through a bad definition make the leak worse, because they bury the few good leads in a longer queue and teach reps the list isn't worth their time. Once sales stop trusting the list, even a great lead gets treated like noise.

Lead quality, follow-up, or definition? How to tell which one is failing

You can separate these problems in an afternoon.

1. Check what qualified each MQL. Sort 90 days of MQLs by the action that pushed them over the threshold. If most came from low-intent actions, it's a definition problem.
2. Check fit. Compare those MQLs to your ICP on industry, company size, and role. If poor-fit contacts still scored as MQLs, the definition isn't weighting fit.
3. Check follow-up on the good ones. Take the MQLs that fit and show real intent. If many waited days for a first response, you also have a Ghost Handoff, and that's a separate fix.

Most companies find some of each. Fix the definition first, since it decides which leads the follow-up gets pointed at.

How to rebuild the MQL with sales in the room

This is Align work, the first stage of StringCan's Revenue Flow methodology. Both teams agree on what a sales-ready lead is before anyone adds activity.

• Review your last 20 closed-won deals together. Note who those buyers were and what they did first.
• Separate fit from intent. A contact outside your ICP shouldn't become an MQL, however engaged they are.
• Weight real buying signals, like demo requests, pricing page visits, and direct replies.
• Require a logged reason every time sales rejects an MQL, and review those reasons monthly.
• Change what the CEO sees. Lead the report with SQLs, pipeline created and conversion by source.

Expect MQL volume to drop after you do this. A smaller list that sales works is worth more than a big one it ignores.

FAQ

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

There's no single number that applies across companies because every company defines an MQL differently. A loose definition produces a low rate and a strict one produces a high rate, even with the same buyers. Compare your own rate over time and by source. If one source converts far below the others, start there.

Who should own the MQL definition, marketing or sales?

Both teams have to agree on it, but one person should own maintaining it. That's usually the marketing leader or a RevOps lead, with the sales leader signing off on every change. If sales didn't help write the criteria, the definition drifts back toward what's easy for marketing to produce.

Should we stop reporting MQLs to leadership?

Don't drop them, but stop leading with them. MQL count is a useful operating number for marketing, but it doesn't predict revenue on its own. Put SQLs, pipeline created and revenue by source at the top of the leadership report and keep MQLs underneath as context. Tell leadership before you tighten the definition, so a lower MQL count doesn't read as a worse quarter.

What if we've rebuilt lead scoring before and nothing changed?

Then the leak is probably upstream or downstream of scoring. Upstream, your ICP may be too broad, so even a well-built score attracts the wrong companies. Downstream, good leads may be stalling in the handoff to sales. That's when a wider diagnosis helps, like the Revenue Leak Finder or a Growth System Session, which maps what to fix before adding more activity.

Take the Revenue Leak Finder. If your result feels familiar, send it to me and I'll tell you where I'd inspect first.

Jay Feitlinger is the CEO of StringCan and the creator of Revenue Rewired, a framework that helps B2B leaders find where revenue leaks between marketing, sales and operations.