MQL and SQL are among the most-used acronyms in B2B, and among the most loosely defined. When the definitions are vague, the marketing-to-sales handoff breaks down — marketing passes “qualified leads” that sales rejects, and everyone blames everyone. This article defines MQL and SQL operationally, in terms specific enough to actually use.

What MQL and SQL actually mean

MQL and SQL mark two stages in a lead’s progression from raw contact to sales opportunity. A Marketing-Qualified Lead (MQL) is a lead that has met marketing’s criteria for genuine interest and fit — enough to be worth marketing’s continued attention and, eventually, a handoff to sales. MQL criteria typically combine fit (does this contact match our ideal customer profile — right industry, size, role?) and engagement (have they shown meaningful interest — downloaded substantive content, attended a webinar, visited key pages, engaged repeatedly?). A Sales-Qualified Lead (SQL) is a lead that sales has accepted as worth active pursuit — it has met not just marketing’s interest criteria but sales’ readiness criteria. SQL criteria add intent and readiness (does this lead have a real need, budget, authority, and timeline?) to the fit and engagement that made it an MQL. An SQL is someone a salesperson should be actively working. The operational distinction: MQL is marketing’s judgment that a lead is interested enough to pursue; SQL is sales’ judgment that a lead is ready enough to sell to. The transition from MQL to SQL is the critical handoff — and it only works when both teams agree on what each stage requires. Vague definitions (“an MQL is an interested lead”) are useless; operational definitions specify the exact fit, engagement, and readiness criteria that move a lead between stages.

Common questions

What’s the core difference between an MQL and an SQL?

An MQL has met marketing’s criteria for interest and fit — it’s worth pursuing. An SQL has additionally met sales’ criteria for readiness — it’s worth actively selling to now. The difference is interest versus readiness: an MQL is interested enough for marketing to nurture and hand off; an SQL is ready enough (need, budget, authority, timing) for sales to actively work. The MQL-to-SQL transition is sales accepting that a marketing-qualified lead meets the bar for active sales effort.

Who defines the MQL and SQL criteria?

Both teams, together — that’s the entire point. MQL criteria are set with marketing’s input (what signals genuine interest and fit) but must be acceptable to sales (so the MQLs marketing produces are ones sales considers worth receiving). SQL criteria are set by sales (what makes a lead worth active pursuit) with marketing’s understanding (so marketing nurtures toward it). Definitions set unilaterally by one team cause the handoff conflict. Shared, jointly-agreed criteria are what make MQL and SQL operationally useful.

What criteria should an MQL definition include?

Two dimensions: fit and engagement. Fit criteria assess whether the contact matches your ideal customer profile — industry, company size, role/seniority, geography, and other firmographic factors. Engagement criteria assess demonstrated interest — meaningful content engagement, repeat visits, webinar attendance, form submissions of substance (not just a single low-value download). A strong MQL definition combines both: a contact that fits the profile and has shown real engagement, with specific thresholds for each rather than vague “showed interest” language.

What makes a lead sales-qualified?

Readiness on top of fit and engagement — typically assessed through frameworks like BANT (Budget, Authority, Need, Timeline) or similar. An SQL has a real, identified need your product addresses, involves someone with buying authority or influence, has budget potential, and has a timeline that makes active pursuit worthwhile. Where an MQL is “interested and fits,” an SQL is “interested, fits, and is ready to have a sales conversation.” Sales accepts the lead as worth their active time.

Why does the MQL-to-SQL handoff break down?

Almost always because of misaligned definitions. Marketing, measured on MQL volume, may set a loose MQL bar and pass leads sales doesn’t consider ready; sales, measured on closed deals, rejects them and stops trusting marketing’s leads. The breakdown is rarely about effort — it’s about definitions. When both teams agree precisely on what qualifies a lead at each stage, and on the handoff process, the friction largely disappears. The fix is shared operational criteria, not more leads or more effort.

Should every MQL become an SQL?

No — and expecting that misunderstands the funnel. MQLs are leads interested enough to pursue, but many won’t prove ready (no budget, no timeline, wrong fit on closer inspection). A healthy funnel has an MQL-to-SQL conversion rate well below 100% — the qualification stages exist precisely to filter. The MQL-to-SQL conversion rate is itself a key metric: too low suggests marketing’s MQL bar is loose; very high might suggest the bar is too strict and marketing is under-supplying the top of the funnel.

How do I use MQL and SQL to improve performance?

Track conversion between stages and diagnose where leads stall. A low MQL-to-SQL rate suggests marketing’s MQL criteria are too loose (passing unready leads) or nurturing is weak. A low SQL-to-opportunity rate suggests sales’ qualification or follow-up needs work. Measuring conversion at each stage reveals where the funnel leaks, letting you fix the specific problem — tighten MQL criteria, improve nurturing, or strengthen sales follow-up — rather than guessing. The stages become diagnostic checkpoints, not just labels.

How this applies to your business

Define MQL and SQL criteria jointly with both marketing and sales, in specific operational terms, because vague or unilateral definitions are the root of the handoff conflict. Specify the exact fit, engagement, and readiness thresholds that qualify a lead at each stage, with both teams agreeing the criteria produce leads worth receiving. This shared, precise definition is what makes the marketing-sales handoff work. Use the stages as diagnostic checkpoints by tracking conversion between them. The MQL-to-SQL and SQL-to-opportunity conversion rates reveal where your funnel leaks — loose MQL criteria, weak nurturing, or poor sales follow-up. Measuring at each stage lets you fix the specific problem rather than guessing, turning MQL and SQL from labels into operational tools for improving lead-generation performance. Don’t expect every MQL to become an SQL — the filtering is the point. A healthy funnel loses leads at each qualification stage as fit and readiness are tested. Monitor the conversion rates for balance: too low suggests over-loose qualification or weak nurturing; too high might mean overly strict criteria starving the funnel. The right rates depend on your business, but the goal is a funnel that filters effectively while supplying enough qualified leads. Iscope Digital’s Online Lead Generation service delivers leads against jointly-defined qualification criteria with a lead-quality SLA. For the foundational definitions of leads and lead generation, see What is online lead generation? and for holding lead quality accountable through the handoff, Lead-quality SLAs: how to write one that holds the agency accountable.