MQL vs SQL Is a Written Agreement, Not a Law

A marketing qualified lead (MQL) is marketing's label. A sales qualified lead (SQL) is the label sales applies once it accepts the record. SQL here is not the database language, and MQL is not MQL5.

HubSpot's lifecycle docs, updated 17 July 2026, say marketing sets the first label and sales sets the second. No cited guide publishes one point cutoff that turns an MQL into an SQL. You will not find one checklist these guides share.

The marketing funnel still needs a written handoff. Intent data can time the outreach. Intent data does not accept the lead.

Key Takeaways

• An MQL is marketing's bar. An SQL is sales' bar. The pages that define them do not share one sentence.
• HubSpot's lifecycle docs call an MQL ready for sales. HubSpot's own sales post, updated 31 July 2026, says an MQL is not ready for a pitch.
• SQL can mean a score, a salesperson's call, or a rep's explicit yes. A booked call can skip the MQL stage.
• No cited guide publishes a universal point cutoff. Adobe's more-than-65 line is a telesales handoff in one undated guide, not an SQL.
• The circulated 13% line is a 2014 lead-to-opportunity rate. It is not an MQL-to-SQL benchmark.

If you want the next argument over this handoff, the newsletter is the place.

MQL vs SQL at a Glance

Neither label wins. They are two bars. The failure mode is using one word for both events.

What Is a Marketing Qualified Lead?

HubSpot's lifecycle docs define an MQL as "a contact or company that your marketing team has qualified as ready for the sales team." The page was last updated 17 July 2026. Marketing applies the label. Sales has not accepted the record yet.

That is not the sentence on HubSpot's sales post. Michael Welch's update on 31 July 2026 says an MQL has engaged with marketing content, has shown potential interest, and "isn't ready for a sales pitch yet." Window shopping, in his framing.

The sales post does not cite the lifecycle knowledge base. Two HubSpot pages, two weeks apart, point in opposite directions.

Salesforce Trailhead sits closer to Welch than to the knowledge base: a good fit, not ready to buy. Kristen Baker's HubSpot marketing post, updated 31 August 2023, sits closer to the knowledge base. Marketing has deemed the lead more likely to become a customer and sends it to sales.

Those three sentences do not combine into one HubSpot definition.

Gartner's public abstract, Jenifer Silverstein, published 2 January 2026, restricts the use. Use MQLs "only to identify sales-ready buyers or pinpoint optimization needs," not as a demand-generation success metric. The abstract does not contain a conversion percentage.

On demand generation, becoming an MQL is a stage name, not a shared test of readiness.

Janessa Lantz, in "How MQLs Broke B2B Marketing's Credibility and How to Rebuild It" (Troupe, 17:01), put the unit mismatch in one line.

"We're always going to stay in marketing world and we're going to pitch these units over to you that you don't actually care about because everything in your world is about the account."

Marketing's unit is the person. Sales' unit is the account. A score on one contact looks thin when the buying group is several people deep.

The bar: Marketing is willing to put the record in front of sales. That is not the same claim as "not ready for a pitch." Write which sentence your team implemented.

SQL Is Three Different Events

Vendor pages use "SQL" for at least three events: a score or a content action, a salesperson's call, or a rep's explicit acceptance. Those are not the same meeting.

HubSpot's lifecycle docs define an SQL as "a contact or company that your sales team has qualified as a potential customer." Lead Status is a sub-stage of that lifecycle stage, not a third stage. HubSpot's default lifecycle has no sales accepted lead.

The listed statuses include New, Open, In Progress, Open Deal, Unqualified, Attempted to Contact, Connected, and Bad Timing. Unqualified and Bad Timing sit inside SQL. The knowledge base does not define those tests.

Adobe's comparison, dated 4 April 2025, lets marketing declare the pass. The buyer has the information to decide, the budget and resources, and executive buy-in. A trial signup or a discovery call can also be the trigger.

The page stops at interest versus buying intent. It does not show a call that skips MQL.

Paul Bookstaber, in Salesforce's 18 March 2024 post, says a sales qualified lead is flagged by a sales team member as likely to convert. One listed trait is personal contact, usually through a call or video meeting.

Other traits are persona fit, a pain the company can help solve, and no BANT barrier. On that page, BANT is budget, authority, need, and timing.

LinkedIn's SQL glossary uses budget, authority, need, and timing, and says sales teams identify the lead as qualified for outreach. BANT is not the definition of an MQL. It is a test several vendor pages apply at the SQL stage.

A third event is explicit acceptance. 4Thought draws the line at a record sales has reviewed and explicitly accepted.

MQL is marketing's output. SQL is sales' commitment to follow through.

A booked call can skip the MQL stage. Salesforce's Australia and New Zealand post, byline 9 June 2026, treats MQL and SQL as Lead Status values.

An MQL is actively qualified by a person or agent against ideal-customer fields. An SQL, on that page, is an MQL that then shows buying intent: a demo, a trial, a quote, or an ask to speak with sales.

The same page says a booked call can go straight to SQL. Opportunity is a later conversion, when a rep converts the Lead. Welch's "MQL always comes before SQL" is that author's sequence, not a law.

The bar: Sales has accepted the record, or a named intent action has fired and a rep has reviewed it. Write which of the three events your CRM is counting.

HubSpot's Own Pages Disagree

Welch's ranking post, updated 31 July 2026, does not cite the lifecycle knowledge base updated 17 July 2026. Who gets to declare the pass splits the same way at other vendors.

Adobe's 4 April 2025 page says "the marketing team determines when it's time to pass that buyer to the sales team." Salesforce's March 2024 post says a sales team member flags the SQL. Trailhead agrees that an SQL is a former MQL that has been nurtured into "good fit and ready to buy."

That disagrees with HubSpot's knowledge base. There, the MQL was already "ready for the sales team," and the SQL is what sales then qualifies as a potential customer.

Budget moves, too. Bookstaber's 26 January 2024 comparison puts product-need fit and budget inside the MQL criteria, and says the lead is not ready to purchase. His 18 March 2024 post says BANT barriers still exist for an MQL, and that an SQL has no BANT barrier.

Those two Salesforce posts are not one rule.

A pricing-page visit is an MQL signal on Adobe's 2025 page. On Welch's 2026 post, pricing-page engagement, including repeat visits, sits on the SQL side. Copy the page you implemented.

A first-touch pricing download is one of two false passes Adobe names. The other is a high interaction count that is still early-journey questions.

The bar: Cite the page you implemented. "HubSpot and Salesforce agree" is not a sentence you can defend.

Handoff Criteria Are a Written Agreement

The definitions agree that criteria exist. They do not publish one checklist. Steve Silver's Forrester post, 17 May 2018, tells you to write the definitions, the acceptance and rejection criteria, the response times, and the conversion expectations.

The post supplies questions. It does not supply numbers. A vendor blog's integers are not that standard.

Fewer pages name a rejection test than name a trigger.

HubSpot's Lead Status list, inside SQL, includes Unqualified and Bad Timing. The knowledge base does not define the tests. Adobe's comparison names the two false passes above.

Bookstaber's March 2024 post treats a career-page visit, and a journalist or student doing research, as signs the person is not buying. 4Thought wants a structured reject field: wrong fit, bad timing, already a customer, competitor. That is their recommendation, not a sample of your pipeline.

Response time is a recommendation, not a study. Zendesk gives "ideally within 24 hours" as one reason to require an acceptance step.

Your written agreement can name a different window. The page does not report a measured lift.

The measured follow-up finding is from 2013, and it is not an SLA. Sabnis, Chatterjee, Grewal, and Lilien studied 461 sales reps at four firms, in the Journal of Marketing, first published online 1 January 2013. As reps' experience increases, their responses to managerial tracking of lead follow-up and to marketing-lead volume decrease, and their responses to the quality of prequalification increase.

The title is "The Sales Lead Black Hole." The abstract's 70% names that hole. It is not a measured ignore rate from those 461 reps.

The drop is still happening, and it is not a conversion rate. Zapier's survey, run by Centiment from 3 to 17 April 2026, collected 404 completed surveys from US sales and marketing managers and above, at companies with at least 50 employees, involved in the sales process. Use the wire's bullet, not the looser headline: 92% of sales managers say qualified leads are regularly dropped each month.

On Zapier's post, 42% of sales teams drop leads a few times a month, and 38% see it multiple times a week. 12% report leads going untouched nearly every day.

The break they name is the handoff. 37% say leads fall through between marketing tools and the CRM, or between marketing and sales. "Qualified" is not defined as MQL or SQL.

ZoomInfo on LinkedIn (Oct 2026) named the break in one line: "Marketing throw leads over the wall to sales, and context gets lost at every handoff."

On r/b2bmarketing, the fix that repeats is process, not a new point threshold.

u/mustangscottie in r/b2bmarketing (Aug 2026) put the political version cleanly: "If you get sales involved in building out this process, they then can't moan about it - because they helped build it."

The bar: Write the trigger, one reject reason, and a response time your team will keep. A score is not that document.

Scoring Has No Universal Cutoff

No cited vendor guide publishes a universal point at which an MQL becomes an SQL. A sentence that says "75 points means SQL" is invented. Three different things get called "the score."

Fit, or grade, asks whether this person or company looks like a customer. Engagement, or behavior, asks what they did. The handoff line is the score at which you may call the record an MQL, or send it to a person.

Only the third item is a qualification decision.

Adobe's undated lead-scoring guide is Adobe's own model. Demographic attributes earn 0 to 30 points. A page visit or an email open earns 1 point.

Searching "Marketo Engage" on Google earns 15. An unsubscribe is −50.

If a qualified lead has fewer than 65 points, the guide calls it a prospect and sends it for further nurturing. If it has more than 65 points, the guide calls it a lead and sends it to telesales for further qualification. Exactly 65 is not named, so "65 or more" is not what the guide says.

The more-than-65 record is not called an SQL in that paragraph. Later in the same guide, you are told to set an MQL threshold with sales. Keep those two sentences apart.

HubSpot's scoring tool, last updated 2 September 2026, says you set the thresholds. The example labels are not a recommended MQL line: High is 70 to 100, Medium is 40 to 69, Low is −100 to 39. A worked example caps the overall score at 100 and scores one described contact at 29.

Workflow examples notify an owner over 50, or when a deal score goes above 75. Documentation examples. Not the industry line between MQL and SQL.

Welch's "over 75 points went to sales" is one company he worked with. That is not a named employer, and it is not a HubSpot recommendation.

Trailhead separates score from grade. Score is activity, and you set the threshold. Grade is fit, from prospect fields.

A demo-request form is a reason to notify the assigned rep. "Just any form completion" is not treated as intent.

The design point that survives outside a vendor worksheet is newer. Wu, Andreev, and Benyoucef, published online 25 March 2026, cluster on demographic and firmographic cues first, then rank conversion likelihood inside the cluster. After preparation, the set is 3,448,111 call interactions with 784,493 leads, from 40 companies in legal consulting, custom payment services, and commercial office cleaning.

Fit can be scored before behavior exists. The paper does not give one headline lift, and it is not an MQL-to-SQL rate.

The bar: Set the number with sales. Name the label that number creates. Leave 65 and 75 in the worksheets they came from.

The 13 Percent Line Is Lead to Opportunity

MQL-to-SQL conversion rate is (SQLs / MQLs) × 100. A same-month ratio is the wrong cohort when the handoff takes months.

Geckoboard states the offset: if the average conversion time from MQL to SQL is 3 months, divide SQLs created in month 3 by MQLs created in month 1. If you report this rate next to other paid KPIs, including in performance marketing, name the cohort.

If you have seen 13% quoted as an MQL-to-SQL rate "according to Salesforce," that citation is not this rate. Geckoboard prints 13% and 84 days, then adds a parenthesis that equates lead to opportunity with MQL to SQL.

The study Geckoboard names is Gilad Raichshtain at Implisit, November 2014, on Salesforce's blog. Implisit measured lead to opportunity: 13% of leads, average 84 days, anonymous data from hundreds of companies, no sample size, no industry list. The words MQL and SQL do not appear in those sentences.

That parenthesis is Geckoboard's, not Implisit's. Salesforce hosting the 2014 post does not make it a 2026 study.

Bookstaber's 26 January 2024 comparison prints an unsourced "Gartner shows 21%." The 2 January 2026 abstract does not contain 21%.

4Thought, cited above for the acceptance test, also prints 13% to 25% as a healthy MQL-to-SQL rate. No study is attached.

A broad MQL pool converts at a lower rate than an ICP-filtered pool, and both ratios can be internally consistent. The spread is a definition problem, not a missing industry number.

The bar: Use a cohort. Label the numerator. 13% is the wrong figure for this rate.

Sales Accepted Lead Is a Checkpoint

A sales accepted lead is the checkpoint you insert when "marketing will hand it over" and "sales has accepted it" are not the same meeting. It is not a third column in the table above.

LinkedIn's glossary says SALs "are often the bridge between MQLs and SQLs." Zendesk describes them as leads sales officially accepts from marketing for further investigation.

HubSpot's default lifecycle has no SAL. Terry Flaherty's Forrester post, 1 May 2018, says version one of the waterfall has sales accept the MQL and then qualify it.

That is the conceptual slot. No single glossary sentence is shared across the vendor pages cited here.

A product qualified lead is a different test. Pendo, 3 September 2019, defines a PQL as someone who has had some success using the product. Amplitude, Phil Burch, 18 September 2024, defines a PQL as a user who has meaningfully engaged with the product and shows intent to convert.

A PQL is not an SQL.

An opportunity sits after SQL. On HubSpot, it is the next default lifecycle stage, associated with a deal. On the Salesforce ANZ page, it is an active deal, created when a rep converts the Lead.

An opportunity is not a synonym for SQL.

The bar: Add a sales accepted lead only if acceptance and qualification are different meetings. A product-use success is not an SQL.

Pick the Marketing Bar or the Sales Bar

Choose the marketing bar if the question is whether marketing will put the record in front of sales.

Choose the sales bar if the question is whether sales has accepted it, on a call, a named intent action, or an explicit yes.

The failure is one label for both events. On r/b2bmarketing, the comments land on misuse, not abolition. u/Brian-Carroll in r/b2bmarketing (Oct 2026) kept both sides: "I don’t think the MQL is dead. But we need to stop treating it as a reliable signal of buying readiness."

Lantz's last word in the same Troupe episode is that she does not think MQLs are going to completely go away. The board metric is the misuse. The stage can stay, once you write what it means.