MQL vs SQL: The Difference and How to Hand Off Leads

MQL vs SQL looks like a naming question until sales stops calling marketing’s leads.

Marketing reports 500 MQLs for the quarter. Sales works through a few dozen, reaches students and job seekers, and gives up on the rest. The real buyers in that list never get a call.

I’ve watched this handoff from the sales and CRM side, and now from B2B marketing. Below you’ll find plain definitions of each stage and a lead scoring model you can copy. You’ll also get the SLA that stops leads going cold, and why the MQL alone can’t predict a deal.

First, the definitions. In my experience, marketing and sales usually hold different ones without realizing it.

What Is the Difference Between MQL and SQL?

The difference between an MQL and an SQL is who qualified the lead and how close the buyer is to deciding. A marketing qualified lead (MQL) fits your target profile and has engaged enough for marketing to flag it. A sales qualified lead (SQL) has been reviewed by sales and confirmed as ready for a sales conversation.

	MQL	SQL
Who qualifies it	Marketing, usually through a scoring model	Sales, after review or a first call
Typical triggers	Webinar attendance, repeat product page visits, content downloads	Demo request, pricing question, confirmed need and timeline
Buyer stage	Researching the problem	Comparing solutions
Next step	Nurture, or route to sales for review	Discovery call and a new opportunity
Main risk	Volume with no buying intent behind it	Over-qualifying and slowing good deals down

Look at the first row again. If marketing writes both definitions alone, sales treats the SQL label as marketing’s opinion, and the leads get ignored either way.

Arguments between the two teams almost always start at the MQL stage, so that’s the one to get right first.

What Is a Marketing Qualified Lead?

A marketing qualified lead is a contact who matches your ideal customer profile and has shown enough interest for marketing to flag. Both parts have to be true at once.

Fit tells you whether the company could buy. It comes from firmographic details like industry, headcount, and region, plus technographic signals like the tools a company already runs.

Engagement tells you whether the person is paying attention. These are the actions I’d count toward MQL status:

• Downloading a gated guide or template after reading two or more related posts.
• Attending a live webinar and staying past the halfway mark.
• Visiting product or integration pages three or more times in one week.
• Clicking through a nurture email to a use-case or comparison page.

One ebook download should never create an MQL by itself. Students, consultants, job seekers, and competitors all download ebooks.

A student writing a thesis on marketing automation will grab every guide you publish. Your scoring model will adore them.

What to do: Require at least one fit signal and one engagement signal before any lead becomes an MQL. No fit means no MQL, however many points the behavior earns.

The MQL is marketing’s judgment call. The SQL is where sales signs its own name.

What Makes a Lead Sales Qualified?

A sales qualified lead has been checked by sales and accepted as a potential deal. Leads get there in one of two ways.

The first is a direct hand-raise: a demo request, a “contact sales” form, a pricing question, or a reply asking about setup. These leads should skip the MQL stage entirely.

(Parking a demo request in a nurture sequence is a polite way to lose the deal.)

The second is a short qualifying call. You might use BANT, MEDDIC, or your own checklist. Any lead qualification framework worth using answers three questions:

1. Does the buyer have a real problem your product solves, in their own words?
2. Is this person part of the group that approves or shapes the purchase?
3. Is there a reason to act within two quarters, like a renewal, a new leader, or a failed tool?

Budget isn’t on that list, on purpose. Early buyers rarely know their budget, and forcing the question on a first call kills more deals than it qualifies.

A lead that passes all three gets booked for a proper discovery call, not another nurture email.

Plenty of funnels jump straight from MQL to SQL. There’s a stage in between, and leaving it out is where leads go missing.

MQL vs SQL vs SAL: Where the Sales Accepted Lead Fits

A sales accepted lead (SAL) is an MQL that a rep has reviewed and agreed to follow up. Accepting a lead means committing to outreach. Confirming a deal comes later, at the SQL stage.

The full sequence runs in five stages:

1. Lead: anyone who comes in through your lead generation efforts or shows up in your data.
2. MQL: the lead fits your ICP and crosses your engagement threshold.
3. SAL: a rep accepts the lead within the agreed time and starts outreach.
4. SQL: the rep confirms need, role, and timing through a call or a direct request.
5. Opportunity: a deal record exists with an estimated value and a close date.

These stages cover the middle of your wider sales funnel. Once a deal record exists, your B2B sales process takes over, from discovery through close.

The SAL exists for accountability. Without it, nobody owns the time between marketing’s handoff and the first call, and a lead can sit there for a week.

Even with clean stages, the MQL has a flaw that no stage design fixes.

Why MQLs Fail So Often

Lead-based funnels leak badly. Forrester’s waterfall benchmarks show that lead-centric processes built on MQLs convert less than 1% of inquiries into closed-won deals.

That’s fewer than one win for every 100 people who raise their hand. The same Forrester research found that over 80% of buying decisions are made by a buying group of more than three people.

Three problems sit behind those numbers:

• Scoring weights are often guesses. Is a whitepaper worth 10 points or 40? That number usually gets picked in a meeting, not pulled from closed-won data.
• One person is not the buyer. A single contact bingeing content tells you one person is curious. It says nothing about whether their company is buying.
• MQL volume becomes the target. Pay marketing on MQL count, and the threshold drifts lower every quarter. Sales notices, and trust drops.

My take: don’t kill the MQL overnight. It still works as an internal routing signal. The mistake is treating it as a promise of revenue.

The fix starts with your own closed deals, because they already show what a real buyer does before talking to sales.

How to Build a Lead Scoring Model for MQLs and SQLs

Industry templates guess at your buyer. Your closed-won history doesn’t. Build the model in six steps:

1. Pull your last 30 to 50 closed-won deals. List the company traits they share and the actions their contacts took before talking to sales.
2. Score fit and intent separately. A perfect-fit account with zero activity and a hyperactive student can share one score. Two scores keep them apart.
3. Weight the behaviors that showed up before wins. If pricing page visits appeared in your won deals and webinar attendance didn’t, weight them that way. Layer in third-party intent data to catch accounts researching your category off your site.
4. Add negative scoring. Subtract points for personal email domains, careers page visits, student titles, and companies outside your ICP. It removes junk faster than any threshold tweak.
5. Set the MQL threshold with sales in the room. Agree on the number together, then write the SQL definition in sales’ own words. If sales won’t sign it, the definition isn’t finished.
6. Recalibrate every quarter. Compare MQLs that became SQLs with the ones sales rejected. Adjust weights wherever the model and reality disagree.

Here is a starting model for a mid-market B2B SaaS company. Treat the numbers as a template, then swap in weights from your own closed-won data.

Signal	Type	Points
Company size inside your ICP range	Fit	+20
Industry on your target list	Fit	+15
Uses a tool your product integrates with	Fit	+10
Title in the buying group (director and above, or core user role)	Fit	+10
Pricing page visit	Intent	+20
Two or more product page visits in seven days	Intent	+10
Live webinar attendance	Intent	+10
Single content download	Intent	+5
Personal email domain	Negative	-20
Careers page visit	Negative	-15
Student or intern title	Negative	-30

The rule: a lead becomes an MQL at 60 points, with at least 30 of those points from fit. A demo request goes straight to sales, whatever the score says.

Fit scoring only works if your CRM records have company size and industry filled in. If half of them are blank, add an enrichment step before scoring, or your fit points are fiction.

A sharp model still wastes leads if nobody agrees on what happens after a lead crosses the line. That agreement belongs in writing.

The MQL to SQL Handoff: Write an SLA Both Teams Sign

A service level agreement (SLA) is a written deal between marketing and sales. Marketing commits to a volume of MQLs that meet the agreed definition. Sales commits to how fast and how hard it works them.

Every SLA I’d sign covers five things:

• Response time: Every MQL gets accepted or rejected within one business day. Demo requests get a same-day response.
• Minimum effort: Both teams agree how many touches across email, phone, and LinkedIn come before a lead counts as unresponsive.
• Rejection reasons: Every rejected MQL gets a reason code, like “no fit,” “wrong contact,” or “no current need.” A bare “not qualified” doesn’t count.
• Recycling rules: Leads rejected for timing go back into nurture, not the trash. They return to sales when new signals appear.
• Shared review: Both teams look at acceptance rates and rejection codes together every month.

Rejection codes are the most underrated part of lead qualification. They turn sales complaints into data marketing can act on.

In companies with a revenue operations team, RevOps usually owns the SLA and the dashboard behind it. In smaller companies, the marketing lead and the sales lead own it together.

Everything so far scores one person at a time. B2B deals don’t close that way.

Qualify Buying Groups, Not Single Leads

Several people from one account engaging at once tells you far more than one person engaging a lot. Deals close when a group agrees, so that group is what you should qualify.

Palo Alto Networks tested this. In a Forrester client story, opportunities with several people attached were eight times more likely to advance than single-contact ones.

Focusing on buying groups also brought the company bigger deals and a 17% higher closed-won rate.

You don’t need new software to start. If you already run account-based marketing, you have the target account list this needs. Three changes get you most of the way:

1. Match every lead to its account, so three contacts from one company show up as one signal instead of three scattered MQLs.
2. Flag the account, not the person, when two or more contacts engage within the same 30-day window.
3. Ask on the first sales call who else is involved, then add those people to the opportunity record.

Last, decide how you’ll know the whole setup is working.

How to Measure Your MQL to SQL Conversion Rate

Your MQL to SQL conversion rate is the share of MQLs that sales confirms as SQLs in a given period. The formula:

MQL to SQL conversion rate = (SQLs created from MQLs ÷ total MQLs) × 100

If you generated 400 MQLs last quarter and 60 became SQLs, your rate is 15%.

I’d skip published benchmarks for this one. Every company defines an MQL differently, so comparing your rate with someone else’s compares two different things.

Four numbers tell you more:

• The trend over time. A falling rate while MQL volume climbs means your threshold slipped.
• SQL to opportunity rate. If sales accepts leads but can’t turn them into deals, the problem sits in your SQL definition.
• Time from MQL to first touch. Slow follow-up drags conversion down before lead quality even comes into play.
• Pipeline value by MQL source. This shows which channels bring buyers and which bring readers.

That last number is also the fairest way to judge a demand generation program: pipeline created, not forms collected.

These are the questions I get most often about MQLs and SQLs.

MQL vs SQL: Where to Start This Week

Pull your last 30 closed-won deals and look at what they did before anyone talked to sales. That pattern tells you where your MQL threshold belongs.

From there, the rest follows in order. Score fit and intent separately, add the SAL stage, write the SLA, and start grouping contacts by account.

Getting MQL vs SQL right won’t fix a weak product or a bad market. It will stop your team from losing buyers who already raised their hand.

Frequently Asked Questions