MQL vs SQL: Differences and How to Define Each

MQL vs SQL is one of the most argued definitions in B2B go-to-market, and most of those arguments happen because the two terms were never formally agreed on. If marketing and sales are fighting over lead quality, the fix isn't better CRM hygiene or a new scoring tool. It's a shared written definition that both teams sign off on.

What is an MQL?

A marketing qualified lead (MQL) is a lead that has crossed an explicit interest threshold marketing agreed on, but is not yet sales-ready. The threshold is typically a combination of buyer-fit signals (company size, industry, job title) and behavioral signals (page visits, content downloads, webinar attendance) that together suggest real intent.

What is an SQL?

A sales qualified lead (SQL) is a lead a sales rep has reviewed and accepted as a real prospect worth pursuing. It means the rep believes the lead has a confirmed need, decision-making authority, and realistic timing to buy. The key word is "accepted": an SQL is a human judgment call, not just a score.

MQL vs SQL at a glance

Key Facts

Key Facts: MQL vs SQL

• LinkedIn's 2024 B2B Marketing Benchmark found that, on average, only 25-30% of MQLs convert to SQLs across B2B companies, with top-quartile teams achieving 35-40%. (LinkedIn, 2024)
• Forrester's B2B Revenue Waterfall remains the most-cited framework for the MQL-SAL-SQL handoff flow, with the SAL stage as the critical accept/reject gate. (Forrester, 2023)
• Gartner's 2024 CSO survey reported that sales-marketing alignment on lead definitions is the single highest-impact lever for improving pipeline conversion rates. (Gartner, 2024)

The lead lifecycle: where MQL and SQL fit

Lead lifecycle stages typically run through seven stages. Understanding where MQL and SQL sit within that funnel helps both teams understand who owns what.

• Visitor -- someone who lands on your website or content with no identity attached.
• Lead -- a visitor who has shared contact info (form fill, event registration, etc.).
• MQL -- a lead who has hit the agreed interest and fit threshold; marketing passes it to sales.
• SAL (Sales Accepted Lead) -- a lead a rep has reviewed and acknowledged. The SAL stage is the handoff receipt: the rep hasn't worked it yet, but they've confirmed it's worth working.
• SQL -- a lead the rep has qualified with a discovery call or structured criteria (BANT, MEDDIC, etc.) and accepted as a real prospect.
• Opportunity -- an SQL with a defined deal: budget confirmed, next step agreed, pipeline stage set.
• Customer -- a closed-won deal.

The gap between MQL and SQL is where most pipeline leaks happen. Without a SAL stage, you don't know if the problem is lead quality (marketing) or rep follow-through (sales).

How to define an MQL

An MQL definition that both teams respect needs to be built jointly, not imposed by marketing. Here's a five-step approach:

Step 1: Pick the 2-3 buyer-fit signals

Choose the firmographic or demographic attributes that describe your ideal customer profile (ICP). Common options: company revenue range, headcount, industry vertical, job title or seniority, geography. Cap it at three so the scoring stays legible.

Step 2: Pick the 2-3 intent signals

Intent signals are behavioral events that suggest active interest. Choose events tied to real buying intent, not passive consumption. Strong signals: visited pricing page, booked a demo, viewed 3+ product pages in 7 days, downloaded a bottom-of-funnel asset. Weak signals: opened a newsletter, visited the homepage once.

Step 3: Set a score threshold

Assign point values to fit and intent signals, then set the minimum score that triggers MQL status. A common model: fit score (0-50 points) + behavioral score (0-50 points) = 100-point total; MQL at 60+. Run the threshold against 3 months of historical data before going live. If it flags more than 20% of your leads as MQLs, it's too loose.

Step 4: Agree the SLA with sales

An MQL without a lead response time SLA is just a number in a database. Sales needs to commit to reviewing every MQL within a defined window (typically 24 hours for inbound, 48 hours for outbound-assisted). Marketing needs to commit to flagging MQL rejections and using the feedback to improve lead scoring.

Step 5: Review monthly

Lead scoring models go stale. Buyer behavior shifts, your ICP evolves, campaigns change. Build a monthly review cadence where marketing and sales compare MQL-to-SQL conversion rates by source, segment, and scoring band. Adjust thresholds based on data, not gut feel.

Example: Acme SaaS defines an MQL as: ICP fit score of 60 or above (company 50-500 employees, SaaS or tech industry, VP or above title) AND at least one of: booked a demo, viewed the pricing page twice in 7 days, or downloaded the ROI calculator.

How to define an SQL

An SQL definition gives sales a consistent gate to apply before opening a deal. Without it, every rep qualifies differently, and pipeline coverage becomes meaningless.

Step 1: Pick a qualification framework (BANT, MEDDIC, etc.)

Lead qualification frameworks like BANT (Budget, Authority, Need, Timeline) or MEDDIC (Metrics, Economic Buyer, Decision Criteria, Decision Process, Identify Pain, Champion) give reps a consistent checklist. Pick one and train to it. BANT works well for straightforward transactional sales. MEDDIC fits complex enterprise deals where multiple stakeholders influence the outcome.

Step 2: Decide minimum fit criteria

Not every BANT box needs to be checked, but some are non-negotiable. Decide: what is the minimum ICP fit a lead needs to qualify as an SQL? Typical minimums: headcount above a certain floor, budget range that covers your deal size, decision-maker or strong influencer in the contact.

Step 3: Decide minimum interest criteria

Interest is what separates a qualified lead from a qualified prospect. A lead that fits your ICP but has no active need isn't worth opening a deal on. Minimum interest criteria might include: acknowledged a specific pain point on discovery, has a project or initiative tied to your solution, has a decision timeline in the next two quarters.

Step 4: Document rejection reasons

Every rejected SAL should carry a structured rejection reason. Common categories: no budget, wrong authority level, no active need, bad timing, already with a competitor. This data feeds back to marketing to improve lead nurturing programs and ICP targeting.

Step 5: Set a 24-hour SLA for outreach

Once a lead hits SQL status, the clock starts. Response speed drops conversion rates dramatically. Build the 24-hour SLA into your CRM workflow so reps get automatic reminders and managers can monitor compliance.

MQL-to-SQL conversion: what is a good rate?

The MQL-to-SQL rate measures what percentage of leads marketing qualifies that sales actually accepts.

MQL-to-SQL rate = SQLs generated / MQLs passed to sales

Industry benchmarks for B2B SaaS:

• Top quartile: 35-40%
• Median: 25-30%
• Below average: under 15%

If your rate is below 15%, the most common culprits are: MQL threshold set too low, poor ICP targeting in campaigns, or no rejection feedback loop from sales to marketing. If it's above 40%, check whether the MQL bar is too tight and you're undersending leads.

A low MQL-to-SQL rate is almost always a shared problem. Marketing may be generating volume over quality. But sales may also be cherry-picking leads or applying inconsistent criteria. The only way to diagnose it is to track rejections by reason and review them jointly.

Common MQL / SQL mistakes

• Chasing volume over quality. Inflating MQL counts to hit a metric makes the SQL rate look worse and erodes sales trust in marketing leads.
• No SLA on MQL review. MQLs that sit unreviewed for days lose intent. A lead who booked a demo and got no call for 72 hours has already moved on.
• Missing rejection feedback loop. If sales can't reject an MQL with a reason code, marketing has no signal to improve. The feedback loop is what makes lead management a system rather than a one-way conveyor.
• No shared dashboard. Marketing watches MQL volume. Sales watches pipeline. Without a shared view that shows MQL-to-SQL-to-opportunity, neither team sees the full picture.
• Scoring that never gets updated. A scoring model built in year one reflects year-one buyer behavior. If you haven't touched it since, it's almost certainly wrong.
• Skipping the SAL stage. Without a formal accept/reject handoff, you can't tell whether pipeline problems are a lead quality issue or a sales execution issue.

How marketing and sales should align on definitions

Getting to a shared MQL/SQL definition isn't a one-time meeting. It's an ongoing operational rhythm. Here's what actually works:

1. Weekly handoff review. A 30-minute standing meeting where marketing and sales review the prior week's MQL-to-SQL conversions, rejections, and rejection reasons. Keep it focused on data, not blame.
2. Shared dashboard. Both teams should see the same funnel view: MQLs created, SALs accepted, SQLs opened, opportunities created, closed-won. Use it to spot where leads are dropping.
3. SLA on response time. Write the MQL response SLA into the CRM workflow. Build escalation alerts for reps who miss the window. Track compliance as a sales operations metric.
4. Joint rejection taxonomy. Marketing and sales agree in advance on the rejection reason codes. This prevents reps from using vague reasons like "not a good fit" that give marketing nothing to act on.
5. Quarterly re-scoring. Every quarter, pull the MQL-to-SQL rate by scoring band and ICP segment. Adjust the thresholds to reflect what's actually converting. This is how scoring stays accurate over time.

Frequently asked questions

What is the difference between an MQL and an SQL?

An MQL is a lead that marketing has flagged as meeting an agreed interest and fit threshold. An SQL is a lead that sales has reviewed, qualified, and accepted as a real prospect. The MQL is based on automated scoring. The SQL is a human judgment call made by a rep.

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

For B2B SaaS, the median is 25-30%. Top-quartile teams hit 35-40%. Anything below 15% usually means the MQL threshold is too loose, ICP targeting is weak, or there's no rejection feedback going back to marketing. Anything above 40% may mean the MQL bar is too tight and you're undersending leads to sales.

What is a SAL and how does it fit?

A SAL (Sales Accepted Lead) is the stage between MQL and SQL. When a rep receives an MQL, they review it and either accept it (SAL) or reject it with a reason code. The SAL stage makes the handoff auditable and separates lead quality problems from sales execution problems. Without it, marketing and sales have no shared data to diagnose conversion failures.

Who owns the MQL, and who owns the SQL?

Marketing owns the MQL: they define the threshold, run the scoring, and are responsible for MQL volume and MQL-to-SQL rate. Sales owns the SQL: reps set the qualification criteria (within the agreed framework), review inbound MQLs, and are responsible for SQL-to-opportunity conversion. Shared ownership of the handoff SLA sits with revenue operations or whoever runs the weekly alignment meeting.

How is an SQL different from an opportunity?

An SQL is a qualified lead that sales has accepted. An opportunity is a deal that has been opened in the CRM with a defined stage, expected value, and next step. An SQL becomes an opportunity when the rep has confirmed budget and opened a formal deal record. Not every SQL becomes an opportunity: some get disqualified during discovery before a deal is ever opened.

---

The marketing-sales handoff will keep generating friction as long as MQL and SQL stay loosely defined. Nailing both definitions is one of the highest-leverage moves available to a revenue team. A shared definition, a SLA, a rejection taxonomy, and a weekly review cadence: that's the whole system. Start there, and the blame game mostly stops on its own.