MQL and SQL are among the most-used acronyms in B2B, and among the most loosely defined. When the definitions are vague, the marketing-to-sales handoff breaks down — marketing passes “qualified leads” that sales rejects, and everyone blames everyone. This article defines MQL and SQL operationally, in terms specific enough to actually use.

What MQL and SQL actually mean

MQL and SQL mark two stages in a lead’s progression from raw contact to sales opportunity. A Marketing-Qualified Lead (MQL) is a lead that has met marketing’s criteria for genuine interest and fit — enough to be worth marketing’s continued attention and, eventually, a handoff to sales. MQL criteria typically combine fit (does this contact match our ideal customer profile — right industry, size, role?) and engagement (have they shown meaningful interest — downloaded substantive content, attended a webinar, visited key pages, engaged repeatedly?). A Sales-Qualified Lead (SQL) is a lead that sales has accepted as worth active pursuit — it has met not just marketing’s interest criteria but sales’ readiness criteria. SQL criteria add intent and readiness (does this lead have a real need, budget, authority, and timeline?) to the fit and engagement that made it an MQL. An SQL is someone a salesperson should be actively working. The operational distinction: MQL is marketing’s judgment that a lead is interested enough to pursue; SQL is sales’ judgment that a lead is ready enough to sell to. The transition from MQL to SQL is the critical handoff — and it only works when both teams agree on what each stage requires. Vague definitions (“an MQL is an interested lead”) are useless; operational definitions specify the exact fit, engagement, and readiness criteria that move a lead between stages.

Common questions

What is an MQL?

MQL stands for Marketing Qualified Lead. Operationally, an MQL should be a prospect who meets predefined marketing criteria indicating that the person or account is worth passing into a more active sales process. Those criteria might include company fit, engagement, content activity, form submissions, or other qualification signals. The exact definition should be agreed upon by marketing and sales rather than based solely on a lead-scoring number.

What is an SQL?

SQL stands for Sales Qualified Lead. Operationally, an SQL is a prospect that sales has reviewed and determined is sufficiently qualified for direct sales follow-up. Qualification can involve factors such as company fit, relevant business need, appropriate stakeholder involvement, timing, budget, or willingness to have a sales conversation. The definition should be specific enough that sales representatives can consistently decide whether a lead qualifies.

What is the difference between an MQL and an SQL?

An MQL has met marketing-defined qualification criteria, while an SQL has met sales-defined qualification criteria. An MQL might have demonstrated meaningful engagement and fit the target market, but that does not necessarily mean the prospect is ready for a sales conversation. An SQL represents a stronger level of sales readiness based on the organization’s agreed qualification process.

What criteria should make someone an MQL?

An MQL definition should combine fit and meaningful behavior rather than relying on one activity. Criteria could include matching the ideal customer profile, reaching a defined engagement threshold, requesting high-intent information, attending a relevant event, or taking another action that indicates potential interest. The exact criteria should reflect the company’s sales cycle and customer journey. A simple page visit, for example, may not be enough to qualify someone as an MQL.

What criteria should make someone an SQL?

An SQL should meet clearly defined sales criteria. Depending on the business, this could mean confirming that the prospect fits the target market, has a relevant business problem, has an appropriate role in the buying process, and is willing to discuss a potential solution. Some organizations use frameworks such as BANT, MEDDICC, or their own qualification methodology. The important point is that the definition must produce a lead that a salesperson can reasonably act on.

Should MQL and SQL definitions be based on lead scores?

Lead scoring can support qualification, but a score should not automatically determine whether a lead is an MQL or SQL. A prospect can accumulate points through activities that do not indicate genuine buying interest. Conversely, a high-value account may be commercially important even with limited observable engagement. Scores work best when combined with firmographic fit, contact information, account context, and explicit qualification criteria.

Who decides whether a lead is an MQL or SQL?

Marketing should generally own the operational definition of an MQL, while sales should own the definition of an SQL. However, both definitions should be agreed upon jointly because the handoff affects both teams. Marketing needs to understand what sales considers actionable, while sales needs to understand how marketing generates and qualifies leads. Regular reviews should determine whether the definitions are producing useful opportunities.

What happens after an MQL becomes an SQL?

Once an MQL meets the agreed sales qualification criteria, it should be routed to the appropriate salesperson or sales team with enough context to act. The CRM should record the qualification status, ownership, source, relevant account information, and important engagement or qualification details. Sales should then accept, reject, disqualify, or further qualify the lead according to an agreed process. This creates accountability rather than allowing leads to disappear between marketing and sales.

How should businesses measure MQL-to-SQL conversion?

Calculate the percentage of MQLs that become SQLs over a defined period. However, the metric is only useful if both stages have consistent definitions. Businesses should also track SQL-to-opportunity, opportunity-to-customer, pipeline value, revenue, and time-to-conversion. A high MQL-to-SQL rate is not necessarily positive if the resulting SQLs rarely become opportunities or customers. Quality should be evaluated throughout the funnel.

What is the biggest problem with poorly defined MQLs and SQLs?

The biggest problem is that the labels become meaningless. Marketing may optimize for large numbers of MQLs while sales considers most of them unqualified, creating friction and poor follow-up. Similarly, if sales can classify almost any contact as an SQL, the metric stops providing useful information. An operational definition should specify who qualifies, why they qualify, what happens next, who owns the lead, and which measurable criteria determine each stage. Use the stages as diagnostic checkpoints by tracking conversion between them. The MQL-to-SQL and SQL-to-opportunity conversion rates reveal where your funnel leaks — loose MQL criteria, weak nurturing, or poor sales follow-up. Measuring at each stage lets you fix the specific problem rather than guessing, turning MQL and SQL from labels into operational tools for improving lead-generation performance. Don’t expect every MQL to become an SQL — the filtering is the point. A healthy funnel loses leads at each qualification stage as fit and readiness are tested. Monitor the conversion rates for balance: too low suggests over-loose qualification or weak nurturing; too high might mean overly strict criteria starving the funnel. The right rates depend on your business, but the goal is a funnel that filters effectively while supplying enough qualified leads. Iscope Digital’s Online Lead Generation service delivers leads against jointly-defined qualification criteria with a lead-quality SLA. For the foundational definitions of leads and lead generation, see What is online lead generation? and for holding lead quality accountable through the handoff, Lead-quality SLAs: how to write one that holds the agency accountable.