The fastest way to break a sales and marketing relationship is to disagree on what a lead means. Marketing sends MQLs. Sales says they are garbage. Leadership blames someone. The cycle repeats every quarter.
The underlying problem is almost always definitional. MQL, SQL, and PQL each represent a different philosophy of lead qualification. Understanding the differences — and choosing the right model for your GTM motion — is one of the highest-leverage fixes a revenue leader can make.
What Is an MQL (Marketing Qualified Lead)?
An MQL is a lead that marketing has determined is worth passing to sales based on behavioral or demographic criteria. Classic MQL definitions include:
- Downloaded a whitepaper + matches target company size
- Attended a webinar + ICP industry
- Reached a minimum lead score based on engagement thresholds
- Filled out a contact form
The MQL model is marketing-centric. It says: “We have generated enough interest that this person is worth a sales conversation.” The problem is that marketing’s definition of “enough interest” often does not match what sales actually needs to close a deal.
What Is an SQL (Sales Qualified Lead)?
An SQL is a lead that sales has accepted and confirmed is worth pursuing based on discovery criteria. The most common framework for SQL qualification is BANT:
- Budget — Do they have funds allocated for this type of purchase?
- Authority — Are we speaking to a decision-maker or influencer?
- Need — Is there a confirmed, articulated problem we can solve?
- Timeline — Are they actively looking to make a decision in the next 90 days?
BANT is not the only SQL framework. MEDDIC, CHAMP, and SPICED are common alternatives. The key point is that SQL qualification requires a human interaction — usually an SDR or AE call — to confirm the criteria. An SQL is a lead that has been vetted.
What Is a PQL (Product Qualified Lead)?
A PQL is a lead that has demonstrated buying intent through product usage. PQLs only apply to companies with a free trial, freemium tier, or PLG (Product-Led Growth) motion. Classic PQL triggers:
- Free user who invited 3+ teammates (network effect = stickiness)
- Trial user who hit the paywall feature 5+ times
- Freemium user who exported data (signals they got value)
- User who completed the core workflow within the first week
PQLs are the highest-quality leads available in a PLG model because they have already experienced the value of the product. Conversion rates from PQL to paid are typically 3–5x higher than MQL-to-close rates.
| Lead Type | Qualification Source | Signal Type | Best For | Avg Close Rate |
|---|---|---|---|---|
| MQL | Marketing | Content/form engagement | Top-of-funnel volume | 1–5% |
| SQL | Sales (after discovery) | BANT/MEDDIC confirmed | Enterprise, complex sales | 15–30% |
| PQL | Product usage | In-app behavior | PLG, SMB, freemium | 20–40% |
The MQL Problem (and Why So Many B2B Teams Are Abandoning It)
MQL as a primary metric creates perverse incentives. Marketing optimizes for volume of MQLs. Sales ignores them because quality is inconsistent. The SLA breaks down. Companies end up with a massive MQL number that has almost no correlation with revenue.
Forrester research found that 99% of MQLs never result in revenue for the typical B2B company. That is not a rounding error — that is a systemic problem with how the metric is defined and incentivized.
The fix is not to eliminate marketing qualification. It is to align the MQL definition tightly with what sales actually needs. A content download alone is not an MQL. A content download from a VP of Sales at a Series B SaaS company in your target vertical who has visited your pricing page — that might be.
How to Define SQLs for a Cold Outbound Motion
In a cold outbound context, the SQL definition needs to account for the fact that leads are being sourced by your team, not inbound. Your SQL criteria should include:
- ICP fit confirmed: Industry, company size, tech stack — all verified, not assumed
- Decision-maker or champion identified: Not just any contact — the person who can buy or influence the buy
- Pain point confirmed: A discovery call or email response that explicitly surfaces a problem you can solve
- Timeline established: Active evaluation or an upcoming trigger event (contract renewal, new hire, funding round)
This connects directly to how you build and run your outbound sequences. Strong SQL criteria make your cold email outreach more targeted because your SDRs know exactly what they are looking for in a response before they hand off to an AE.
Which Model Is Right for Your GTM?
The answer depends on your growth motion:
- Pure outbound / no product trial: SQL is your primary metric. MQL may not exist. Focus on outbound-sourced pipeline that passes BANT.
- Inbound + outbound: Use MQL for inbound leads, SQL as the handoff threshold for both channels. Define the MQL criteria tightly — engagement + ICP fit minimum.
- PLG or freemium: PQL is your highest-priority lead type. Build a workflow that surfaces PQLs to sales the same day they trigger. Consider running outbound to non-converting trial users (reverse PQL outbound).
- Enterprise (complex sales cycle): SQL is king. MQL volume matters less. Focus on opportunity creation rate and pipeline quality.
Aligning Sales and Marketing on Lead Definitions
The conversation that ends the MQL/SQL war is a simple one: get sales and marketing in a room and agree on the minimum criteria a lead must meet before it is handed off. Document it. Build it into your CRM as a required field on the Lead object. Review it quarterly using win/loss data.
When building this alignment, it helps to have a clean GTM architecture. See our guide on GTM engineering for B2B outbound for how to wire this into your full stack.
Conclusion
MQL, SQL, and PQL are not interchangeable — they represent three fundamentally different beliefs about when a lead is ready for sales. The right choice depends on your GTM motion. What matters most is that your definition is precise, agreed upon, and used consistently. Vague lead definitions cost you more in rep time and misaligned effort than almost any other operational failure.
COLDICP builds outbound systems with clear SQL definitions built in from day one. Talk to us.
Frequently Asked Questions
Can a lead be both an MQL and an SQL?
Not simultaneously — they represent different stages. A lead starts as an MQL when marketing qualifies it. If sales then conducts discovery and confirms BANT criteria, it becomes an SQL. The MQL stage is typically short-lived in high-velocity sales motions.
What happens to leads that fail SQL qualification?
They go back to marketing for nurture, or they are recycled into a lower-priority sequence. Strong outbound programs track SQL rejection reasons and use them to improve ICP filters upstream — so fewer poor-fit leads make it into sequences at all.
How many touches does it take to convert an MQL to an SQL?
In B2B SaaS outbound, most SQLs come from 2–5 touchpoints. Cold inbound MQLs (from content) often require 3–7 nurture touches before they are ready for a discovery call. The number varies significantly by deal size and sales cycle length.
What is an SAL (Sales Accepted Lead)?
An SAL is a stage between MQL and SQL — the point where sales formally accepts the lead and commits to working it. In high-volume inbound environments, the SAL stage creates accountability: sales must either accept or reject MQLs with documented reasons, preventing leads from dying in a gray zone.
