MQL vs SQL: Where the Line Goes When Sales Cycles Run 90+ Days

MQL vs SQL is not a vocabulary question. It is a decision about who owns a lead, on what evidence, and from which date you start counting.

A marketing qualified lead (MQL) is a lead marketing judges worth a salesperson’s time. A sales qualified lead (SQL) is one a salesperson has spoken to and agreed is a real buying conversation. Many guides stop there. This one is for B2B SaaS and fintech teams whose deals take three months or more to close, because that is where the line between the two stages starts to distort every channel report you read.

Below: definitions you can write into a CRM, why long cycles break the usual handoff, what MQL to SQL conversion rate to expect and how far to trust the benchmarks, and how to build B2B lead scoring that sales will actually accept.

MQL vs SQL: the definitions that hold up

Every team uses the acronyms. Far fewer have written down what moves a lead from one to the other. The result is a familiar meeting: marketing reports MQLs up, sales reports pipeline flat, and both are right about their own number.

The fix is a definition each side can audit. Here is the version we recommend, with the stage in the middle that many guides skip.

Why the sales accepted lead stage matters

Without an SAL, an MQL that sales never touches looks identical to one sales rejected. You cannot tell a bad lead from an ignored one. Adding the stage costs one field in the CRM and turns the argument into data: how many MQLs were accepted, how fast, and how many of those became SQLs.

Pair it with a written service-level agreement. Marketing commits to a volume and a definition; sales commits to a review time and a reason code for every rejection. The reason codes are what let you fix the MQL definition later.

The SQL vs MQL test for a single lead

When a record is disputed, ask one question: has anyone at our company spoken to this person about a problem we solve? If not, it is at most an MQL, however good the fit. If yes, and the conversation confirmed need and a way to buy, it is an SQL. Behavior alone never makes an SQL.

Where the line goes in MQL vs SQL when sales cycles run 90+ days

On a short cycle, the MQL and the SQL are days apart and the definitions barely matter. On a cycle of three months or more, the gap between them is long enough to break measurement, and the break is mechanical rather than a matter of opinion.

The platform stops counting before sales says yes

Ad platforms credit a conversion only inside a set period after the ad interaction, the conversion window. In Google Ads, the default click-through window for Search and Display is 30 days, and it can be set anywhere from 1 to 90 days depending on the conversion source. A change to the window applies only from that day forward (Google Ads Help, conversion windows, checked 6 October 2026).

So if a form fill becomes an SQL six weeks later, a 30-day window never sees it. Set to 90 days, the window still misses anything slower. A campaign optimized on MQLs will look efficient at exactly the point where sales disagrees.

LinkedIn is more generous. It recommends a 90-day click and 90-day view window, which is the default in Campaign Manager, lets you set 1, 7, 30 or 90 days manually, and, for advertisers sending conversions through its Conversions API or a CSV upload, offers 180- or 365-day windows for certain categories, including Marketing Qualified Lead and Sales Qualified Lead (LinkedIn Marketing Solutions Help, conversion windows, checked 6 October 2026). That is a platform naming the SQL as an event worth tracking separately. It is worth taking the hint.

Send the SQL back to the platform

The way to close the gap is offline conversion import. Google Ads attaches a Google Click ID (GCLID) to each ad click. You store it with the lead, and when that lead later converts offline, you send the GCLID back with the conversion type and time (Google Ads Help, offline conversion imports, checked 6 October 2026).

Two practical notes from the same page. Google offers enhanced conversions for leads as the upgrade, which adds hashed first-party data such as email addresses and phone numbers to the match. And Google’s page says that from 15 June 2026, offline conversion imports and enhanced conversions for leads uploads move to the Data Manager API and are blocked in the Google Ads API, and developer tokens that sent no request between January and June 2026 are not allowlisted for legacy access. If your CRM uploads through the Google Ads API, check which route it uses now.

What this means for where you draw the line

• Import the SQL, not just the MQL, as a separate conversion action, so bidding can learn from the stage sales agrees with.
• Keep MQL criteria strict enough that most MQLs are worth a call. A loose MQL definition flatters the platform’s numbers and buries sales.
• Report over a period that matches your cycle. We explain how long acquisition takes to earn its cost back in our guide to CAC payback period benchmarks.

MQL to SQL conversion rate: what to expect, and from which source

Your MQL to SQL conversion rate is SQLs created divided by MQLs created, over the same cohort. Track it by cohort month rather than calendar month: on a long cycle, this month’s SQLs came from MQLs created weeks ago.

The by-channel benchmark, and its limits

The by-channel figures we found come from First Page Sage, an SEO agency, in its B2B SaaS Funnel Conversion Benchmarks report, last updated 11 June 2025. The firm says the data comes from access to 50+ B2B SaaS clients over the last decade, mostly companies with $10M–$100M in revenue. Its reported MQL to SQL rates by channel:

Read these as direction, not as a target. Three reasons:

• It is one firm’s client data, not a sampled study. The report gives no count of companies or leads behind each cell.
• Its definitions are its own. It defines an MQL by fit alone, and an SQL as an MQL who has said the product is desirable and within budget and is already speaking with a salesperson. A team whose MQL requires intent as well as fit will see a higher rate by construction.
• The direction is the useful part. Organic search leads have often researched the problem before they arrive, while paid clicks can include more early comparison shoppers, especially on broad match. A gap between the two is plausible. Its exact size in your funnel is something only your CRM can tell you.

We found no independently sampled study of MQL to SQL conversion rate by channel that we could cite with confidence. If you see a single “good” number quoted without its definitions, treat it the same way.

A rate is only meaningful against your own line

Move the MQL line and the rate moves with it. Tighten MQL criteria and fewer leads qualify, but more of them become SQLs. Loosen them and the opposite happens. Neither change says anything about whether marketing improved.

That is why we report SQL conversion rate by source, over a window matching your sales cycle, and refuse to report lead volume without quality or any 30-day performance window. Both lists are published on how we work and what we report. The pipeline argument for judging SEO and paid on SQLs rather than lead counts is set out in SEO vs PPC lead quality.

If you want an outside read of where your own line sits, the Acquisition Audit is a two-week diagnosis of your search and paid acquisition: what is broken, what it is costing you, and what to fix in what order.

B2B lead scoring that sales will accept

Lead scoring is how you decide, at scale, which leads cross the MQL line. A common reason models fail: sales did not help build them, so sales does not trust them.

Score fit and intent separately

Good B2B lead scoring keeps two numbers rather than one:

• Fit: does this company look like your customers? Industry, size, region, tech stack, and for fintech the regulated category it sits in.
• Intent: is this person acting like a buyer now? Pricing-page visits, a demo request, repeat visits to product pages, a reply to sales.

A high-fit, low-intent lead goes to nurture. A low-fit, high-intent lead gets a polite check before sales spends time on it. Only high fit plus high intent becomes an MQL. Collapsing both into one score hides which half is doing the work.

Why BANT alone does not fit a buying committee

BANT (budget, authority, need, timeline) asks whether one person can buy. In a B2B SaaS or fintech deal, several people often have to agree, and the first person to fill in a form is often not the one who signs. Score at the account level as well as the person: three engaged people from one target account mean more than one very active individual.

Let scores decay

On a long cycle, a pricing-page visit from four months ago is history, not intent. Give behavioral points a half-life, so a lead that goes quiet drops back below the MQL line instead of sitting there inflating the count.

Close the loop with sales

• Review the SAL rejection reason codes monthly and change the model when one reason dominates.
• Compare SQL rates for leads just above and just below the MQL threshold. If they are similar, the threshold is in the wrong place.
• Separate product qualified leads if you have a free trial or freemium tier: usage is stronger evidence than any form fill.

Scoring is also where cost comes back in. If a channel’s MQLs rarely become SQLs, its real customer acquisition cost is much higher than its cost per lead suggests.

FAQ: MQL vs SQL

MQL vs SQL: what to do next

Write both definitions down this week, add a sales accepted lead stage with reason codes, and import SQLs into your ad platforms as their own conversion. Then judge every channel on SQLs by source over a window that matches your sales cycle, and on the marketing-sourced pipeline those SQLs become.

The line between MQL vs SQL is not where the best guide says it is. It is where your sales team agrees it is, written down and measured.