MQL and SQL: the critical handover points in your pipeline
There is no universal definition. But without clean definitions you lose leads, time and revenue. We show you how it works.
Why MQL and SQL are still a big topic today
MQL and SQL are the critical handover points between marketing and sales. They determine when marketing hands over a lead and when sales actively works it.
The problem: there is no universally valid definition of what makes an MQL or an SQL. Every company defines it individually, based on business model, ICP, brand awareness, buying centre size and sales logic.
That sounds flexible. In practice, without an agreed definition it turns into chaos.
When MQL and SQL are understood differently, expensive inefficiencies appear:
- Marketing generates leads, sales does not work them (“that is not an SQL”)
- Sales rejects leads without documenting a reason
- Leads disappear in the CRM instead of going back into nurturing
- Nobody really knows which leads are the best ones
The consequence
Friction, frustration, lost revenue.
This becomes critical in B2B in particular. Longer cycles, more complex buying centres, higher CAC: here the clean definition of MQL and SQL decides between success and failure.
The good news: the problem is solvable. With clear definitions, documented criteria and feedback loops it works.
MQL and SQL explained simply
MQL: Marketing Qualified Lead
An MQL is a lead that has shown enough interest and relevance through marketing activities to justify deeper qualification by sales.
Specifically: the lead fits your ICP, has shown relevant behaviour (website visits, content downloads, event attendance) and has plausible potential for further qualification by sales.
Important: an MQL has no purchase readiness yet. It signals: “I am interested.”
SQL: Sales Qualified Lead
An SQL is a lead where, in addition to interest and relevance, purchase potential is also visible.
Specifically: the lead has shown concrete sales signals (demo request, request for a conversation, dissatisfaction with the current solution), meets your sales requirements (budget, timing, tech stack) and is ready to be actively worked.
Important: purchase potential is not the same as purchase intent. An SQL may still say no. But the probability of a real conversation is significantly higher.
Who defines MQL and SQL, and how does lip service become binding rules?
MQL and SQL must be defined jointly by marketing, sales and RevOps.
This is not optional. If only marketing writes the definition, sales will not accept it. If only sales defines it, marketing will not be able to deliver.
The roles in the definition process
Marketing
Which behavioural signals show genuine interest? Which content interactions are meaningful? Which intent signals trigger the next stage?
Sales
Which criteria do we need to run a meaningful conversation? Which information is still missing? At which signals is a lead not mature enough?
RevOps
How do we build this technically? Which fields do we need in the CRM? How do we automate the handover?
The practical mechanism: the SLA
An SLA (Service Level Agreement) is where MQL and SQL become binding.
The SLA documents:
- Which profile attributes an MQL has to meet
- Which behavioural signals trigger a handover
- Within which time frame sales works a lead
- What happens when a lead is rejected
- How the lead is documented and returned to nurturing
Important: The SLA is not static. If sales regularly rejects leads in practice or conversion drops, the criteria have to be reviewed. This happens in regular feedback loops (monthly or quarterly).
Related reading: SLAs: the next step after shared KPIs
Without this feedback, the MQL/SQL definition remains a guess instead of a reliable working basis.
Need an outside view on your handover model?
Why MQL/SQL definitions fail in practice
Mistake 1: too much focus on lead score, too little on intent signals
The problem
A high lead score alone says little about sales readiness. A contact may have generated a lot of website traffic but hold the wrong role or come at the wrong time. Especially complex scoring models produce false positives: lead scores that look hot on paper but turn into nothing in reality.
The trend
The industry is moving away from complicated mathematical scoring models towards clear intent signals. Instead of a black box formula (50 points for a website visit, 30 for a download), explicit behavioural triggers are defined: “visit to the pricing page after 3+ website visits = SQL-ready” or “demo request = immediate handover”.
The consequence
Sales receives leads that look hot on paper but turn into nothing in conversation. Frustration rises, lead rejection rises, trust in marketing drops.
The solution
Combine lead score with explicit intent signals. A lead with a medium score but three visits to the pricing page is more valuable than a lead with a high score and no buying signals. Intent is king.
Mistake 2: unclear lead routing and return processes
The problem
A lead is handed over, sales rejects it, but it is unclear when the lead goes back into nurturing, how long it stays there or who reactivates it later.
The consequence
Leads disappear in the CRM. Marketing never sees that the lead was rejected. Potential deals are lost.
The solution
Clear return processes in the SLA. Example: “If sales rejects a lead, it goes back to marketing for 6 months of nurturing. After 6 months or on a new buying signal it is reassessed.”
Mistake 3: no feedback loops between marketing and sales
The problem
Sales documents “rejected: wrong timing”, but this information never reaches marketing. Marketing does not know that timing is an issue and changes nothing.
The consequence
Marketing optimises blindly. The same problems keep recurring. The MQL definition remains a guess.
The solution
Monthly feedback meetings between marketing and sales. Topics: which leads were rejected and why? Which signals are meaningful? Do the criteria need to change?
Mistake 4: no shared data basis (single point of truth)
The problem
Marketing looks at its marketing automation tool. Sales looks at the CRM. The numbers do not match. Who is right?
The consequence
Discussions become political instead of operational. “We see different numbers” leads to blame, not to solutions.
The solution
One single dashboard used by both teams. A single point of truth for pipeline, conversion, lead quality and rejection reasons. Only then can both teams work together cleanly.
What criteria an MQL should meet
An MQL has to be more than a contact with a vague expression of interest.
Leads should be defined as MQLs when they are both structurally relevant and behaviourally notable enough to justify deeper qualification by sales.
That means: there is a concrete problem, a matching fit and a realistic sales opportunity within a defined time frame.
The three levels of an MQL definition
Level 1: fit with the Ideal Customer Profile (ICP)
The lead should in principle match your target customer profile. Company size, industry, market, role, team structure or use case must at least be known so that later sales follow-up makes sense.
An example: you build a solution for CMOs in industrial companies with 100 to 500 employees in the DACH region. An intern from a 10-person startup is not an MQL, no matter how much content they consumed.
Level 2: relevant behaviour & context signals
Relevant behaviour does not only come from the frequency with which content is consumed, but above all from the context.
Important context signals are:
- •Repeated website visits (not just one visit)
- •Content downloads (especially checklists, ROI calculators, whitepapers)
- •High-intent page views (pricing, case studies, demo page, contact form)
- •Attendance at webinars or events
- •Repeated contacts (several interactions over time)
Level 3: plausibility for further qualification
Direct purchase readiness must never be assumed at the MQL stage. An MQL has the plausible potential to be further qualified by sales.
The difference between campaign noise and plausible potential:
| Criterion | Campaign noise | Plausible potential |
|---|---|---|
| Topic interest & problem pressure | Download of a whitepaper (could also be a working student) | Download of a checklist plus a visit to the pricing page |
| Customer profile | A student downloads a whitepaper | A department head downloads a whitepaper and then visits pricing |
| Conversation probability | “Just wanted to have a look” | Invested time, concrete conversation angles are visible |
An MQL is the lead in the right-hand column, not the one on the left.
What criteria an SQL should meet
An SQL marks the point at which a lead is no longer managed primarily in a marketing context, but may be actively worked based on sales logic.
That is why this stage needs significantly stricter and clearer criteria than an MQL.
The four pillars of an SQL definition
Pillar 1: clear sales readiness
A direct demo request or a request for a conversation is the perfect example. But a clear problem statement and strong intent signals (for example dissatisfaction with the current solution) count as well.
Examples of SQL signals:
- •“We are looking for a solution for X”
- •“Can I book a demo?”
- •Repeated visits to the pricing or demo page
- •Download of a comparison with your main competitor
- •Visit to the implementation page
Pillar 2: a minimum of fit and relevance
Not every interested contact is an SQL. Depending on the funnel model, a check happens here: does the timing fit? Is the budget realistic? What role does the contact hold in the buying centre? These questions are often clarified in the MQL stage or in the discovery call with sales.
Pillar 3: defined handover criteria
Sales must be able to understand why a lead was handed over as an SQL. This requires documented criteria: which signals were decisive? Which information is already available? Which questions remain open?
Pillar 4: clear follow-up logic
An SQL only works as an operational category if it is defined what happens next: who takes over (account executive, sales development rep, account manager)? How fast is the response (24 hours, 4 hours)? How many contact attempts are mandatory? When and under which conditions can an SQL be returned? Only this follow-up logic makes the status manageable.
Want to know how solid your MQL/SQL definition is today?
How we define MQL and SQL in practice: the 4-step process
How we define MQL and SQL depends not only on the terms themselves, but on how lead statuses, handover rules, scoring models and CRM logics interact day to day.
What matters is not the formal definition alone, but whether marketing and sales understand it the same way and live by it consistently.
Step 1: taking stock
First we review which lead statuses, handover rules, scoring models and CRM logics already exist.
We are particularly interested in how the teams live the existing setup in practice. A common pattern: “SQL and opportunity are basically the same for us, we do not always change the status.”
This gap between theory and practice is normal, and documenting it is the first step towards improvement.
Step 2: defining funnel stages and thresholds
In the next step we define together which funnel stages will exist in future. The guiding principle: as much as necessary, as little as possible.
Too many stages (lead, MQL, SAL, SQL, opportunity) create complexity and errors. Too few (lead, SQL) lose important context.
At the same time we define which combination of ICP fit, behaviour, need, role and intent signals turns a lead into an MQL, and at which point it becomes an SQL.
Step 3: handover & return
Then we define when sales has to accept a lead, under which conditions a return is possible, how it is documented and how the lead goes back into nurturing.
The return logic is the weak spot in many companies. Won but not yet sales-ready leads disappear in the CRM instead of being nurtured in a structured way.
Step 4: system logic in the CRM
Finally we translate the definitions into system logic: status fields and their transitions, mandatory information per stage, automations (which action triggers when?), ownership (who is responsible?), response times and follow-up obligations as well as reporting logic.
Only when this layer is built cleanly can MQL and SQL be measured and managed reliably.
Common mistakes in the B2B context
In B2B in particular it quickly becomes clear whether the MQL/SQL model holds up. Longer cycles, more complex buying centres, higher acquisition costs: here MQL and SQL have to be robust and precise.
Common mistakes in B2B
Mistake 1: the funnel is treated as a one-way street
Leads go in, and if they do not convert they are gone. Yet a return is not a step back, it is a documented, controlled shift of maturity into better nurturing.
Example: an SQL is worked by sales, but the timing does not fit. The lead goes back as an MQL with the context “good fit, but Q2 2027 instead of now”. Marketing can nurture it specifically until the right moment.
Mistake 2: statuses are treated like fixed labels
Sales marks a lead as SQL and that status never changes, even though the situation changed long ago.
Statuses should only apply as long as they reflect reality. If the target group, buying behaviour or sales logic changes, the criteria have to follow.
Mistake 3: the model is defended although it does not work
Conversion drops or the lead acceptance rate is low. Instead of reviewing the definitions, more reporting is built.
That is the wrong move. The problem is not measurement, it is the handover model itself. It needs sharper definitions, not more dashboards.
Need an outside view on your handover model?
Your next step
Your next step: review the model
MQL and SQL do not run by themselves. They are a system that needs maintenance.
The good news: you do not have to start from scratch. You have processes, data, a CRM. You only need to define it cleanly and make it binding.
Three ways to get started
Option 1
Check it yourself
Use our interactive checklist to see how well your MQL/SQL model already works today.
Option 2
Work with our template
Transfer the criteria from this guide into your MQL/SQL definition and adapt them to your own numbers.
Option 3
Professional support
In a first call (30 minutes, free of charge) we show you where your model creates friction and how to improve it.
Interactive checklist
Culture: Shared accountability instead of silo thinking
"Marketing celebrates lead volume while sales curses the quality. We break down silos and align both teams on one shared goal."
Marketing and sales teams share written, documented revenue targets.
disagreeStrongly
agree
disagree Strongly
agree
Marketing and sales goals are tied directly to the same business KPIs.
disagreeStrongly
agree
disagree Strongly
agree
Bonus and incentive structures reward collaboration between marketing and sales.
disagreeStrongly
agree
disagree Strongly
agree
Marketing and sales work with customer success to identify cross-sell/upsell potential.
disagreeStrongly
agree
disagree Strongly
agree
Answer at least one question
Together we build
the bridge
Every week without a functioning pipeline costs you more than 30 minutes of your time. In the initial consultation (free, 30 minutes) you get an outside perspective on your situation. No pitch. Then you decide.
FAQ: common questions about MQL and SQL
Sources
Sources: bvik Trendbarometer Industriekommunikation, Alltake Lead Quality Report, Lunas Benchmarks, DigitalApplied Smarketing Playbook, SyncGTM Lead Conversion Data, B2B-Runner, SalesHead, iGrow, Vogler Marketing, Adobe, Vertus Lead Scoring Guide, HeyRebels, Clicknify (“MQL is Dead” trend).