Stop Giving Marketing an MQL Target

I was talking to a CRO at the end of a meeting last week. We'd been discussing targets for the marketing and sales teams, and I made the case that marketing's main metric should be Pipeline Generated, not MQLs. His pushback was immediate: "But they need an MQL target to aim for, right?"

It's a reasonable reaction. MQL targets feel concrete. They give marketing something to count, something to report on, something to optimize toward. The problem is what happens next.

The MQL Target Trap

When marketing has an MQL target, the incentive is volume. And when the volume of real hand-raisers isn't enough to hit the number, the playbook writes itself: gate a whitepaper, count the downloads, adjust the engagement scoring until those downloads qualify as MQLs, and ship them to sales.

Target hit. Pipeline unchanged.

I see this everywhere. Marketing can't generate enough high-intent leads to hit their MQL number, so they start manufacturing MQLs through content downloads and loose scoring thresholds. Sales gets a pile of "leads" that are really just people who wanted to read something. SDRs burn hours chasing contacts who have no intention of buying. And then everyone sits in a pipeline review arguing about lead quality.

The worst part: this isn't a failure of the marketing team. It's the predictable outcome of the incentive structure. Give smart people a volume target, and they'll find the most efficient way to hit it. If that means lowering the bar on what counts as an MQL, that's what they'll do.

The Definition That Always Shifts

Here's another thing I keep running into. Ask three people at the same company what an MQL is, and you'll get three different answers.

Is it a lead score threshold? A specific action like a demo request? A content download from someone at a target company? It depends on who set the definition, when they set it, and how much pressure the team was under at the time.

MQL definitions drift. When the target is comfortable, the definition stays tight. When the target feels unreachable, the definition loosens. I've seen companies redefine their MQL criteria mid-quarter because the number wasn't tracking. At that point, you're not measuring marketing performance. You're negotiating what counts as success after the fact.

Why Pipeline Generated Is the Right Target

When marketing's primary accountability is Pipeline Generated, the decision-making changes fundamentally.

Instead of asking "what campaign generates the most leads?", the team asks "what generates pipeline in the next few months?" Instead of optimizing for form fills, they optimize for the quality of conversations that reach sales. Instead of shipping everything to SDRs and hoping for the best, they think about whether a lead is actually ready for a sales conversation.

Pipeline Generated forces marketing to care about what happens after the handoff. And that's the point.

The CRO's concern was that marketing doesn't fully control Pipeline Generated because sales has to follow up the leads. To me, that's a feature, not a bug. It creates shared accountability. Marketing has to deliver leads worth working. Sales has to actually work them. Neither side can point fingers without the other side's cooperation.

The alternative, where marketing ships MQLs and washes their hands, is comfortable but lazy. It lets marketing celebrate "hitting their number" while pipeline stays flat. It lets the entire team avoid the harder conversation about whether the leads are any good and whether sales is following up properly.

"But Marketing Needs a Leading Indicator"

Fair point. Pipeline Generated is a lagging metric. By the time you know Q2 pipeline is short, the quarter is almost over. Marketing needs something they can monitor weekly to course-correct.

Here's where MQLs actually belong: as a diagnostic metric, not a target.

Think of it like this. A doctor monitors blood pressure, but the goal isn't "achieve 120/80." The goal is "keep the patient healthy." Blood pressure is one signal among many that helps the doctor understand what's happening in the system. If blood pressure becomes the target, people start optimizing for the number at the expense of everything else.

MQL volume, conversion rates by source, time from first touch to hand-raise... all useful diagnostics. Monitor them weekly. But don't put them on a marketing leader's performance review as the number they're accountable for. The moment MQLs become a target, they get gamed. Keep them as a way to research and identify issues in your funnel.

"Won't This Over-Index on Bottom of Funnel?"

Yes, this is a real risk. If marketing only gets credit for pipeline, the temptation is to push demo request ads, aggressive retargeting, "book a call" everything. That works short-term, but it starves the top of the funnel. Six months later you're wondering why there's no new pipeline, and it's because nobody was doing the awareness and education work.

The answer isn't adding an MQL target back. It's pairing the Pipeline Generated target with top-of-funnel health metrics on the diagnostic dashboard. Two that are actually measurable and hard to game:

Branded search volume. Google Search Console shows you exactly how many people searched your brand name. If that number is growing, your awareness engine is working. If it's flat, you have a top-of-funnel problem regardless of what your pipeline numbers say this month.

Direct traffic trends. People typing your URL or clicking a bookmark. Between branded search and direct traffic, you have a reasonable pulse on "are more people aware of us and coming to look?"

These aren't targets. They're weather stations. You check them regularly, and when they trend down for two months, something upstream is broken.

Targets Don't Drive Performance. Systems Do.

There's a deeper point here that I think gets lost in most target-setting conversations.

Organizations put a lot of effort into debating which metric should be the target and what number to put on it. Both matter, but for different reasons.

The type of target sets the orientation. Telling marketing "your job is to generate pipeline" creates a fundamentally different team than "your job is to generate MQLs." One builds a system aimed at revenue, the other builds a system aimed at form fills. That's the most important decision in this whole conversation.

Think about Kevin De Bruyne. Set him a 95% passing accuracy target and he'll hit it by playing safe short balls. His accuracy goes up, his team wins nothing, because the passes that create goals are the risky ones. Wrong type of target, wrong behavior. Set him a "chances created per 90" target instead, and suddenly he's playing the football that actually wins matches. Same player, same skill, completely different output, because the target pointed at the right thing.

The number on the target sets the scale. A €500K pipeline target and a €5M pipeline target produce completely different strategies, channel mixes, and hiring plans. The number tells your team how big to think and what kind of motion they need to build. It's not decorative.

But here's where it breaks down. Once those two things are set, spending three more weeks debating whether the number should be €1.8M or €2.1M doesn't change what the team does on Monday morning. And neither the type nor the number actually produces the result.

Even with the right target pointed at chances created, De Bruyne doesn't manufacture those chances alone. He needs teammates making runs, a manager setting tactics, training sessions that rehearse the patterns, weekly analysis of what's working. The target told him what to aim at. The system around him produced the output.

The System That Replaces MQL Targets

If MQLs aren't the target and Pipeline Generated is, you need a way to monitor whether the engine is healthy. Not a single number, but a layered view that tells you where things are working and where they're breaking.

One output target: Pipeline Generated (€ value of qualified pipeline created per quarter). This is what the marketing leader is accountable for.

Then a diagnostic dashboard organized in layers:

The dashboard tells a story when you read it top to bottom. If pipeline is short, check demand capture. If capture looks fine but pipeline is still short, the problem is downstream in sales execution. If capture is declining, look at demand creation. If everything upstream is declining, your top of funnel is broken.

This replaces the obsession with individual metric targets. You're not optimizing one number. You're keeping the system healthy.

The Handoff: SAL, Not MQL

If Pipeline Generated is the target and the diagnostic dashboard monitors the system, you still need a clear moment where marketing says "this one's ready" and sales says "I agree." That's where the Sales Accepted Lead comes in.

In the HubSpot lifecycle I use, SQL is the handoff moment: the buyer has signaled explicit willingness to engage. SAL is sales' acceptance, within 24-48 hours: "yes, this is worth my time to work." Opportunity is the post-discovery moment, once a Deal gets created in the CRM. That might take 2-3 weeks. I've written up the full MQL vs SQL vs SAL framework as its own piece.

SAL matters more for the marketing-sales interface because of speed. It forces sales to actually look at what marketing sent and make a call, rather than letting leads sit in a queue for two weeks and then complaining they were all cold.

The acceptance criteria should be simple. Something like: the company fits the ICP, the contact is a decision-maker or strong influencer in the relevant function, and the lead took a high-intent action (demo request, pricing inquiry, or direct outreach). If all three are met, sales accepts and books a meeting within 48 hours. If a criterion is missing, sales rejects with a documented reason. That rejection reason is the feedback loop that helps marketing calibrate what they're sending.

The SLA That Actually Works

A handoff protocol only works if both sides actually stick to it. The 48-hour acceptance, the documented rejection reasons, the calibration loop: all of that falls apart the moment one side treats it as optional. Which is why you need a shared agreement that makes the commitments explicit.

The formal version, the 20-page document nobody reads, doesn't work. But a lightweight version with three simple commitments does.

That weekly sync is where the real value lives. Not the SLA document. The conversation. It's the feedback loop that keeps the system honest and both sides accountable. The moment someone turns this into a Salesforce workflow with 14 required fields and a mandatory disposition code, you've killed it. Keep it lightweight or don't do it at all.

What I'd Actually Recommend

If you're a founder, CRO, or marketing leader and your team is currently chasing an MQL target, here's what I'd do.

Start having this conversation toward next quarter. This isn't a switch you flip overnight. Moving from an MQL target to a Pipeline Generated target requires alignment between marketing, sales, and leadership. It needs preparation: agreeing on what counts as pipeline, how marketing gets credit, what the handoff looks like. Don't try to change it mid-quarter.

Make Pipeline Generated the primary marketing target. Not the only metric. The primary accountability metric. The thing the marketing leader reports to the board on.

Demote MQLs to diagnostic. Keep tracking them. Use them to understand what's happening in your funnel. But take them off the target slide. The moment they stop being a target, the incentive to game them disappears.

Implement a SAL handoff with simple acceptance criteria. Three criteria, clear and specific. Sales accepts or rejects within 48 hours with a reason. This creates the feedback loop that MQL definitions never could.

Run a weekly 30-minute sync between marketing and sales. Review what was passed, what was accepted, what converted. This is the operating system that actually drives performance. Not the target number on a quarterly plan.

And if you're looking for more on how to structure the demand motions that feed this system, the three-lane model for demand capture, demand creation, and outbound splits them into distinct lanes with different owners and timelines.