Digital Squad

B2B Marketing · July 31, 2026

MQL vs SQL vs SAL: Defining Lead Stages Your Sales Team Will Actually Agree On

MQL, SQL, and SAL explained in plain terms. What each stage means, who owns it, and how to define them so marketing and sales stop arguing about lead quality.

By Digital Squad

July 31, 2026 MQL vs SQL vs SAL: Defining Lead Stages Your Sales Team Will Actually Agree On

Marketing says they sent over 200 qualified leads last quarter. Sales says maybe ten were worth a phone call. Neither side is lying — they're just using the word "qualified" to mean two completely different things.

This is the most common breakdown in B2B revenue teams, and it almost always comes down to one root cause: MQL, SQL, and SAL are undefined, or defined once in a slide deck and never revisited.

Here's a straight answer to the definitional question, followed by how to actually build stage definitions that hold up in a real pipeline review.

MQL vs SQL vs SAL: The Quick Answer

  • MQL (Marketing Qualified Lead) — a contact who has shown enough engagement or fit (content downloads, website behaviour, firmographic match) that marketing believes they're worth sales' attention.
  • SAL (Sales Accepted Lead) — an MQL that a sales rep has reviewed and formally accepted as worth pursuing, confirming it matches the target account profile.
  • SQL (Sales Qualified Lead) — a lead that sales has engaged directly and confirmed has a real need, budget, timeline, and authority to buy — it's now a genuine sales opportunity.

The stages move in that order: MQL → SAL → SQL. Each stage represents a different party taking ownership and a different level of buying intent confirmed. Skipping SAL is common in smaller teams, but it's the stage that most directly fixes the "sales says these leads are junk" problem, because it forces a human handoff instead of an automated one.

Why This Distinction Actually Matters

Marketing and sales use fundamentally different definitions of "ready" — marketing measures interest, sales measures intent to buy. Left unreconciled, this gap creates two expensive symptoms:

  • Marketing over-reports impact. Lead volume looks strong, but pipeline contribution and closed revenue don't follow, because MQLs were never filtered for real buying intent.
  • Sales under-invests in follow-up. Reps stop calling marketing leads because their hit rate is poor, which suppresses conversion data and makes marketing look even less effective than it is — a feedback loop that erodes trust between the two functions.

Defining and agreeing on lead stages isn't a reporting exercise. It's how you align two teams around a shared definition of a good lead, so marketing optimises for the right kind of volume and sales trusts what lands in their queue.

Breaking Down Each Stage

MQL: Marketing Qualified Lead

An MQL has engaged with your brand in a way that signals genuine interest, but hasn't been vetted by a human yet. This is typically determined by a lead scoring model combining:

  • Firmographic fit — company size, industry, region, job title/seniority
  • Behavioural signals — content downloads, pricing page visits, webinar attendance, email engagement, repeat site visits
  • Intent signals — third-party intent data showing active research on relevant topics

A lead crosses the MQL threshold when its score passes an agreed cutoff. The mistake most teams make here: setting the threshold too low to inflate lead counts, or never revisiting the score as new closed-won data comes in.

SAL: Sales Accepted Lead

This is the most overlooked stage, and often the most valuable to formalise. An SAL is an MQL that a sales development rep has manually reviewed within an agreed SLA (commonly 24 hours) and accepted as matching the ideal customer profile.

The SAL stage exists specifically to create accountability on both sides:

  • Marketing gets visibility into acceptance rates — a leading indicator of lead quality, weeks before deals close.
  • Sales can reject leads back to marketing with a reason code (wrong industry, wrong seniority, already a customer), which feeds directly back into scoring model refinement.

Without SAL as a distinct stage, MQLs flow straight into a sales rep's queue with no accountability checkpoint, and quality issues only surface much later, when it's too late to course-correct that quarter's campaigns.

SQL: Sales Qualified Lead

An SQL is a lead that a sales rep has directly engaged and confirmed has real buying potential, typically assessed against a qualification framework like BANT (Budget, Authority, Need, Timeline) or MEDDIC for more complex enterprise sales. At this point, the lead is functionally a sales opportunity and usually gets logged as such in the CRM.

This is the stage most B2B teams should be reporting against when they talk about "marketing-generated pipeline" — not raw MQL count, which is far too early-stage a metric to reflect actual revenue potential.

MQL vs SAL vs SQL at a Glance

StageWho Qualifies ItWhat It ConfirmsTypical Signal
MQLMarketing (via scoring model)Fit + engagementContent download, site behaviour, firmographic match
SALSales (manual review)ICP match, worth pursuingSDR accepts/rejects within SLA
SQLSales (direct conversation)Budget, authority, need, timelineDiscovery call confirms real opportunity

How to Define Your Own Lead Stages (Without a Six-Month Project)

You don't need a perfect model on day one. You need a definition both teams can point to in a pipeline review without disagreement.

  • Start from closed-won data, not assumptions. Look at your last 20–30 closed-won deals and identify what they had in common at the MQL stage — company size, source, engagement pattern. Build your scoring model backwards from what actually converted, not from what feels intuitively "engaged."
  • Write the SAL criteria down as a checklist, not a vibe. "Right industry, right seniority, right region, not an existing customer" is a checklist a rep can apply in 30 seconds.
  • Agree on an SLA for lead follow-up and acceptance. A lead that sits untouched for a week isn't qualified anything — it's cold.
  • Review acceptance and conversion rates monthly, together. If SAL acceptance rate is below 50%, that's a scoring model problem. If SQL-to-close rate is dropping, that's a sales qualification rigor problem. The stage data tells you where the leak is.
  • Put it in the CRM, not just a document. Stage definitions only work if they're operationalised as actual pipeline stages with required fields — otherwise every rep interprets them differently.

The Real Fix Isn't a Better Definition — It's a Shared System

Clear definitions solve the argument. They don't solve the underlying issue if marketing and sales are still working off separate spreadsheets, disconnected CRM views, or lead routing that happens manually and inconsistently. The teams that get real value from MQL/SAL/SQL definitions are the ones that also connect them to marketing automation for consistent lead scoring and routing, and to analytics that report pipeline contribution by stage — not just top-of-funnel volume.

If your marketing and sales teams are still debating what "qualified" means, that's usually a signal the underlying lead management infrastructure needs attention, not just the terminology.

How Digital Squad Can Help

Getting MQL, SAL, and SQL definitions to actually stick requires more than a shared glossary — it requires the systems and data behind them to be aligned too. Digital Squad supports this through:

  • Marketing Automation — building lead scoring models, routing workflows, and nurture sequences so leads move through MQL, SAL, and SQL consistently, without manual bottlenecks.
  • Data Analytics — connecting lead-stage data to your CRM and closed-won outcomes, so you can see exactly where leads convert or fall through, by stage.
  • LinkedIn Marketing — generating higher-fit MQLs at the top of the funnel through targeted account and audience strategy, so your sales team spends less time rejecting leads at the SAL stage.

Book a discovery session with a senior strategist to review how your current lead stages are performing.

FAQs

What is the difference between MQL and SQL?

An MQL is qualified by marketing based on engagement and fit signals, such as content downloads or firmographic match. An SQL is qualified by sales after a direct conversation confirms budget, authority, need, and timeline. An MQL indicates interest; an SQL indicates a real, active buying opportunity.

Do all B2B companies need an SAL stage?

Not always — smaller teams with high-touch sales processes sometimes merge SAL into SQL. But adding a distinct SAL stage is usually worthwhile once lead volume grows enough that sales starts ignoring marketing-sourced leads, since it creates an accountability checkpoint before a rep invests time in full qualification.

Who should own the lead scoring model that defines an MQL?

Marketing typically owns the scoring model, but it should be built and reviewed jointly with sales using closed-won data, not marketing assumptions alone. Models that are never validated against actual conversions tend to produce high MQL volume with low sales acceptance.