An MQL, a marketing qualified lead, has shown interest — downloaded something, attended a webinar, visited pricing pages repeatedly. An SQL, a sales qualified lead, has been checked against real buying criteria — budget, authority, need, and timing — and is ready for an actual sales conversation. The difference is verification: an MQL is a guess based on behavior; an SQL is a lead someone has actually confirmed.


What makes a lead an MQL instead of just a visitor?

Marketing scores behavior signals — page visits, content downloads, email engagement, time spent on a pricing page — against a threshold the team has agreed represents genuine interest. Crossing that threshold makes someone an MQL. It does not mean they can buy, or even that they've fully identified their own problem yet, only that they've engaged enough with the content to be worth a closer, human look.

What turns an MQL into an SQL?

A real qualification conversation, or a set of verified facts, typically covering the same ground a lead-scoring system already checks before anyone picks up the phone:

  • Fit — are they genuinely the buyer this business serves, not just someone who found the content interesting?
  • Intent — did their behavior show a real, specific problem, not idle curiosity or research for someone else's decision?
  • Capacity — can they actually pay for this, at the price the business actually charges?
  • Timing — is there a real deadline or trigger event pushing an actual decision this quarter, not eventually?

An SQL has cleared all four of these. An MQL, at best, has cleared the first two.

Why does this distinction matter enough to formalize in writing?

Because the alternative is a sales team burning real hours on leads that were never going to close, while a marketing team gets blamed for "bad leads" that were never actually screened for the things that make a lead sales-ready in the first place. HBR's research on lead response time found firms contacting a lead within an hour of an inquiry were far more likely to qualify it than firms that waited even a single hour longer — but response speed only pays off once the lead is genuinely worth a fast response. Skipping the MQL-to-SQL check and routing every single form-fill straight to sales doesn't remove the wasted time, it just relocates it downstream, onto more expensive people.

What goes wrong when marketing and sales don't agree on the definitions?

Marketing reports a growing MQL count every month as proof of a healthy pipeline. Sales reports the exact same leads as unusable, over and over. Both teams are right, because they're measuring two completely different things under the same label. The fix isn't more leads, and it isn't a better lead-scoring tool either — it's a single, written definition both teams actually use and agree on in advance, reviewed the same disciplined way a sales pipeline gets reviewed: on a fixed weekly cadence, against the same four criteria, every single time, with no exceptions made under deadline pressure.

How do you know your MQL-to-SQL definition is actually working?

Track the real conversion rate from MQL to SQL over time, broken out by source. A source that generates high MQL volume but a stubbornly low SQL conversion rate isn't actually generating better leads for the business — it's just generating more of the same unqualified ones, faster, which is a genuinely different and usually more expensive problem to have than too few leads in the first place.

Should the threshold ever change?

Yes — revisit it quarterly. A qualification bar set when the business had excess sales capacity and needed volume looks very different from the right bar once the team is at capacity and needs precision instead. Leaving the definition frozen while the business's real constraints change underneath it is how a once-sensible system quietly stops fitting reality.

As Avi Vatsa puts it: "Most MQL-to-SQL arguments aren't really about the leads. They're a symptom of marketing and sales never sitting down together and writing the same four-question standard down." That single written definition, revisited on the same schedule as everything else in the pipeline, is usually worth more than any new lead-scoring tool a business could buy instead.


About the author

Avi Vatsa — CEO, Exchange Four Agency

Avi Vatsa is CEO of Exchange Four Agency, where he leads the team that installs and runs AI-leveraged revenue systems for owner-led companies. His background spans law, technology, and marketing; he also co-founded Dialora, an AI voice-agent platform for automated lead capture and booking. (Marketer of the Day #1411) · LinkedIn

Last reviewed: 11 September 2026