The difference between MQL and SQL

Carel Schrier Carel Schrier
1 Jul 2026 - 7 min leestijd

The difference between an MQL and an SQL lies in the qualification. A Marketing Qualified Lead (MQL) shows enough interest through marketing to justify follow-up, but is not yet sales ready. A Sales Qualified Lead (SQL) is qualified by sales as sales ready and is actively followed up by a rep.

Almost every B2B team uses the terms MQL and SQL, but few teams have defined them precisely. That is exactly where leads get stuck: marketing throws a list over the fence, sales finds half of it not sales ready, and nobody can see where it goes wrong. This article lays out the difference, places MQL and SQL within the full lifecycle, and explains at what point you hand over a lead.

The difference between MQL and SQL in one table

An MQL and an SQL are both qualified leads, but they are assessed by different teams and on different signals.

MQL (Marketing Qualified Lead)SQL (Sales Qualified Lead)
Who qualifiesMarketingSales
Based on whatProfile (fits your ICP) plus behaviour (interest signals)Concrete buying intent and willingness to talk
Typical signalsWhitepaper download, repeat visits, email clicks, score threshold reachedDemo request, pricing enquiry, budget and timeline confirmed
Ready forFurther nurturing or sales contactActive follow-up by a rep
OwnerMarketing, until the SQL thresholdSales

In short: an MQL is a promise, an SQL is an agreement to proceed. The MQL says "this person fits us and shows interest". The SQL says "sales has established that a buying conversation is possible here".

The full lifecycle: from subscriber to customer

MQL and SQL are two steps in a longer chain. In HubSpot these are called the lifecycle stages. One sentence per stage:

Lifecycle stageWhat it means
SubscriberHas signed up for content (for example a newsletter), but does not yet show buying interest.
LeadHas left details and is therefore a traceable contact, still without qualification.
MQLMarketing qualified: fits your ICP and shows enough interest to justify follow-up.
SQLSales qualified: assessed by sales as sales ready and ready for active follow-up.
OpportunityA concrete deal is running: there is a sales opportunity with budget, need and timeline.
CustomerThe deal is won, the contact has become a customer.

Two terms you will also often come across:

  • SAL (Sales Accepted Lead): the intermediate step between MQL and SQL. Sales has accepted the lead and is going to investigate it, but has not yet confirmed that it is sales ready. The SAL makes the handover measurable: you can see how many MQLs sales actually picks up.
  • PQL (Product Qualified Lead): a lead that qualifies through product usage, for example in a free trial or freemium model. Relevant for product-led teams, less so for classic B2B sales.

When does marketing hand over a lead to sales?

The moment of handover is not a feeling, it is an agreement. A lead moves from marketing to sales the moment it reaches the pre-agreed SQL score. That scoring model combines two things:

  1. Fit: does the profile match your ideal customer (sector, company size, role)?
  2. Intent: does the behaviour show buying signals (demo request, pricing page, repeat visits)?

As soon as fit and intent together cross the threshold, the lead belongs with sales. Not earlier, because then sales wastes time on cold contact. Not later, because then the interest cools off.

Speed is decisive here. Research by InsideSales (the classic Lead Response Management study with MIT) shows that leads followed up within 5 minutes have a multiple times higher chance of being qualified than leads that get contact after 30 minutes or longer. For high-intent leads such as demo requests, every minute counts. For low-intent leads (a whitepaper download), follow-up within the same working day is sufficient.

A simple decision tree

Use this logic to place every lead:

  • Does not fit your ICP? No MQL. Keep it in nurturing or disqualify.
  • Fits your ICP, but low intent? MQL. Marketing keeps nurturing until intent rises.
  • Fits your ICP and high intent (demo, pricing enquiry)? Straight to sales as an SQL. Follow up within 5 minutes.
  • Sales picks it up but doubts sales readiness? SAL. Sales investigates and promotes to SQL or sends it back to marketing with a reason.

How do you know if your MQL and SQL definition holds up?

The best test is the acceptance rate: what percentage of your MQLs does sales accept as an SQL? A common rule of thumb from RevOps practice: if MQL-to-SQL acceptance is structurally below 30%, your scoring model is broken. Marketing then sends through leads that sales does not recognise as sales ready, and the handover gets stuck in discussion.

A healthy system has three things in place:

  • One shared definition of MQL and SQL, agreed by marketing and sales together.
  • A scoring model that combines fit and intent, not just pageview counts.
  • A feedback loop: sales gives a reason for every rejected lead, so the model learns.

Miss one of those three and you get the classic picture: marketing reports record numbers of MQLs, sales complains about lead quality, and revenue does not move.

Frequently asked questions

What is the difference between an MQL and an SQL?

An MQL is marketing qualified based on interest and profile, but not yet sales ready. An SQL is sales qualified and ready for active follow-up by a rep. The difference determines which team holds the lead and what action follows.

When should marketing hand over a lead to sales?

The moment the lead reaches the agreed SQL score, which combines fit (fits your ICP) and intent (buying signals). Speed counts: high-intent leads such as demo requests are ideally followed up within 5 minutes.

What is a SAL and a PQL?

A SAL (Sales Accepted Lead) is the intermediate step in which sales has accepted an MQL but not yet confirmed it as sales ready. A PQL (Product Qualified Lead) qualifies through product usage, for example in a free trial, and is mainly relevant for product-led teams.

Do you work with BANT or MEDDIC to qualify SQLs?

That depends on your deal size. A light qualification approach for SMB and transactional deals, a more extensive one for mid-market and enterprise. We do not prescribe a fixed framework, but adapt it to your sales cycle, often a lighter variant than the textbook version.

A working MQL and SQL definition stands or falls with the routing underneath it. We set up your scoring model, MQL and SQL thresholds and automated handover on your HubSpot foundation. See how that works at Lead routing and qualification.