Demand Generation

MQL vs. SQL: Definitions, Examples and the Handoff

Marketing says it sent sales 400 qualified leads last quarter. Sales says maybe 20 were worth a call. Both teams are looking at the same CRM, and both think the other is wrong.

That argument almost always comes down to 2 terms: MQL and SQL. When the definitions are vague, every handoff becomes a fight. When they’re clear and agreed, marketing knows what to produce and sales knows what to expect.

Here’s what each term means, how they differ, how to set the line between them and what to measure once you do.

The short answer

A marketing qualified lead (MQL) is a lead that marketing has judged ready for sales, based on who they are and what they’ve done. A sales qualified lead (SQL) is a lead that sales has reviewed and accepted as a potential customer worth active pursuit.

The MQL is marketing’s call. The SQL is sales’ call. The handoff between them is where most pipelines leak.

What a marketing qualified lead is

HubSpot’s definition is a clean starting point. A marketing qualified lead is “a contact or company that your marketing team has qualified as ready for the sales team” (HubSpot Knowledge Base).

In practice, an MQL usually meets 2 kinds of criteria:

Fit. The person and company match your ideal customer. Right industry, right company size, right job title, in a region you serve.

Engagement. They’ve done things that suggest interest. Visited key pages, downloaded a guide, attended a webinar, opened several emails or requested pricing.

Most teams turn these into a lead score. A contact earns points for fit and for actions, and crosses into MQL at a set threshold.

MQL examples

• A VP of Operations at a 300-person manufacturer downloads your buyer’s guide and returns twice to your pricing page.
• A marketing director at a SaaS company attends your webinar and asks a question in the chat.
• 3 people from the same target account visit your case studies in one week.

What a sales qualified lead is

HubSpot defines an SQL as “a contact or company that your sales team has qualified as a potential customer.” The key word is sales. An SQL has passed a human check, usually a first call or a careful review.

Sales teams often qualify against a framework like BANT (budget, authority, need, timing) or a fuller one like MEDDICC. The questions are some version of:

• Do they have a problem we solve?
• Is the person we’re talking to involved in the decision?
• Is there a reason to act in the next few months?
• Could they afford a solution like ours?

SQL examples

• The VP of Operations takes a discovery call and confirms they’re replacing their current vendor next quarter.
• The marketing director books a demo and brings their CFO.

Why the MQL model is under pressure

The MQL has taken a lot of criticism, and the data explains why. Forrester has found that fewer than 1% of leads convert to closed deals, and has urged B2B teams to move away from MQL-driven processes (Forrester).

The core problems:

One person rarely buys alone. B2B purchases involve buying groups. An MQL tracks one contact’s clicks, while the decision sits with 5 or 6 people.

Engagement isn’t the same as buying intent. A student researching a report and a buyer with a budget can rack up the same score.

Buyers decide before they talk to you. In 6sense’s 2025 Buyer Experience Report, 94% of buying groups ranked their preferred vendors before first contact with a seller (6sense). By the time a lead hits MQL, the shortlist may already be set.

Keep MQLs, but treat each one as a signal for sales to look closer. Judge it alongside account-level activity, and stop paying marketing on the raw count.

How to set the MQL to SQL handoff

Most handoff problems come from definitions nobody wrote down. Fix that in 5 steps.

1. Agree on the ideal customer first

Sit marketing and sales in one room and agree on the companies and roles you want. Industry, company size, region, tech stack, job titles. If the 2 teams disagree here, no scoring model will save you.

2. Define MQL with fit and intent

Set a fit floor: leads outside your ideal customer never become MQLs, however active they are. Then weight high-intent actions more than light ones. A pricing page visit or a demo request should count far more than a blog read.

3. Define SQL in writing

Write down what sales must confirm before a lead becomes an SQL. Keep it to 3 or 4 criteria. Make it a required field in the CRM, so the stage can’t change without it.

4. Set a service level agreement

A service level agreement sets what each team owes the other. Marketing commits to a number of MQLs at an agreed quality. Sales commits to follow up within a set time, say 1 business day, and to mark every MQL as accepted or rejected with a reason.

5. Close the loop

Rejected MQLs carry useful data. Review the reasons every month. If sales keeps rejecting leads from one campaign, change the campaign or the score. Leads that aren’t ready go back to nurturing.

What to measure

Track the stages as a funnel, and look at conversion between each one:

The last 2 matter most. A campaign that brings 50 MQLs and no pipeline is worth less than one that brings 10 MQLs and 2 deals. Our lead generation calculator helps you work backward from a revenue goal to the leads you need at each stage.

Where account-based marketing fits

If you sell to a defined list of target accounts, consider qualifying accounts as well as people. Track engagement across everyone at the account, and flag the account to sales when several people show interest. This is the approach behind account-based marketing, and it fits how buying groups make decisions.

Many teams now run both: MQLs for inbound leads from outside the target list, and account-level signals for the named accounts that matter most.

MQL vs. SQL in one line

An MQL is marketing saying “this one looks ready.” An SQL is sales saying “we agree, and we’re pursuing it.” Write both definitions down, agree on them together and measure what happens after the handoff.

Getting this right is part of the broader shift from lead generation to demand generation. If you’d like help setting definitions, scoring and the handoff between your teams, contact us. Tell us how leads flow from marketing to sales today, and we’ll show you where they’re getting stuck.

FAQs

What comes first, MQL or SQL?

MQL comes first. A lead becomes an MQL when marketing judges it ready for sales. It becomes an SQL once sales reviews it and accepts it as an opportunity to pursue.

What is a good MQL to SQL conversion rate?

It varies widely by industry, deal size and how strict your MQL definition is. Track your own rate over time and look at it by source. A rising rate usually means marketing and sales agree better on what “ready” means.

What is a SAL?

A sales accepted lead (SAL) is a step some teams add between MQL and SQL. It means sales has accepted the MQL for follow-up but hasn’t qualified it yet. It helps track whether sales is reviewing leads at all.

Who should own lead scoring?

Marketing usually builds and maintains it, but sales should help set the criteria and review results each quarter. A score that sales doesn’t trust gets ignored.