Why SQL, not MQL, should be the number in your board deck

The slide said MQLs were up 40% quarter over quarter. The founder was proud of it. The board nodded, the number went in the minutes, and the meeting moved on to product roadmap. Nobody asked the only question that mattered: how many of those MQLs had actually talked to a salesperson.

The answer, when I pulled it later, was 6%. The other 94% were people who'd downloaded a whitepaper, hit the pricing page once, or fit a firmographic filter loose enough to catch half of LinkedIn. The number that made the board feel good was almost entirely disconnected from the number that predicts revenue. It's the same disconnect that shows up when an unsupervised marketing hire builds a dashboard nobody senior has ever pressure tested: the metric looks fine until someone finally asks what's underneath it.

The number that means something different at every company

Here's what most boards don't realize about MQLs: the definition isn't standardized, isn't audited, and isn't comparable across companies, or even across quarters at the same company. Research from Understory on B2B SaaS conversion benchmarks makes the point bluntly: two companies in the same vertical can report MQL-to-SQL conversion rates of 13% and 42%, and both numbers can be accurate. They're just measuring different things. One company counts anyone who filled out a form. The other requires demonstrated intent and confirmed ICP fit before a lead earns the label.

That flexibility is exactly why MQL is a dangerous headline metric for a board. It's not lying, technically. It's just a number marketing gets to define for itself, report on itself, and improve by loosening its own definition whenever the quarter needs a win. Martal Group's 2026 B2B benchmark analysis puts the cross-industry MQL-to-SQL conversion average at 13%, with top-performing B2B SaaS teams using behavioral scoring reaching 39 to 40%. That's not a narrow benchmark band. That's a number that can be manufactured almost anywhere inside a 3x range depending entirely on how loosely marketing wants to define "qualified."

Where the money actually gets lost

The steepest drop in the entire funnel happens at exactly this transition. An analysis synthesizing 2025 B2B SaaS benchmark data identifies MQL-to-SQL as the funnel's biggest bottleneck, with conversion rates varying enormously by lead source. A marketing team goaled on MQL volume has every incentive to keep pumping its highest-volume channel into that count, because it makes the top-line number look strong. It has almost no incentive to report the conversion rate underneath, because that number tells the real story.

This is the mechanism, not a personality flaw in any one marketing team. Goal a function on MQLs and it will optimize for MQLs, which means optimizing for volume over quality, because volume is the easier lever to pull. Goal it on SQLs, or on marketing-sourced pipeline specifically, and the incentive flips: now the loose email list is a liability instead of a stat, because it drags the number marketing is actually accountable for.

I watched this play out at a Series A company that made the switch mid-year. Under an MQL goal, the team's dashboard showed 340 MQLs a quarter, most of them from a newsletter list that had never been segmented by fit. Sales worked maybe 20 of them. When the board pushed the goal to SQLs and marketing-sourced pipeline percentage instead, the newsletter list got cut from the count entirely within a month, not because anyone was told to cut it, but because it was actively hurting the one number that now mattered. Marketing-sourced pipeline went from an unmeasured, unspoken 15% of total pipeline to a tracked 34% in two quarters. The MQL count on the dashboard dropped by more than half. The board finally had a number that meant something, and it took removing the old number to get there.

What to ask for instead

Two numbers replace MQL cleanly, and both are harder to manufacture. The first is straightforward SQL count and conversion rate. The second, and the more useful one for a board seat, is marketing-sourced pipeline as a percentage of total pipeline. Martal Group's tiered benchmark puts a floor at 30%, calls 40 to 50% healthy, and treats anything above 60% as stretch performance. That's a number a CFO can audit against the CRM, not a number marketing self-certifies.

Neither metric is gameable the way MQL is, because both require sales agreement. An SQL, by definition, is a lead sales has accepted and is willing to work. Marketing can't inflate that number without sales pushing back, because sales is the one whose time gets wasted by a bad handoff. That built-in check is exactly what MQL lacks, and it's the same kind of check a fractional CMO with board-ready reporting experience is usually brought in to install before the next round's diligence process finds the gap first.

The question that changes the board meeting

A number marketing defines, reports, and grades itself on is not a metric. It's an opinion marketing has about its own performance, formatted to look like data.

The crystallizing insight: a number marketing defines, reports, and grades itself on is not a metric. It's an opinion marketing has about its own performance, formatted to look like data. SQL and marketing-sourced pipeline require a second party's agreement to move, which is the entire reason they're worth putting in a board deck.

The next time an MQL number shows up in a portfolio company's deck, don't nod. Ask what percentage of those MQLs became SQLs last quarter, and what percentage of the pipeline sales is actually working came from marketing. If the founder can't answer both on the spot, you've just found the same gap the SQL number was designed to expose in the first place. Want a second opinion on how a portfolio company's pipeline metrics actually hold up? Let's talk.