MQL vs SQL: The Difference and Why It Matters

Marketing reports 400 leads in a quarter. Sales closes four deals and says the leads were junk. Both teams are looking at the same spreadsheet and reaching opposite conclusions. The fight is almost always about one thing: what counts as a real lead and when does it become sales' problem.

That line has a name. On one side sits the MQL, the marketing qualified lead. On the other sits the SQL, the sales qualified lead. Get the definitions right and the handoff between teams gets quiet. Get them fuzzy and you burn budget on the wrong contacts while reps chase people who were never going to buy.

This piece walks through what each term actually means, where the boundary should sit, and how to set the criteria so marketing and sales stop arguing about the same numbers.

What an MQL is

An MQL is a contact who has shown enough interest that marketing believes they are worth a closer look. They downloaded a guide, requested a demo, attended a webinar, or hit a behavioral threshold you defined in advance. They raised a hand. They have not been vetted as a buyer yet.

The key word is interest, not fit. An MQL might be a student writing a thesis, a competitor poking around, or a junior employee with no budget. Marketing flags them because their behavior crossed a line, not because anyone confirmed they can actually buy.

Most teams build the MQL definition from two ingredients:

  • Fit: does the contact match your ideal customer profile? Right industry, company size, role, region.
  • Behavior: what did they do? A pricing-page visit and a demo request signal more intent than a single ebook download.

A common scoring approach adds points for both and sets a threshold. Cross it, and the contact becomes an MQL. We will get to scoring later, because the threshold is where most of the trouble starts.

What an SQL is

An SQL is a lead that sales has reviewed and accepted as a genuine opportunity worth pursuing. Someone on the sales side looked at the contact, often had a conversation, and confirmed three things: there is a real need, there is budget or a path to it, and there is a reasonable chance of a deal.

The shift from MQL to SQL is a shift from probably interested to worth a rep's time. Marketing says "this person looks promising." Sales says "yes, I will work this." Until a salesperson accepts the lead, it stays on the marketing side of the fence.

Some organizations split this further. The lead marketing passes over becomes an SAL (sales accepted lead) the moment a rep agrees to look at it, and only becomes an SQL after a qualifying conversation confirms fit and intent. If your sales cycle is long or your team is large, that extra step is worth the bookkeeping. For most small teams, MQL and SQL are enough.

The handoff, step by step

The path a contact travels looks like this:

Lead stage progression A contact moves left to right through five stages: Lead, MQL, SAL, SQL, and Opportunity. Marketing owns the first two stages, sales owns the last three. Lead MQL SAL SQL Deal marketing owns sales owns
  1. A visitor converts on something (form, demo request, content download) and becomes a raw lead.
  2. Marketing scores fit and behavior. If the contact clears the bar, they become an MQL and get routed to sales.
  3. A rep reviews the MQL. If it looks workable, they accept it (SAL) and reach out.
  4. After a qualifying conversation, the rep confirms need, budget, and timing. The lead becomes an SQL.
  5. The SQL enters the active pipeline as an opportunity and starts moving toward a close.

The single most important moment is step 2 to step 3: the handoff. This is where most B2B revenue leaks. If marketing's MQL bar is too low, sales drowns in weak leads and starts ignoring the queue. If the bar is too high, good contacts sit untouched while the cost per lead climbs.

Why the distinction matters for your money

This is not vocabulary for its own sake. The MQL-to-SQL line decides three things that show up directly in your numbers.

It tells you where the funnel actually breaks. Say marketing generates 400 MQLs and only 40 become SQLs. A 10% MQL-to-SQL rate could mean two very different problems. Either marketing is sending unqualified contacts, or sales is too slow to follow up and good leads go cold. You cannot fix the leak until you know which stage is failing, and you cannot see the stages without clear definitions. If you want the full picture of how stages connect to revenue, our guide to the B2B sales funnel walks through each step.

It changes what you optimize ad spend toward. When you measure campaigns by MQL volume, you reward whatever produces the most form fills. Cheap, broad traffic wins. When you measure by SQLs and closed deals, the picture often flips: a channel with fewer but higher-fit leads beats the high-volume one. This is the core argument for measuring PPC by revenue, not clicks, and it only works if your stages are wired into the CRM.

It sets honest expectations between teams. When sales and marketing agree on what an MQL is and what an SQL is, the quarterly argument disappears. Marketing's target stops being "generate leads" and becomes "generate MQLs that convert to SQLs at X%." That single change aligns the two teams around the same outcome.

How to define the criteria

Vague definitions are the root cause of most MQL-SQL disputes. "Seems interested" is not a definition. Here is how to make them concrete.

Start from your ideal customer profile

Before behavior, fix fit. Write down the firmographics of a customer worth your sales team's time: company size range, industries, regions, and the roles you sell to. A contact who fails the fit test should rarely become an MQL no matter how much content they consume. A junior analyst at a 5-person shop reading everything you publish is engaged, not qualified.

Set behavioral thresholds, not single actions

One download is weak signal. A pattern is strong signal. Decide which combinations of actions cross your MQL line. For example (illustrative): two content downloads plus a pricing-page visit, or a single demo request, or webinar attendance plus a return visit within a week. Demo and pricing-page activity usually outweigh top-of-funnel content, so weight them higher.

A simple scoring model assigns points to fit and behavior and sets a threshold. If you have never built one, our walkthrough on lead scoring covers the mechanics. Keep the first version simple. A model nobody understands gets ignored.

Write the SQL definition as a checklist

For the SQL, agree with sales on the qualifying questions a lead must clear. Many teams use a framework like BANT (budget, authority, need, timing) or a lighter version of it. The point is not the acronym. The point is that "sales qualified" means a rep verified specific facts, not that the lead "felt good on the call."

Stage Owned by Question it answers Example trigger
Lead Marketing Did someone convert? Filled any form
MQL Marketing Do they fit and show intent? ICP match + demo request
SQL Sales Is this a real opportunity? Rep confirmed need + budget + timing

The triggers above are illustrative; set your own based on your data.

Put both definitions in a written agreement

The cleanest fix is an SLA between sales and marketing: marketing commits to a number and quality of MQLs, sales commits to following up within a set time (lead response speed matters more than most teams think). Both definitions live in one document. When a dispute comes up, you point at the document instead of relitigating it.

Common mistakes

A few patterns show up again and again.

Counting MQLs as the finish line. Marketing celebrates the MQL number, sales never converts it, and nobody connects the two. The MQL is a milestone, not a result. The result is revenue.

An MQL bar set by volume targets. When marketing has a monthly MQL quota and is short, the temptation is to lower the threshold and let weaker contacts through. The number looks fine; the SQL rate quietly collapses. Tie marketing's goal to downstream conversion, not raw count.

No feedback loop from sales. Sales rejects an MQL and the reason never gets back to marketing, so the same bad leads keep coming. A one-field "rejection reason" in the CRM fixes most of this. Review it monthly.

Treating the definitions as permanent. Your market shifts, your product changes, your scoring drifts out of date. Revisit the MQL and SQL criteria at least twice a year against actual conversion data.

Frequently asked questions

Is an MQL better than an SQL?

No, they are different stages of the same journey. An SQL is further along: a salesperson has reviewed it and confirmed it is worth pursuing. An MQL is earlier and less certain. Neither is "better"; you need both, and you need contacts to flow from one to the next.

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

It varies widely by industry, deal size, and how strict your MQL definition is. Rather than chasing a benchmark you read somewhere, measure your own rate, then work to improve it over time. If your MQL-to-SQL rate is very low, your MQL bar is probably too loose or sales follow-up is too slow. A very high rate can mean your bar is set so high that good leads never get flagged.

Who decides when an MQL becomes an SQL?

Sales does. The whole point of the SQL stage is that someone on the sales side has accepted the lead and verified it is a real opportunity. Marketing can recommend, but it cannot declare a lead sales qualified on sales' behalf.

Do small companies need both stages?

If one person handles both marketing and sales, the formal distinction matters less day to day. You still benefit from the thinking: separate "this person showed interest" from "this person is worth a serious conversation." As soon as you have separate teams, write the definitions down.

How is an SQL different from an opportunity?

An SQL is a qualified lead the moment sales accepts it. An opportunity is an SQL that has entered the active deal pipeline with a real chance of closing, often tied to a forecasted value and stage. Some teams use the terms interchangeably; the cleaner setup keeps SQL as the qualification checkpoint and opportunity as the pipeline entry.

What tools track MQL and SQL stages?

Your CRM, paired with marketing automation. Most B2B teams configure lead stages and scoring in the same system that holds their pipeline, so a contact's status updates automatically as they move from MQL to SQL to opportunity. The exact platform matters less than wiring the stages so both teams see the same status.

The takeaway

The difference between an MQL and an SQL is the difference between interested and vetted as a buyer, and the line between them is where most B2B funnels leak. Get the definitions written, agreed, and wired into your CRM, and the two teams stop fighting over the same spreadsheet.

A short checklist to act on:

  • Write an ICP-based fit definition before you score behavior.
  • Set MQL behavioral thresholds on patterns, not single actions.
  • Make the SQL definition a checklist sales actually verifies.
  • Put both in a written sales-marketing SLA with response-time commitments.
  • Add a rejection-reason field and review it monthly.
  • Tie marketing's goal to SQL conversion, not MQL volume.

If your marketing reports lots of leads but your pipeline stays thin, the problem usually hides in this handoff. We help B2B teams define their stages, connect them to revenue analytics, and find exactly where leads fall out. If that sounds like your situation, get in touch for a short review of your funnel and we will show you where the gaps are.