MQL vs SQL vs SAL: A Framework That Holds Up

I've had the MQL/SQL definition conversation with every single client. It always starts the same way. Someone asks: "What's an MQL?" Then someone else asks: "And when does it become an SQL?" An hour later, the whiteboard is full, nothing is decided, and someone suggests "let's take this offline."

The reason this conversation loops is that people debate labels instead of definitions. And the labels themselves are genuinely ambiguous, because the industry never agreed on what they mean.

Why MQL and SQL Mean Different Things

There's a piece of history behind the confusion that most people skip over. Different schools of thought shaped the vocabulary in different ways, and most marketing and sales teams have absorbed one dialect or another without realizing it.

The HubSpot tradition. HubSpot's default lifecycle is Subscriber → Lead → MQL → SQL → Opportunity → Customer. In this model, SQL is the marketing-to-sales handoff moment: the lead is "ready for Sales to work on." Opportunity is what comes after discovery, once a Deal record gets created in the CRM. SQL sits upstream of the qualifying conversation, not downstream.

The Winning by Design tradition. In Jacco van der Kooij's Revenue Architecture, the customer journey runs Prospect → MQL → MQA → SQL → SAL → Commit → Live → MRR → LTV. Their MQL is "expresses interest and fits the target profile." Their SQL is "experiences a pain and wants to take action." Their SAL is "verified by the sales team as benefiting from the impact." Translated: SQL is the explicit willingness to engage, SAL is sales confirming the fit, Commit is the closed deal. Same structural logic as HubSpot's lifecycle, just with Commit replacing Opportunity as the label.

The Salesforce tradition. In classic Salesforce and enterprise B2B usage, SQL often means "Sales has qualified this after a conversation." The handoff gets called an MQL, the qualification conversation happens, and only then does it become an SQL. Opportunity is either the same moment as SQL or immediately after.

Same acronym, completely different positions in the funnel. When a marketer raised on HubSpot talks to a sales leader raised on Salesforce, they're using the same word for different things. An hour of meeting time disappears, and neither side realizes they were never actually disagreeing about substance.

My Framework (And Why)

I'm going to use the HubSpot lifecycle as the reference model. Three reasons:

1. Most B2B SaaS companies I work with live in HubSpot or a HubSpot-like tool. Their stages are already set up this way.
2. It aligns with Winning by Design's Revenue Architecture, which puts SQL before SAL and treats SAL as the sales-side acceptance moment. Two traditions, one structural logic.
3. The "qualified for whose work" reading is operationally cleaner than the "qualified by whom" reading. It tells you whose queue the lead is in right now, which is what teams actually need to know on a Monday morning.

Here's the model:

If you come from a Salesforce background, mentally translate my "SQL" as "the handoff moment" and my "Opportunity" as "what you might have been calling SQL." The mapping is consistent, the names just sit differently.

The Question That Determines Everything

Everything in this model hinges on one question. When does a Lead that Marketing is working on become a Lead that Sales should work on?

Most teams land on one of two answers, and only one of them holds up.

The three directions an explicit signal can arrive from:

• They came to you. Demo request, pricing inquiry, qualifying freemium signup, direct outreach ("can we talk?"). The classic hand-raise.
• You came to them and they said yes. Marketing-owned outbound triggers a reply that's warm enough to book a meeting. Functionally identical to a hand-raise, just with a different origin story. Same explicit consent.
• They demonstrated it through product behavior. Tight, explicit product-qualified signals in a freemium or trial motion. A user in a paid-tier-sized workspace, with admin rights, who invited 12 teammates and hit the core feature 30 times hasn't raised their hand, but they've behaviorally said "this product matters." Treat it as SQL-worthy if the criteria are specific (which workspace size, which actions, which role, which window). Loose criteria turns this into scoring with extra steps.

All three are the same category: explicit signals of buying intent from the buyer's side. The path there can be inbound, outbound, or product-led, but the trigger is always a human decision to engage, not a model's inference.

Why scoring alone fails as the trigger. Scoring is a black box to Sales. They can't tell which SQLs are "someone told us they want to talk" versus "a model thinks they might." Trust in the queue collapses. Marketing starts optimizing the score because it's easier than generating actual intent. The MQL-gaming trap that plagues teams who use MQL as a target reappears, just with a prettier name.

When Signals Don't Produce Enough SQLs

This is where most teams break. SQL volume is low, someone proposes relaxing the definition, and three quarters later the conversation is looping again. The honest answer is that a low SQL number is a symptom, and loosening the definition treats the symptom instead of the cause. There are three real causes, and each has a different fix.

Weak demand creation. Not enough of your ICP knows you exist as a solution, so not enough latent demand is out there to convert. Slow fix, compounds over time. If you want the full picture of how demand creation, demand capture, and outbound work together, there's a related piece on the three-lane demand model.

Leaky demand capture. People are visiting pricing, reading case studies, and not hand-raising. The problem is pricing opacity, weak CTAs, a clunky demo form, or missing trust signals. Medium fix, usually high-leverage.

Under-invested outbound. You have ICP-fit accounts that have shown signal but haven't hand-raised, and you're not proactively reaching out. Fast fix in theory, but only if outbound is run as a continuous program, not as an emergency response when pipeline gets thin. This is where marketing-operated outbound matters, because sales-owned outbound almost always kicks in too late to dig you out of the hole.

The one move to not make: inflate SQL volume by counting scored MQLs as SQLs. It moves your failure mode from "not enough SQLs" to "SQLs don't convert," which is harder to diagnose and louder when Sales starts complaining. It also quietly moves the outbound workload from Marketing to Sales. Sales now has to cold-work leads that Marketing either didn't reach out to, or reached out to and couldn't convert. The work doesn't magically become easier because it changed hands.

SAL: Acceptance as the Default

Once the SQL definition is tight, the SAL step becomes almost trivial, which is the point.

The traditional read is that SAL is an active acceptance: Sales looks at the SQL, clicks "accept," then works it. That adds friction. Reps forget to click, leads sit in a queue, the handoff slows down, and the "acceptance" step becomes a bureaucratic bottleneck that produces no useful data.

The rejection reasons are the gold. "Wrong persona." "Company too small." "Already in conversation with a competitor." "Not in a buying cycle." Five to seven options in a dropdown, picked in 10 seconds. Each rejection is a signal that helps Marketing calibrate what's actually being sent. Without this feedback loop, Marketing keeps sending the same shape of lead, Sales keeps ignoring it, and both teams blame each other in the next pipeline review.

From SAL to Opportunity

Once the SAL is working, Sales runs discovery. If the conversation confirms a real problem, a relevant contact, and some timeline or intent to act, the deal gets created. That's the Opportunity stage, and that's where qualification frameworks (BANT, MEDDIC, SPICED, whichever matches your motion) earn their keep. Pick one, define what "qualified" means in those terms, and commit.

This is also the moment the deal enters pipeline, which in my view is where Marketing's accountability should actually sit. I've written separately about why Pipeline Generated, not MQLs, belongs at the top of the Marketing scorecard, if that's a thread you want to pull.

The Most Common Mistakes

Letting scoring sneak into the SQL trigger. Scoring is a Marketing tool. It decides who to chase. It never triggers the handoff on its own. The moment a score threshold is in your SQL definition, Sales stops trusting the queue.

Making SAL an active acceptance. Reps forget, leads sit, the feedback loop doesn't form. Default to accepted. Require action only on rejection.

Forgetting to track rejection reasons. Without reasons, Marketing learns nothing from disqualifications and keeps sending the same shape of lead. Five reasons in a dropdown is all you need.

Loosening the definition to inflate volume. If SQLs are short, the problem is demand creation, demand capture, or outbound. Fix those. Don't move the goalposts.

Skipping the calibration sync. Definitions without a feedback loop decay. A 30-minute weekly or bi-weekly sync between marketing and sales, reviewing what was passed, what was rejected and why, and what converted, is the mechanism that keeps the model honest. Start weekly when the model is new or lead volume is high, move to bi-weekly once the system stabilizes. Without the sync, within two quarters Marketing will be passing SQLs that drift from the criteria, Sales will stop flagging rejections, and you're back in the same room having the same conversation.

What I'd Actually Recommend

Pick a tradition (HubSpot lifecycle or Winning by Design Revenue Architecture both work for B2B SaaS) and plant a flag. Write your definitions on a single page in plain language. Make the SQL trigger "explicit willingness to engage" and name the specific signals that count. Default the SAL to accepted, reject with a reason. Run a 30-minute weekly or bi-weekly sync between marketing and sales to keep the definitions alive.

Then leave it alone. The definitions don't need quarterly revisiting unless your ICP or product fundamentally changes. The calibration sync handles the ongoing drift.

That's the operational layer. Without clear definitions and a feedback loop, any marketing-sales strategy stays theoretical. With them, it becomes a system.