One of the most common sources of friction between sales and marketing teams is a disagreement about lead quality. Sales says the leads are bad. Marketing says sales is not following up. Both are often right, and the root cause is usually an undefined or poorly enforced boundary between a marketing qualified lead and a sales qualified lead.
What is a Marketing Qualified Lead (MQL)?
A marketing qualified lead, or MQL, is a prospect who has shown enough interest to warrant further marketing attention but has not yet been confirmed as ready for a sales conversation. An MQL has usually done something active: downloaded a guide, attended a webinar, requested more information, or matched a target profile that suggests interest. The definition of an MQL varies by company, but the key principle is that the prospect has crossed a threshold that makes them worth nurturing, without yet committing a sales rep's time.
What is a Sales Qualified Lead (SQL)?
A sales qualified lead, or SQL, is a prospect who has been assessed against specific criteria and confirmed as worth a sales rep's direct attention. An SQL has typically been verified to have a genuine need your solution addresses, some level of buying authority or influence, a realistic budget, and a timeframe for a decision. The key difference from an MQL is that the SQL has passed a qualification check, not just a behaviour or intent signal.
MQL vs SQL: the core differences
- An MQL is qualified by marketing behaviour and intent signals; an SQL is qualified by a human conversation against defined sales criteria.
- MQLs are typically nurtured with content and automated sequences; SQLs are handed to a sales rep for a direct conversation.
- The bar for MQL is lower: expressing interest or fitting a profile. The bar for SQL is higher: confirmed need, authority, and timeline.
- An MQL that passes a qualification conversation becomes an SQL. Not every MQL will ever become an SQL.
Why the MQL to SQL handoff breaks down
The handoff between marketing and sales is where pipeline most often leaks. Common failure modes include:
- The MQL definition is too loose, so marketing sends over contacts who are nowhere near ready to buy and sales wastes time chasing them.
- The SQL criteria are vague, so reps set their own bar and either cherry-pick or ignore the queue entirely.
- There is no SLA: marketing does not know when or whether sales followed up, so bad leads are never fed back.
- Outbound and inbound leads are treated identically, even though they enter at very different stages of intent.
How to define MQL and SQL for your B2B team
The most effective approach is to define both thresholds together, with input from both sales and marketing, so both teams buy into the definitions and the criteria reflect what actually converts.
- 1.Start with closed-won data. Look at the last 20 to 30 customers and identify what they had in common at the point they became active opportunities. Company size, industry, role, pain point, and trigger event. These become your SQL criteria.
- 2.Work backwards to MQL. What signals did those same customers give at an earlier stage? These become the MQL triggers.
- 3.Write both definitions down in a shared document and make them the foundation of your lead routing rules.
- 4.Set a clear SLA: how quickly should sales follow up on an SQL? What feedback should go back to marketing on every MQL they send?
- 5.Review the definitions quarterly. Markets change, messaging changes, and what made a good lead a year ago may not be the same today.
How B2BLead handles qualification
At B2BLead, every prospect we book as a meeting has been through a human qualification step, not a scoring algorithm. We define your specific SQL criteria at the start of the engagement: company size, industry, role, pain point, and buying stage. Every positive reply from our outbound campaigns is assessed against those criteria before a meeting is booked. The result is that every meeting your team takes is an SQL, not an MQL waiting to be disqualified on the first call.
Frequently asked questions
- What does MQL mean?
- MQL stands for Marketing Qualified Lead. It is a prospect who has shown enough interest or fits enough criteria to be worth further marketing nurturing, but has not yet been confirmed as ready for a direct sales conversation.
- What does SQL mean in sales?
- SQL stands for Sales Qualified Lead. It is a prospect who has been assessed against defined criteria, including need, authority, budget, and timeline, and confirmed as worth a sales rep's time and attention.
- What is the difference between MQL and SQL?
- An MQL is qualified by behaviour or intent signals (downloads, webinar attendance, profile match). An SQL has passed a human qualification conversation against defined sales criteria. MQLs are nurtured by marketing; SQLs are handed to sales for a direct conversation.
- How do you convert an MQL to an SQL?
- An MQL converts to an SQL through a qualification step, typically a human conversation or structured assessment against criteria covering need, authority, budget, and timeline. If the prospect meets the bar, they become an SQL and are handed to a sales rep. If not, they stay in marketing nurture until they become ready.
- Why do MQL and SQL definitions matter?
- Without clear, shared definitions, marketing sends leads that sales ignores, and sales blames marketing for poor-quality pipeline. Shared definitions create alignment, reduce wasted rep time, and give both teams a common language for pipeline conversations.