What Is MQL vs SQL? Definition, Handoff, and 2026 Conversion Benchmarks
An MQL is marketing's bet that a contact is worth a sales conversation. An SQL is sales confirming fit and intent, usually on a live call. Median MQL-to-SQL sits near 13%; Forrester's lead-centric waterfall closes under 1%.
A marketing qualified lead (MQL) is a contact marketing has scored as fit-plus-engagement and is willing to send to sales. A sales qualified lead (SQL) is a contact a salesperson has independently confirmed is worth working — typically after a live conversation that checks budget, authority, need, and timing. The labels are not two names for the same form fill. One is a marketing signal. The other is a sales decision. Most pipeline fights start when a team treats them as the same number.
Growth Centr publishes evergreen, research-backed analysis on go-to-market strategy for founders, marketers, and operators who need a handoff they can defend in a pipeline review, not a scoring model that quietly inflates MQLs.
HubSpot's MQL definition is the working marketing bar: a lead marketing has deemed more likely to become a customer than the rest of the list, based on pages visited, offers downloaded, CTAs clicked, and other engagement. Salesforce's MQL vs SQL explainer draws the sales line: an MQL has shown interest and is not ready to buy; an SQL has shown enough intent to enter the sales process. Forrester's B2B Revenue Waterfall is why the distinction is not semantic. In a typical lead-centric process, inquiry-to-closed-won conversion is less than 1% — fewer than one won deal for every 100 people who raise a hand.
Key Takeaways
- An MQL is marketing's judgment that a contact matches ICP and has crossed an engagement threshold. An SQL is sales' judgment that the same contact (or buying group) has confirmed fit and buying intent. Do not auto-flip MQL to SQL on a form.
- Forrester's waterfall puts lead-centric inquiry-to-close under 1%. GrowthCentr's 2026 lead-generation compilation puts median MQL-to-SQL at 13% and top quartile at 28%; a more granular waterfall (MQL → sales-accepted → SQL) compresses the combined rate to 9.8%.
- HubSpot's January 2026 demand-gen reporting, citing the 2025 Demand Generation Benchmark Survey, found 55% of B2B marketers named MQL-to-opportunity conversion a top-three priority — conversion quality, not more MQLs.
- Forrester's 2021 B2B Buying Survey (cited in the same waterfall series) found over 80% of buying decisions are made by a group of more than three people. Scoring one ebook downloader as the deal is how SQLs get rejected.
- Measure marketing on accepted SQLs, pipeline dollars, and win rate. Measure the handoff on MQL-to-SQL, speed-to-lead, and rejection reasons. Test the definition in 30 days without buying another scoring tool.
How MQL vs SQL Actually Works
The funnel is a routing problem, not a vocabulary problem.
A lead is a known contact. Someone filled a form, scanned a badge, started a trial, or got added from a list. That is identity, not qualification.
An MQL is marketing saying: this contact looks like our buyer and they did something that usually precedes a useful sales conversation. HubSpot's criteria are behavioral — pages, downloads, CTAs, social. Salesforce adds fit: product-need match and budget signals. The honest version of both is fit plus intent, written down with sales in the room. Fit without intent is a newsletter subscriber. Intent without fit is a student downloading a template.
An SQL is sales saying: we spoke (or otherwise verified), and this is a real opportunity to work. IBM's BANT — Budget, Authority, Need, Timeline — is still the default checklist for that conversation. The order matters less than the evidence. A demo request from an ICP account can skip the MQL queue and land as an SQL. A whitepaper download cannot.
The missing stage in most CRMs is the sales-accepted lead (SAL): the SDR or AE takes the MQL, does not bounce it, and agrees to work it under an SLA. MQL-to-SQL then splits into two rates — acceptance, then qualification — which is how the same company can report 13% and 9.8% without either number being a lie.
Demand generation vs lead generation sits one step upstream. Demand gen creates the memory that puts you on the shortlist; lead gen captures the hand-raiser; MQL/SQL is how you decide which hand-raisers deserve a rep. Account-based marketing inverts the unit: you qualify the account (an MQA) and the buying group, not a single MQL. Product-led growth adds a third door: a product-qualified lead (PQL) is usage evidence, which is usually a better SQL than a gated PDF.
Create the definition together, then score against it. If marketing's MQL is "score > 50" and sales' SQL is "has a project this quarter," you do not have a funnel. You have two dashboards.
MQL vs SQL vs SAL vs PQL
Four labels, four jobs. Collapse them and you will send webinar registrants to AEs and call the resulting no-shows a "sales problem."
| Dimension | MQL | SAL | SQL | PQL |
|---|---|---|---|---|
| Who decides | Marketing, against a written ICP + engagement bar | SDR/AE accepts the MQL under an SLA | Sales, after a live qualification | Product + ops, against a usage threshold |
| What it proves | Fit and enough interest to interrupt a rep | The lead was not junk; someone will work it | Budget/authority/need/timing (or your equivalent) are real | The account already got value in the product |
| Typical trigger | Pricing page + ICP firmographics; high-intent form; score threshold with a fit gate | Lead accepted in CRM within the SLA window | Discovery call, demo, or verified BANT | Activation event: seats invited, workflow completed, usage cap hit |
| Typical next step | Route to SDR/AE or nurture if timing is wrong | Outreach sequence; book qualification | Create opportunity; run the deal process | AE opens with usage, not a deck |
| Primary metric | MQL volume and MQL-to-SAL | Acceptance rate, speed-to-lead, reject reasons | SQL-to-opportunity, pipeline $, win rate | PQL-to-paid or PQL-to-opportunity |
| Failure mode | Ebook downloads counted as pipeline | Silent rejects; 42-hour median first response | SQL created from a form, never a conversation | Vanity activation that never reaches a buyer |
Salesforce's B2B SaaS examples are the practical test. Downloading a generic "best CRMs" guide is an MQL. Returning for "things to know before purchasing" or booking a demo is SQL territory. A hand-raiser (Contact Us, Request a demo) can skip MQL entirely. That skip is a feature. Forcing every demo request through a 14-day nurture because "the lifecycle must go Lead → MQL → SQL" is how you lose the 5% who are already in-market.
Forrester's objection to the whole lead object is the buying group. One person is not the buyer. Their 2021 survey put more than three people on over 80% of B2B decisions. 6sense's 2025 Buyer Experience Report (as used in our demand-gen and ABM briefs) puts the average group at 10.1, with 94% ranking a shortlist before anyone talks to sales and the first-ranked vendor winning 77% of deals. An MQL that is one champion and no economic buyer is a sample, not a deal. ABM teams rename this an MQA and refuse to pass a single contact as "the account."
2026 Conversion Benchmarks
Do not quote a single "good" MQL-to-SQL number. Quote the waterfall you actually run, on a lagged cohort.
MQL-to-SQL % = SQLs created from a cohort ÷ MQLs in that cohort × 100
Use the cohort that created the MQLs, delayed by your median time-to-SQL (often 7–21 days). Same-month SQLs ÷ same-month MQLs understates the rate in a growing funnel and overstates it in a shrinking one.
| Stage | Median (2026) | Top quartile | What a miss usually means |
|---|---|---|---|
| Visitor → lead | ~1.8% | ~4.7% | Offer/page mismatch, not "traffic quality" |
| Lead → MQL | ~28% | ~44% | Fit gate missing, or scoring too loose |
| MQL → SQL (headline) | 13% | 28% | Definition fight; sales ignoring junk; slow follow-up |
| MQL → SAL → SQL (combined) | 9.8% | ~16% | Same fight, split into accept vs qualify |
| SQL → opportunity | ~59% | ~75% | SQL was a meeting, not a qualified deal |
| Opportunity → closed-won | ~22% | ~33% | ICP, competitive, or cycle — not the MQL label |
| Inquiry → closed-won (Forrester lead-centric) | <1% | — | Structural: individuals, not buying groups |
The 13% / 28% pair is from the 2026 B2B panel compiled in our lead generation statistics (Digital Applied aggregating HubSpot, Demand Gen Report, Forrester, and LinkedIn B2B Institute sources). The 9.8% combined rate is the same publisher's more granular waterfall: MQL → sales-accepted 47.1%, SAL → SQL 31.7%. Forrester's <1% is inquiry-to-close on a lead-centric process — a different denominator, and the reason "more MQLs" can grow while revenue does not.
HubSpot's January 2026 demand-gen writing, citing the 2025 Demand Generation Benchmark Survey, is the operator tell: 55% of B2B marketers put MQL-to-opportunity conversion in their top three priorities, 52% named ROI measurement, 38% named sales-marketing alignment. Volume is not the 2026 bottleneck.
Cost makes the math rude. Median B2B cost per lead in that same 2026 compilation is $213, up from $198 in 2025. At 13% MQL-to-SQL you are paying about $1,640 per SQL before the AE starts a deal cycle. At 9.8% it is about $2,170. GrowthCentr's B2B SaaS CAC benchmarks put median payback at 16 months and new-name CAC at $1.63 of sales-and-marketing per $1 of ARR. Flooding the SQL queue with loose MQLs does not buy growth. It buys a longer payback and a worse lifetime value ratio, because reps spend the expensive hours on accounts that were never going to retain.
Channel mix moves the rate more than the CRM field. SEO- and high-intent search-sourced MQLs routinely convert several times paid-social ebook fills, because the query already implies a problem. Treat "MQL-to-SQL" as a channel metric, not a company vanity number.
AI scoring changed the top quartile, not the median. 61% of B2B teams now use AI for lead scoring, up from 23% in 2024, per the same 2026 panel. Median MQL-to-SQL barely moved. Top quartile pulled away to 28%. The mechanism is not a model. It is a tighter fit gate plus faster rejects — the model just enforces the definition humans already agreed.
The Handoff: Scoring, SLAs, and Speed
A written definition that sales never uses is a blog post. The operating system is three rules.
1. Fit gate before engagement points. Firmographics and ICP (industry, size, tech, geography, role) are a yes/no. Engagement is a score. A 200-point intern at a 12-person company that cannot pay you is not an MQL. A VP of Ops at an ICP account who hit pricing twice and requested a demo is an SQL, even if they never downloaded the ebook that your scoring model loves.
2. SLA on the accept, not the vibe. When an MQL is created, sales has a clock to accept or reject with a reason code (wrong ICP, no timing, duplicate, already in pipeline, student, competitor). No reason code means it did not happen. Recycle rejects to nurture; do not delete them and do not keep them in the SQL report.
3. Speed is the cheapest conversion lever. The MIT / InsideSales Lead Response Management study still holds: contact within five minutes and you are about 21× more likely to qualify the lead than if you wait 30 minutes. The 2026 field measurement in our lead-gen compilation is grim: median first response 42 hours, only 7% of teams inside five minutes, and one 1,000-company study found 63.5% never responded at all. You do not have an MQL quality problem if nobody calls.
What to put on the shared dashboard:
- MQLs created, by source and by ICP match (yes/no)
- MQL-to-SAL (acceptance) and SAL-to-SQL, lagged
- Median and 90th-percentile speed-to-first-touch
- Reject reasons, ranked
- SQL-sourced pipeline $ and win rate, versus outbound and expansion
- Buying-group coverage on SQLs (second contact in a different role)
If MQL volume is up 20% and SQL volume is flat, the scoring threshold moved — almost always down. Tighten the fit gate before you hire another SDR.
A 30-Day Operator Test
Do not buy a new platform. Rewrite the two sentences, put a clock on the queue, and stop sending junk.
Days 1–7 — Write the two sentences with sales in the room. MQL: "An ICP contact who did [high-intent action] or crossed [score] after passing the fit gate." SQL: "A contact or buying group a rep has spoken with and confirmed [BANT or your equivalent]." List the last 50 MQLs. Mark which ones sales would actually call. If that share is under ~30%, your MQL is a lead.
Days 8–14 — Baseline the real funnel. Last 90 days: MQL volume by source, acceptance rate, time-to-first-touch (median and p90), MQL-to-SQL on a lagged cohort, SQL-to-opportunity, win rate. Add a required reject-reason field this week. If "how did you hear about us?" is not required on opportunities, add that too — demand gen needs it as much as this handoff does.
Days 15–21 — Tighten one gate; speed up one queue. Remove one engagement event that has never predicted an SQL (the classic: any ebook, any webinar attendance, any pricing-page visit from a free-mail domain). Route demo and contact-us forms past MQL, straight to SQL/SDR with a five-minute SLA. If you have a product-led path, wire PQLs so they do not sit behind the same ebook score.
Days 22–30 — Read conversion, not volume. The test worked if MQL-to-SQL and SQL-to-opportunity rose on a smaller MQL count, and if reject reasons concentrated (wrong ICP, not "sales was busy"). If volume fell and conversion did not rise, the ICP is wrong or the offer is wrong — not the lifecycle field. Freeze the definition for 90 days before changing scores again.
Methodology
This is a definitional brief, not a survey we ran. MQL wording follows HubSpot's marketing-qualified-lead explainer. MQL vs SQL split follows Salesforce's MQL vs SQL and sales-qualified-lead pages. Inquiry-to-close <1% and the >80% / groups of 3+ buying-group figure: Forrester, The Revenue Process Alignment Series, Part 1 (14 April 2022), citing Forrester's 2021 B2B Buying Survey. 2026 funnel medians (13% / 28% MQL-to-SQL, 9.8% combined, $213 CPL, 61% AI scoring, 42-hour median response): GrowthCentr's lead-generation statistics compilation, which aggregates HubSpot, Demand Gen Report, Forrester, LinkedIn B2B Institute, MIT/InsideSales, and 2026 panel studies. HubSpot 55/52/38 demand-gen priorities: HubSpot's January 2026 demand-gen reporting citing the 2025 Demand Generation Benchmark Survey, as used in our demand-generation brief. Buying-group size, shortlist, and win-from-favorite: 6sense 2025 B2B Buyer Experience Report. CAC: GrowthCentr's Benchmarkit compilation. BANT is IBM's 1960s qualification framework. No statistic appears here unless it was on a page we fetched or on a GrowthCentr brief built from fetched pages.
Read Next
- What Is Demand Generation vs Lead Generation? Definition, Metrics, and How They Work Together
- What Is Account-Based Marketing (ABM)? Definition, Tiers, and When It Beats Broad Demand Gen
- Lead Generation Statistics 2026: 50+ Benchmarks on Cost, Conversion, and Speed
- B2B SaaS CAC Benchmarks 2026: What It Costs to Acquire a Customer
- What Is Customer Lifetime Value (LTV)? Formula, 2026 Benchmarks, and the 3:1 Rule
FAQs
1. What is the difference between an MQL and an SQL?
An MQL is a contact marketing has scored as ICP-fit plus engaged enough to interrupt sales. An SQL is a contact sales has confirmed — usually on a call — as having real buying intent and a workable BANT (or equivalent) profile. HubSpot treats MQL as marketing's vet; Salesforce treats SQL as readiness to enter the sales process. The handoff is a decision, not an automatic field change.
2. What is a good MQL-to-SQL conversion rate in 2026?
Treat 13% as the cross-industry headline median and 28% as top quartile. A combined MQL → accepted → SQL waterfall closer to 10% is also common and not a crisis by itself. Below ~10% on a lagged cohort is usually a loose MQL definition or a slow SLA, not an SDR talent problem. Above ~35% often means you are only passing demo requests and calling them MQLs.
3. Can a lead become an SQL without being an MQL first?
Yes. A demo request, contact-us form, inbound referral, or PQL from an ICP account should skip the nurture queue. Forcing every hand-raiser through Lead → MQL → SQL because the CRM lifecycle is linear is how in-market buyers wait 42 hours.
4. Is SQL the same as Structured Query Language?
No. In go-to-market, SQL means sales qualified lead. In data, SQL is the query language. Search engines mix the two; this page is the GTM definition.
5. Should we stop using MQLs?
Stop using MQL volume as the marketing KPI. Keep the stage as a routing label if it still describes a real fit-plus-intent threshold sales accepts. Forrester's case for dropping MQLs is the <1% inquiry-to-close rate and the buying-group problem. Teams that cannot yet report on opportunities and buying groups should tighten the MQL, add SAL, and measure pipeline — not delete the field and hope.
Disclaimer: This content is provided for informational purposes only and does not constitute financial, investment, or operating advice. Figures reflect publicly reported research as of August 2026, from studies with different sample frames, years, denominators, and funnel definitions. "MQL-to-SQL" is not a standardized accounting metric. Treat every benchmark as a directional peer check, not a board target without your own lagged cohort data.
