MQL and SQL: Definition, differences and why a smooth handover is so important
MQL and SQL are operational thresholds in B2B lead management. They determine when Marketing hands over a lead and when Sales actively follows it up.
There is no universally accepted definition of what constitutes an MQL or an SQL. You determine this individually for your company, based on factors such as your business model, your ICP, your brand awareness, your customers' buying centres, etc.
In practice, it is precisely this handover that determines whether leads are nurtured effectively within the pipeline or fizzle out due to unnecessary friction. If marketing and sales have different understandings of MQLs and SQLs, this leads to costly inefficiencies, frustration and lost revenue.
In practice, the terms MQL and SQL raise four key questions for marketing, sales and management:
- What constitutes an MQL for your company?
- What constitutes an SQL for your company?
- How do you organise the handover from MQL to SQL so that it actually works in day-to-day operations?
- How is a rejected lead documented, returned and transferred back into the nurturing process?
MQLs and SQLs are therefore critical operational handover points, rather than mere linguistic abbreviations.
Lead qualification in B2B: the most important models
Whether an MQL/SQL definition is appropriate at all depends on the sales model and product complexity. The classic waterfall model may be useful, but a product-led growth approach or an account-based model may work better.
Wasserfallprinzip
Demand Gen
Product Led Growth
Account Based
Whichever model suits you best, what matters is not the label given to the funnel stages, but that they are understood consistently and supported by clearly defined processes. Depending on the funnel model, individual operational steps — such as the discovery call — may therefore take place as early as the SAL phase or only in the SQL phase.
MQL and SQL explained simply
MQL
An MQL is a lead that has demonstrated sufficient interest and relevance through marketing activities to justify further qualification by the sales team.
SQL
An SQL is a solid prospect for a concrete discussion with the sales team, as, in addition to interest and relevance, purchasing potential is also evident.
Important: Purchase potential does not automatically equate to purchase intent. This is a key distinction that often leads to misunderstandings in practice.
Where & why MQL and SQL definitions fail in practice
We have repeatedly identified the following four points as critical in B2B companies.
Too much focus on scoring, too little on context
A high lead score alone does not say enough about the lead's actual sales readiness. Particularly in a B2B context, it is often more crucial to know what role a person holds, which company they work for, what problem they are trying to solve, and whether the timing is right for a sales conversation at all.
Unclear lead routing and return processes
Automated nurturing processes only work really well if it is clearly defined which lead belongs in which path, when sales takes over, and when a contact is returned to the nurturing process. Without this shared logic, automation may be achieved, but there is no clear control based on fit, relevance and sales readiness.
Lack of feedback loops
Marketing can only improve its lead qualification if feedback from the sales team actually flows back into the system. This includes, for example, reasons for rejection, objections raised during conversations, lost deals, patterns in unsuitable leads, and indications of what content or signals were missing from the process. Without this feedback, marketing optimises in a vacuum, whilst sales remains faced with the same problems.
No shared data source (Single Point of Truth)
Different dashboards are used across departments, which do not reflect the full context of the pipeline. This means that discussions about lead quality, pipeline status and revenue quickly become political rather than operational. Shared dashboards covering the entire pipeline (funnel stages, conversion rates, reasons for loss) as a single point of truth ensure that both teams have the same view of the pipeline's performance. Only then can decisions be made clearly and responsibilities truly be traced.
Common mistakes with MQLs and SQLs in the B2B SaaS environment
In B2B SaaS in particular, it quickly becomes apparent whether the model being used is viable. Longer sales cycles, buying centres, product complexity and higher acquisition costs mean that MQLs and SQLs should not be viewed too simplistically. Typical problems include poor conversion rates, inconsistent scoring, inconsistent reasons for rejection and CRM statuses that no longer accurately reflect reality.
In our view, common mistakes include:
- Treating the funnel as a one-way street. However, a return to an earlier stage is not a step backwards, but a documented and controlled shift in maturity towards a more appropriate nurturing phase.
- Statuses are treated as fixed labels, even though they are only valid for as long as they reflect reality. If the target group, purchasing behaviour or sales logic changes, the criteria and statuses must be adjusted accordingly.
- The model is defended even though conversion rates or lead acceptance figures show that it is no longer effective. In such cases, what is needed is not more reporting, but a refinement of the definitions.
If one or more of these patterns occur, the problem usually lies not with a single team, but with a handover model that has not been properly integrated in functional, technical and organisational terms.
How well defined is your MQL/SQL model at present?
With our interactive checklist, you can use just a few questions to check whether your marketing and sales teams are already closely integrated or simply working in parallel. This allows you to quickly identify where friction arises and what potential is still being lost between marketing and sales.
Kulturell: Shared Accountability statt Silo-Denke
"Marketing feiert Leadquantität und Sales flucht über die Qualität. Wir brechen Silos auf und richten beide Teams auf ein gemeinsames Ziel aus."
Marketing‑ und Vertriebsteam haben gemeinsame, schriftlich dokumentierte Umsatzziele.
AblehnungStarke
Zustimmung
Ablehnung Starke
Zustimmung
Marketing‑ und Vertriebsziele sind direkt an dieselben Business‑KPIs gekoppelt.
AblehnungStarke
Zustimmung
Ablehnung Starke
Zustimmung
Bonus‑/Incentive‑Strukturen fördern die Zusammenarbeit zwischen Marketing und Sales.
AblehnungStarke
Zustimmung
Ablehnung Starke
Zustimmung
Marketing und Sales arbeiten mit Customer Success zusammen, um Cross‑/Upsell‑Potenziale zu identifizieren.
AblehnungStarke
Zustimmung
Ablehnung Starke
Zustimmung
Mind. eine Frage beantworten
Who defines MQLs and SQLs, and how can lip service be turned into clear commitments?
MQLs and SQLs must be defined jointly by Marketing and Sales. Only when both teams accept the same criteria can lead qualification work effectively in day-to-day operations, thereby generating revenue, speeding up processes and ensuring that sales resources are used effectively.
A tried-and-tested method is the use of SLAs (Service Level Agreements). These set out the definitions, handover criteria, response times and responsibilities in a binding manner.
An SLA covers, amongst other things:
- Which profile characteristics an MQL must fulfil
- Which behavioural signals trigger a handover
- The timeframe within which Sales must process an MQL
- What happens if a lead is rejected
Why feedback loops are crucial
A good SLA is not static. If, in practice, Sales regularly rejects leads or few deals are closed, the criteria must be reviewed and adjusted.
This is precisely why feedback loops between Marketing and Sales are needed. Without this feedback, the lead definition remains a guess rather than a reliable working basis.
What criteria an MQL should meet
An MQL must be more than just a contact who has expressed a vague interest. Contacts should be defined as MQLs if they are both structurally relevant and demonstrate sufficient behavioural indicators to justify more in-depth qualification by the sales team. This means there is a specific problem, a good fit and a realistic sales opportunity within a defined timeframe. From our perspective, the following aspects are particularly important, as a rough guideline:
Fit with the Ideal Customer Profile
The lead should, in principle, match your target customer profile. Company size, sector, market, role, team structure or use case must be known to at least such an extent that subsequent sales follow-up makes sense in principle.
Relevant behaviour & contextual signals
Relevant behaviour stems not only from the frequency with which content is consumed, but above all from the context. Important contextual signals include, for example:
- •Repeated website visits
- •Content downloads
- •High-intent page views (contact, legal notice, pricing, case studies, tools & checklists, etc.)
- •Participation in webinars
- •Repeated contacts (trade fairs, online)
Plausibility for further qualification
Under no circumstances should a direct willingness to purchase be assumed at the MQL stage. Their actual status is better defined as follows: they possess the plausible potential to be further qualified by the sales team.
The difference between campaign noise and plausible potential, explained using a simple example:
| Criterion | Campaign noise | Plausible potential |
|---|---|---|
| Interest in the topic & urgency of the problem | Download of a white paper. This could also be a student on a work-study scheme. | Download of a checklist followed by a visit to the pricing page. |
| Customer profile | Student downloads a white paper. | Department head downloads a white paper. |
| Likelihood of a meeting | Wanted to 'just find out more'. | Has invested time and shown concrete interest in a meeting. |
What criteria an SQL should meet
An SQL marks the point at which a lead is no longer managed primarily within a marketing context, but may be actively pursued based on sales logic. This stage therefore requires significantly stricter and clearer criteria than an MQL.
Clear sales readiness
A direct request for a demo or a request for a meeting are perfect examples. However, a clear description of the problem and other strong signals of intent (such as dissatisfaction with the existing solution) also play a part.
Minimum level of fit and relevance
Not every interested contact is a good SQL. This is where typical sales questions come into play (depending on your funnel model, e.g. during or before the discovery call) to determine factors such as timeframes, tech stack, business impact, etc.
Defined handover criteria
Sales must be able to understand why a lead has been handed over. This requires documented criteria: which signals were decisive, what information is already available, and what outstanding questions remain to be addressed?
Clear processing logic
An SQL only functions as an operational category if it is also specified what happens next. Who takes over, how quickly is a response required, how many contact attempts are mandatory, and when may an SQL be returned with justification? It is only through this follow-up logic that the status becomes manageable.
How we define MQL and SQL in practice
How we define MQL and SQL in practice depends not only on the terms themselves, but on how lead statuses, handoff rules, scoring models and CRM logics interact on a daily basis. The decisive factor is not the formal definition alone, but whether marketing and sales share the same understanding and consistently live by it.
That is why we follow four consecutive steps.
As-is assessment
First, we review which lead statuses, handoff rules, scoring models and CRM logics are already in place. We are particularly interested in how the teams actually live the existing setup in practice. A simple example is the gradual deviation from the defined process: „For us, SQL and opportunity are basically the same thing, we don't always update that.“
Definition of funnel stages and thresholds
In the next step, we jointly define which funnel stages will exist going forward. The guiding principle is always: as much as necessary, as little as possible, in order to minimise process deviations in day-to-day operations.
At the same time, we define which combination of ICP fit, behaviour, need, role, company context and intent signals turns a lead into an MQL, and at what point it becomes an SQL.
Handoff & return
Next, we determine when sales must accept a lead, under what conditions a return is possible, how this is documented, and how the lead goes back into nurturing. This return logic is often the actual weak point in many companies — leads that have been generated but are not yet sales-ready simply disappear into the CRM.
System logic
Finally, we translate the definitions into system logic. This includes status fields, required information, automations, ownership, response times, processing obligations and reporting rules. Only when this layer is properly set up can MQL and SQL be reliably measured.
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.