GTM Engineering

MQL vs SQL vs Opportunity: What Do These Terms Actually Mean?

Sachin Jha
8 mins
Last Updated on
September 2, 2026
Table of content
COMMUNITY
Join the ONEGTM CLUB
500+ GTM leaders and operators discussing what's actually working — in real time.
About the author
Sachin Jha
Founder & CEO, ONEGTMLAB | Engineering GTM for Technical Founders
Sachin has built GTM systems for 47+ technical founders across cybersecurity, DevOps, and developer infrastructure. He writes about GTM Engineering, AI-powered outbound, and what it actually takes to build a predictable pipeline at early-stage B2B SaaS companies.

Two people in the same meeting can say MQL and mean completely different things, and neither of them is wrong.

I have watched that conversation go sideways more than once.

Marketing reports a number, sales says it does not recognise that number, and the next twenty minutes disappear into what counts as qualified.

The terms are not the problem. The missing shared definition is.

So here is the clean explanation of what an MQL, an SQL and an opportunity actually are.

Then why no two companies define them the same way, and what to do if yours have stopped working.

Before the definitions, it helps to see the whole path in one pass.

How a stranger becomes a deal?

Someone becomes known to you. A form fill, a webinar, a downloaded guide, a conversation at an event.

Marketing watches what they do next.

If they do enough of it, and they look like the kind of buyer you sell to, they get handed to sales as an MQL.

A salesperson picks it up, has a conversation, and decides whether it is worth real time. If it is, it becomes an SQL.

If there is a genuine need with budget behind it, the deal is entered in the CRM as an opportunity, with a value and a close date.

From there it is won or lost like any other deal.

That is the shape. Each handoff is where the disagreements live, so take them one at a time.

What is an MQL?

A marketing qualified lead is someone who has engaged with your marketing enough, and fits your buyer profile well enough, that marketing believes sales should look at them.

That is the definition everyone agrees on.

It is also almost useless on its own, and the reason sits inside the sentence.

Every use of the word enough is a decision someone made

Enough engagement. Enough fit.

Neither has a standard value, and nobody outside your company set them.

A whitepaper download might push someone over the line at one company and not register at another.

Same person, same action, two answers.

What the MQL bar is actually measuring

Two things are being scored at once, and they are not the same thing.

  • Fit. Do they look like the kind of company and role you sell to.
  • Engagement. Have they done things that suggest interest.

The trap is treating the combination as readiness to buy. Fit is not readiness, which is an argument I have made at length in GTM Engineering Is Not a Job Title.

A perfect-fit company with a curious intern downloading a guide scores well and is buying nothing.

Which is roughly why the next stage exists at all.

What is an SQL?

A sales qualified lead is a lead a salesperson has looked at and agreed is worth pursuing, usually after a conversation.

The distinction from an MQL is who made the call. An MQL is marketing’s judgment, an SQL is sales agreeing with it.

The qualification framework changes the answer

Different companies qualify against different checklists, and the checklist decides what an SQL is.

  • BANT checks budget, authority, need and timeline. Old, simple, and biased toward deals already forming.
  • MEDDIC checks metrics, economic buyer, decision criteria, decision process, identified pain and champion. Heavier, and suited to complex enterprise deals.
  • Custom question sets are what a lot of teams actually run, built around their own product and cycle.

A lead that clears BANT may not clear MEDDIC.

Both get called an SQL, and a conversion rate calculated on one is not comparable to the other.

The stage some companies add in between

A sales accepted lead, or SAL, sits between MQL and SQL at companies that want to separate two questions.

Accepting means sales agrees it is worth contacting. Qualifying means sales has contacted it and decided it is worth pursuing.

Splitting those apart tells you whether your problem is lead quality or follow-up.

It also puts the word SQL at a different point in your funnel than in someone else’s.

The third term is the one that finally gets tied to something concrete.

What is an opportunity?

An opportunity is a qualified deal with an identified need, entered in the CRM with a value attached and an expected close date.

This is the point where the funnel stops describing a person and starts describing a deal.

Why it is the most consistent of the three

An opportunity is tied to a CRM stage and feeds the forecast, so finance cares about it.

That pressure keeps the definition honest in a way nothing above it experiences.

Nobody argues in a board meeting about what an MQL is. They argue about the forecast, which is why this definition gets maintained.

It is still not standard

When a deal becomes an opportunity varies. Some teams create one after a first discovery call, others wait for a confirmed budget.

That timing decision moves every conversion rate above it.

Create opportunities early and your MQL to opportunity rate looks excellent while your win rate looks poor.

Which brings us to the question the definitions cannot answer on their own.

Why companies define these differently

Here are the three side by side, with the ambiguity in each one named plainly.

MQL vs SQL vs Opportunity

Two structural reasons explain why these do not transfer between companies, and there is a third nobody likes to admit.

They are thresholds, not categories

An MQL is not a type of person. It is a line a company drew.

Where it drew that line reflects things that have nothing to do with the buyer.

Deal size. Sales capacity. How much rejection the sales team tolerates before it stops trusting marketing.

A team with two SDRs draws that line somewhere very different from a team with twenty.

Both are right for their own business and neither transfers.

They describe a person, and B2B buying is done by a group

This is the deeper problem, and it is not an opinion.

Forrester reports that more than 80% of B2B purchases involve complex buying scenarios, and that 95% involve three or more people across at least two departments, published alongside its B2B Revenue Waterfall.

A model that qualifies one named contact is measuring the wrong unit when almost every purchase is made by a committee.

Forrester puts it more plainly elsewhere: your buyer is a group, not a person.

One contact clearing your threshold says very little about whether the account is buying.

The practical answer to that problem is account-based rather than lead-based, which is the whole subject of The ABM Workflow Every Team Needs In 2026.

A lot of definitions were inherited rather than chosen

Scoring models outlive the people who built them.

A rule set that came with a CRM template, or was tuned by someone who left two years ago, is still quietly running.

It describes a company that no longer exists, with a product that has changed and a buyer who has moved on.

Worth asking out loud whether anyone here remembers deciding it.

The benchmark nobody can trace

A widely quoted MQL to SQL conversion figure circulates through this category, usually credited to Salesforce research.

I went looking for the page that publishes it.

Salesforce’s own State of Sales page and HubSpot’s State of Marketing page do not contain the figure, and do not use the term MQL at all.

So this article asserts no benchmark, because I could not find a first-party page stating one.

That absence says more than the number would have.

A metric whose most-quoted benchmark traces back to nothing anyone can open is not measuring the same thing at each company.

company defined thresholds

None of that is a modern complaint. It is built into a model over twenty years old, and the people who built it have already moved on.

Where the model came from, and where it went

The origin makes the variance easier to understand, because these terms were built for a market that no longer exists.

SiriusDecisions coined these terms in the early 2000s

MQL and SQL come from the Demand Waterfall, a framework built by the analyst firm SiriusDecisions to standardise how marketing handed leads to sales.

It worked. It gave two functions a shared vocabulary when they had none, and most funnel language still in use descends from it.

Forrester later acquired SiriusDecisions and continued developing the model, which it renamed along the way.

Forrester moved past the lead in 2021

This is the part almost nobody mentions, and it is the most important fact in this article.

In 2021 Forrester published the B2B Revenue Waterfall, which shifted the model away from tracking individual leads and toward tracking buying groups attached to opportunities.

The organisation that owns the framework made it opportunity-centric rather than lead-centric five years ago.

So arguing that the lead-based funnel is out of date is not contrarian. It is agreeing with the people who built it.

Which leaves the practical question, since a lot of us still have to work inside this vocabulary tomorrow morning.

What to do if your definitions are broken

I should be straight about where this site already stands. We have called the reporting habit around this MQL Theatre.

It appears as the first entry in GTM Anti-Patterns: Seven Failures Nobody Bothered To Name, where the argument is that a number revenue does not trust should not be on the report at all.

Both are true at once. These terms are worth understanding precisely and worth being sceptical of as headline metrics.

Four things to do.

Step 1: Write both definitions down and put them next to each other

Ask marketing to write what an MQL is. Ask sales to write what they think it is. Separately.

The gap between those two documents is usually the entire problem, and it takes an afternoon to find.

Step 2: Measure the handoff, not the volume

Lead volume is easy to move and tells you almost nothing.

The rate at which sales accepts what marketing sends tells you whether the definition works.

Falling acceptance means the threshold is wrong. That is fixable, and a volume number will never surface it.

Step 3: Score the account, not just the contact

If a purchase involves several people across departments, one contact clearing a threshold is thin evidence.

Look at how many people from the same account are engaging, and in which functions.

Two people from different departments beats one person doing five things.

Step 4: Watch behaviour that costs the buyer something

A form fill is cheap.

Sitting through a technical deep dive, pulling three colleagues into a call, or asking about implementation is not, and those are the signals worth turning into pipeline.

Replacing the MQL line on your report with signals acted on and pipeline influenced is a harder conversation, and a better one.

Where to start

Ask your marketing and sales leads to write down what an MQL is, separately, this week. Then put the two definitions side by side.

If they do not match, you have found the reason your funnel numbers have never quite reconciled, and you have found it in an afternoon.

Frequently Ask Questions: Quick Answers to the Real Questions

Is the MQL dead?
No, but it has been demoted by the people who invented it. Forrester’s model now tracks buying groups rather than individual qualified leads. It still works as an internal routing mechanism. It is a poor metric to report upward, which is a different question.
What is a sales accepted lead, and do we need one?
An SAL is a lead sales has agreed to contact, sitting between MQL and SQL. It separates lead quality from follow-up discipline. You need it if marketing and sales are arguing about whose fault the drop-off is. Otherwise it is a stage that adds admin.
What is a good MQL to SQL conversion rate?
Not honestly answerable with a number, which is uncomfortable but true. The rate depends entirely on where you set your MQL threshold. Lower the bar and volume rises while conversion falls. The useful measure is whether your own rate is stable, and what changed when it moved.
Who should own the MQL definition, marketing or sales?
Neither alone. Owned by marketing it drifts toward volume, owned by sales it drifts toward a bar so high marketing stops trying. Set it jointly, review it on a schedule, and make the sales acceptance rate the number both sides are judged on.
How often should these definitions be reviewed?
Quarterly, and any time pricing, product or sales headcount changes materially. The threshold reflects sales capacity, so a team that doubles headcount and keeps the old bar is leaving conversations on the table.
Do these terms still work for product-led growth?
Poorly, because the model assumes qualification happens before use. In PLG someone has signed up and used the product before anyone qualifies anything. PLG teams usually replace the MQL with a product qualified lead, scored on usage depth and account spread rather than content engagement.
About the author
Sachin Jha
Founder & CEO, ONEGTMLAB | Engineering GTM for Technical Founders
Sachin has built GTM systems for 47+ technical founders across cybersecurity, DevOps, and developer infrastructure. He writes about GTM Engineering, AI-powered outbound, and what it actually takes to build a predictable pipeline at early-stage B2B SaaS companies.

Frequently Asked Questions

What is GTM Engineering?

Traditional marketing runs campaigns. GTM Engineering builds the infrastructure that makes campaigns measurable, repeatable, and scalable.

How is it different from traditional marketing?

Traditional marketing runs campaigns. GTM Engineering builds the infrastructure that makes campaigns measurable, repeatable, and scalable.

Who needs GTM Engineering?

Traditional marketing runs campaigns. GTM Engineering builds the infrastructure that makes campaigns measurable, repeatable, and scalable.

What problems does it solve?

Traditional marketing runs campaigns. GTM Engineering builds the infrastructure that makes campaigns measurable, repeatable, and scalable.

What tools are typically involved?

Traditional marketing runs campaigns. GTM Engineering builds the infrastructure that makes campaigns measurable, repeatable, and scalable.

Subscribe To ONEGTMLAB Weekly

Your weekly dose of GTM sanity. Frameworks, signals, and strategies that actually move revenue.
Thank you! Your submission has been received!
Oops! Something went wrong while submitting the form.