MQL vs SQL vs PQL: Lead Stages Explained Simply
MQL, SQL, and PQL explained for B2B teams: what each lead stage means, how to define exit criteria, and how to end the handoff fights between teams.
- MQL and PQL are evidence-based entry claims; SQL is a human acceptance decision.
- Write exit criteria and SLA clocks for every stage boundary.
- Give PQLs their own faster lane with precedence rules to avoid double counting.
- Timestamp every transition and keep definitions stable across quarters.
The Three Stages in Plain Language
An MQL, or marketing qualified lead, is a person whose profile and behavior suggest they are worth a sales conversation, judged by marketing's criteria such as a score threshold or a high-intent action. An SQL, or sales qualified lead, is one that sales has actually examined and accepted as worth pursuing. A PQL, or product qualified lead, is a user whose behavior inside your product signals buying readiness, like hitting a usage limit or inviting teammates.
The key insight is that these are not three ranks of the same thing. MQL and PQL are entry claims made by different evidence sources, marketing signals versus product usage. SQL is an acceptance decision made by a human with quota.
Definitions Are Cheap, Exit Criteria Are Everything
Most handoff fights are not about what MQL means, they are about what happens at the boundary. For each stage, define the exit criteria in writing: what exactly promotes a lead, what demotes or recycles it, and how long sales has to accept or reject an MQL before it escalates.
Require a rejection reason on every declined MQL. Those reasons are the highest-value feedback loop in the funnel, because they tell marketing precisely which scoring signals and campaigns produce leads sales will not touch.
Where PQLs Fit Without Breaking the Model
If you have a free trial or freemium product, PQLs deserve their own lane, not a bolt-on to the MQL flow. Product signals like activation milestones, seat growth, and usage limits are stronger evidence of intent than any whitepaper download, and they should route faster and to reps trained to have a product-context conversation.
Beware double counting. A user can be both an MQL and a PQL, and if both routes fire you get duplicate tasks and confused outreach. Decide precedence rules up front, and let the strongest signal own the handoff.
Instrument the Stages or the Argument Never Ends
Every stage transition needs a timestamp field in the CRM, set by automation rather than memory. With entry and exit timestamps you can measure conversion rates and velocity between stages, which turns the quarterly blame session into an actual funnel review.
Then review the definitions twice a year at most. Teams that redefine MQL every quarter destroy their own trend lines and reopen the treaty negotiations each time. Stability of definitions is worth more than marginal precision.
- MQL and PQL are evidence-based entry claims; SQL is a human acceptance decision.
- Write exit criteria and SLA clocks for every stage boundary.
- Give PQLs their own faster lane with precedence rules to avoid double counting.
- Timestamp every transition and keep definitions stable across quarters.
Frequently asked questions
What is the difference between MQL, SQL, and PQL?
An MQL is a lead marketing judges ready for sales based on profile and behavior, an SQL is a lead sales has reviewed and accepted, and a PQL is a lead qualified by product usage signals like activation or seat growth. MQL and PQL differ by evidence source, while SQL marks a human acceptance decision. Together they describe a handoff, not a hierarchy.
Are MQLs still a useful concept?
Yes, as long as they are defined with sales and graded on downstream conversion rather than counted as a vanity total. The MQL backlash is really about teams optimizing MQL volume instead of SQL acceptance and pipeline. Keep the stage, fix the incentive.
How fast should sales work an MQL or PQL?
Set an explicit SLA per stage and enforce it with automation, since unworked qualified leads decay quickly. Many teams use clocks measured in minutes or hours for high-intent signals like demo requests and PQLs, and a day or two for lower-intent MQLs. The specific number matters less than measuring breaches.
Can a lead be both an MQL and a PQL?
Yes, and it happens constantly in product-led companies where a trial user also downloads content. Define a precedence rule so only one route fires the handoff, usually letting the product signal win because it carries stronger intent. Without precedence, the lead gets two owners and duplicated outreach.
Liked this? Get the next play in your inbox.
One signal-driven GTM play every week. No fluff, no spam, unsubscribe anytime.
Operator-built
Built by someone who runs the playbook, not an agency reselling labor.
You own it
Your data, your CRM, your infrastructure. The system is yours.
No lock-in
Start with a free audit. No multi-month retainer to find out it works.
Privacy-first
Your data stays yours. We pen-test our own funnel before we touch yours.
▸ STOP READING. START PLAYING.
Don't just read about it. Drop your site below and see the revenue you're leaving on the table, live.