An MQL is a lead marketing believes is worth a sales look; an SQL is a lead sales has looked at and agreed is worth pursuing. That is the whole distinction in one sentence, and yet it causes more friction between teams than almost anything else in the funnel.
We run qualification systems for B2B teams every day, and the MQL/SQL boundary is where most of them quietly leak revenue. The labels are simple. The disagreements underneath them are not. This post lays out what each term means, how the handoff is supposed to work, where it breaks in practice, and the criteria that make the distinction genuinely useful instead of just another stage in a CRM nobody trusts.
What an MQL actually is
A Marketing Qualified Lead is a contact who has shown enough interest, and enough fit, that marketing is willing to say "this one is worth a salesperson's time." That willingness is the key idea. An MQL is a recommendation, not a verdict.
In most setups, MQL status gets triggered by some mix of two things:
- Fit signals: the account looks like your ideal customer. Right industry, right size, right role for the contact. This is who they are.
- Behavior signals: they downloaded the pricing sheet, attended the webinar, hit the demo page three times this week. This is what they did.
The trouble starts when teams score only on behavior. A student researching a paper can trip every behavioral wire you set. Someone who fits perfectly but has never clicked an email might be your best account of the quarter. Good MQL definitions weigh both, and we generally push clients to weight fit at least as heavily as activity. You can read our fuller take on that balance in the lead scoring guide.
What an SQL actually is
A Sales Qualified Lead is a lead that sales has independently examined and accepted as worth working. The important word is accepted. An SQL exists only after a human on the sales side (or a system sales trusts) has applied their own judgment and said yes.
There are two common flavors, and mixing them up causes real confusion:
- Sales Accepted Lead (SAL): sales agrees the lead is worth a first touch. A light gate.
- Sales Qualified Lead (SQL): after that first touch, there is a real, budgeted, timed opportunity worth pursuing. A heavier gate.
Some orgs collapse these into one step, others keep all three (MQL, SAL, SQL). Neither is wrong. What matters is that everyone agrees which gate they are talking about, because "SQL" in a board deck and "SQL" in a rep's pipeline are often two different animals.
The handoff: how it is supposed to work
The MQL-to-SQL handoff is a moment of transfer of responsibility, not just a status change. Here is the clean version:
| Stage | Owner | Question being answered |
|---|---|---|
| Lead | Marketing | Is anyone home? |
| MQL | Marketing | Does this look worth sales' time? |
| SAL | Sales | Do we agree it is worth a first touch? |
| SQL | Sales | Is there a real opportunity here? |
The handoff lives between MQL and SAL. Marketing hands a recommendation across; sales either accepts it or bounces it back with a reason. That feedback loop, the bounce-back with a reason, is the single most underrated part of the whole system. Without it, marketing never learns which MQLs were any good, and the definitions never improve.
Where the handoff breaks
We see the same failure points over and over.
Speed. An MQL that sits in a queue for two days is often already talking to a competitor. Interest is perishable. The gap between "marketing flagged this" and "sales touched this" is where the most value evaporates, and it is almost always longer than anyone admits.
No shared definition. Marketing scores an MQL one way, sales judges an SQL another way, and the two criteria were never written down together. Reps start ignoring MQLs wholesale because "marketing's leads are garbage," which usually means the definitions never matched, not that the leads were bad.
Volume over quality. When marketing is measured on MQL count, they optimize for count. You get more MQLs and fewer meetings, and everyone wonders why. This is a metrics problem wearing a lead-quality costume.
No round trip. Leads go marketing to sales and never come back. No disposition, no reason codes, no learning. The definitions calcify.
Behavioral false positives. As noted, activity without fit produces confident-looking MQLs that go nowhere. Enrichment helps here; knowing the account before you score it filters out a lot of noise. Our enrich product exists largely to close that gap.