If your marketing team is generating leads your sales team is rejecting, the problem isn’t lead volume. It’s the definition of what counts as a lead. Here’s how MQLs and SQLs actually work — and how to align them.
Here’s the conversation I have monthly with B2B revenue leaders.
Marketing says: “We hit our lead target. 480 MQLs delivered this quarter.”
Sales says: “Of those 480 leads, 90% weren’t qualified. We worked maybe 50 of them. Marketing is wasting our time.”
Marketing says: “Sales doesn’t follow up on our leads.”
Sales says: “Marketing doesn’t understand what a real lead looks like.”
And around and around it goes — both sides convinced the other side is broken, both sides partially right, both sides missing the structural problem underneath the argument.
The structural problem is almost always the same: the company hasn’t actually defined what counts as an MQL vs. an SQL in a way both teams agree on. So marketing optimizes for one definition and sales evaluates against another. The handoff fails. Pipeline suffers. Both teams blame the other.
After 15 years working with B2B revenue teams, here’s the playbook for actually fixing this — what MQL and SQL really mean, where most companies get it wrong, and how to align both teams around definitions that produce pipeline instead of arguments.
What Is an MQL? What Is an SQL?
The textbook definitions, then the way they actually work.
Marketing Qualified Lead (MQL)
A lead that has demonstrated enough interest or fit to be worth sales investigating. Typically signaled by behaviors:
- Filled out a high-intent form (demo request, pricing page, contact us)
- Downloaded mid-to-bottom-funnel content (case study, ROI calculator, competitive comparison)
- Attended a webinar or event
- Visited high-intent pages multiple times (pricing, customer logos)
- Engaged with sales-aligned content (security overview, implementation guide)
An MQL is not a customer. It’s a signal that this person might be worth sales’ time. Marketing’s job is to source MQLs at scale.
Sales Qualified Lead (SQL)
An MQL that sales has reviewed, contacted, and confirmed has both:
- A real fit (right industry, company size, role, technology stack, geography)
- A real timing window (active project, budget approved or approvable, decision timeline within sales’ working horizon)
An SQL is what enters the pipeline. SQLs are what get worked. SQLs are what convert to opportunities.
The handoff: marketing delivers MQLs → sales reviews and qualifies → MQLs that pass sales’ bar become SQLs → SQLs become opportunities → opportunities become customers.
When this works, pipeline flows smoothly. When it doesn’t, both teams are convinced the other is failing.
The Three Failure Modes That Quietly Kill Pipelines
After auditing dozens of B2B revenue teams, the same three patterns show up over and over.
Failure Mode 1: The MQL Definition Is Too Loose
Marketing defines an MQL as anyone who downloaded an ebook. Sales gets 500 of these per month. Half are students writing research papers; another quarter are competitors. The MQL volume looks great on the dashboard. The SQL conversion rate is 4%.
The diagnostic: if your MQL-to-SQL conversion rate is below 15%, your MQL definition is too loose. You’re optimizing marketing for a vanity metric that doesn’t represent real intent.
Failure Mode 2: The SQL Definition Is Implicit
Sales has a definition of SQL but it lives in their heads, not in writing. Marketing thinks they’re delivering qualified leads; sales thinks marketing doesn’t understand the business. Every individual rep has slightly different qualification criteria. The system can’t be optimized because the standard isn’t documented.
The diagnostic: if you can’t get three salespeople to agree on what an SQL is, you don’t have an SQL definition — you have folklore.
Failure Mode 3: The Handoff Process Is Broken
Marketing delivers MQLs to sales via Salesforce, but reps don’t see them for 3 days. Or marketing dumps 200 leads on a Friday afternoon and sales works the 10 they have time for. Or the routing rules send manufacturing leads to a SaaS-focused rep.
The leads might be perfectly qualified. The process is killing them.
The diagnostic: if you can’t tell me how long it takes for an MQL to be contacted by a rep, the handoff process is broken. Speed-to-lead is the single biggest predictor of conversion in B2B.
How to Align MQL and SQL Definitions: A Working Playbook
Six moves. Don’t skip steps.
Move 1: Run a Closed-Won Audit
Pull your last 50 closed-won customers. For each, document:
- Source: how did the deal originate? (inbound, outbound, referral, partner)
- Initial trigger: what was the first signal of intent? (form fill, email response, networking conversation)
- Time to first contact: how fast was the first sales touch?
- Fit attributes: industry, company size, role of buyer, geography, tech stack
- Timing signal: what was happening in their business that made now the right time?
After 50 customers, patterns emerge. You can see what an actual MQL looks like in your business — not what a marketing automation textbook says it looks like.
Move 2: Define MQL by Behavior + Fit, Not Just Behavior
Most MQL definitions are pure behavioral (“downloaded the ebook”). The strongest definitions blend behavior AND fit.
Generic MQL definition (loose): “Downloaded any piece of content.”
Strong MQL definition (tight): “Filled out a demo request form AND works at a B2B SaaS company with 50-500 employees AND has a title containing ‘VP Sales,’ ‘CRO,’ or ‘Director of Sales.'”
The second definition is harder to hit. But it represents real intent + real fit. Your MQL-to-SQL conversion rate will be 40%+ instead of 4%.
Move 3: Document the SQL Bar in Writing
Sales and marketing should sit down and write a 1-page document that defines exactly what makes a lead an SQL. Specifically:
- Fit criteria (industry, size, role — typically from your ideal customer profile)
- Timing criteria (what makes “now” the right time for this prospect)
- Disqualifiers (what makes a lead NOT an SQL — usually wrong industry, too small, wrong region, no budget signal)
The document should be specific enough that any rep can apply it to any MQL and get the same answer.
Move 4: Build a Scoring Model (Optional but Powerful)
Once the definitions are clear, you can build a scoring model that automates the qualification work. Each behavior + fit attribute gets a point value:
- Demo request: 30 points
- Visited pricing page 2+ times: 15 points
- Title contains “VP” or “Director”: 10 points
- Company size 50-500: 10 points
- Industry = SaaS: 10 points
- Geography = North America: 5 points
Leads that hit a threshold (say, 50 points) become MQLs automatically. Leads that hit a higher threshold (say, 80 points + sales review) become SQLs.
This isn’t required — but it dramatically reduces the “why didn’t sales follow up on this lead?” arguments by making the qualification explicit and rule-based.
Move 5: Set Speed-to-Lead Standards
The single biggest predictor of MQL-to-SQL conversion is how fast the first contact happens after the MQL trigger.
The benchmarks:
– MQL contacted within 5 minutes: ~20% likely to convert to opportunity
– MQL contacted within 1 hour: ~10% likely to convert
– MQL contacted within 1 day: ~3% likely to convert
– MQL contacted within 1 week: ~1% likely to convert
Companies with disciplined 5-minute response times capture meaningfully more pipeline from the same MQL volume. Companies that respond in 1-3 days are leaving 80%+ of potential pipeline on the table.
This is why the follow-up sequence design and SDR rapid-response workflows matter so much — most companies have decent MQL generation and terrible MQL follow-through.
Move 6: Set Up the Feedback Loop
Marketing needs to know what happened to every MQL. Did it convert? Did sales reject it? Why?
The simplest version: a CRM field on every MQL with a status (Working, Disqualified, Converted to SQL, Closed-Won, Closed-Lost) and a reason code (Wrong Industry, Wrong Size, Bad Timing, etc.).
Marketing reviews this monthly. Adjusts the MQL definition based on what’s converting and what’s bouncing. Over 90 days, the MQL definition tightens and the MQL-to-SQL conversion rate rises.
MQL vs. SQL: The Quick-Reference Comparison
Side-by-side so the difference is unambiguous:
| Dimension | MQL (Marketing Qualified Lead) | SQL (Sales Qualified Lead) |
|---|---|---|
| Who qualifies it | Marketing (often automated) | Sales (after review) |
| Source of qualification | Behavioral + fit signals | Direct contact + assessment |
| Confidence level | Medium — interest signal | High — fit + timing confirmed |
| Volume | Higher | Lower |
| Sales involvement | None or light (auto-routing) | Full review, contact, assessment |
| Conversion to opportunity | 15-30% (healthy) | 40-70% (healthy) |
| Where it sits in the pipeline | Top — pre-pipeline | Pipeline-ready |
| Time investment per lead | Low | High |
| What kills it | Loose definition, slow follow-up | Bad fit despite passing MQL bar |
A common rule of thumb: for every 100 MQLs delivered, 20-40 become SQLs in a healthy system. Below 15% conversion: MQL definition is too loose. Above 50% conversion: MQL definition is too tight (you’re under-sourcing).
Common MQL/SQL Mistakes
Six patterns that consistently break the handoff. Audit your team against these.
- Measuring MQL volume in isolation. Without MQL-to-SQL conversion as the counterweight, marketing optimizes for vanity. Always report both metrics together.
- Letting reps disqualify silently. When sales rejects a lead, they need to document the reason. Without it, marketing can’t improve the MQL definition.
- Inconsistent SQL bar across reps. If three reps look at the same MQL and disagree on whether it’s an SQL, you have a process problem, not a lead problem. Write the SQL definition down.
- Ignoring fit in favor of behavior. A lead that downloads every ebook but works at the wrong-size company is not an MQL. Behavior + fit, not behavior alone.
- Slow follow-up. A perfect MQL contacted 3 days late is worse than a marginal MQL contacted in 5 minutes. Speed-to-lead is the entire game.
- No closed-loop feedback. Marketing keeps optimizing the funnel based on top-of-funnel metrics, never knowing what’s actually closing. The closed-loop attribution is what makes the system improvable.
The underlying playbook here connects directly to broader B2B lead generation discipline — MQL/SQL definitions, fit criteria, and speed-to-lead are all part of one system. The single biggest leverage point in most B2B pipelines isn’t generating more leads — it’s tightening the definitions and accelerating the response on the leads you already have. Pair this with a strong outreach strategy and the math compounds. The same logic shows up in lead nurturing — most “not ready yet” MQLs become SQLs 30-90 days later if the follow-up cadence is right. And once SQLs convert, your follow-up email discipline determines whether the opportunity stays alive through the typical 5-7 touch B2B sales cycle.
How MQLs and SQLs Fit Into the Broader Pipeline
The full funnel that most companies should be measuring:
1. Lead — anyone in the database (could be from anywhere)
2. MQL — passed the marketing-qualified threshold (behavior + fit signal)
3. SQL — passed sales review (fit + timing confirmed)
4. Opportunity — sales is actively working a defined deal with a stage, amount, and close date
5. Customer — closed-won
The conversion rates between each stage are what tell you where the leaks are:
| Stage Transition | Healthy Conversion Rate | What to Check If Below |
|---|---|---|
| Lead → MQL | 5-20% | MQL definition (likely too loose if hitting 30%+; too tight if below 5%) |
| MQL → SQL | 20-40% | Fit criteria, speed-to-lead, sales follow-up discipline |
| SQL → Opportunity | 50-70% | Sales process, qualification rigor, real-time intent signals |
| Opportunity → Customer | 20-30% | Sales execution, competitive positioning, pricing |
If conversion is healthy at every stage, the pipeline is working. If one stage is below benchmark, that’s where the fix is. Most companies have 2-3 leaky stages they haven’t diagnosed.
MQL vs. SQL FAQ
What’s the difference between an MQL and an SQL?
An MQL (Marketing Qualified Lead) is a lead that has shown enough interest or fit (via behavior and demographic signals) for marketing to hand it off to sales for evaluation. An SQL (Sales Qualified Lead) is an MQL that sales has reviewed and confirmed has both real fit and real timing — meaning it’s worth working as a pipeline opportunity. MQLs are sourced; SQLs are vetted. The conversion rate between them is one of the most important metrics in B2B revenue.
What’s a good MQL-to-SQL conversion rate?
20-40% is healthy. Below 15% suggests the MQL definition is too loose (you’re including too many people who don’t represent real intent). Above 50% may suggest the MQL definition is too tight (you’re under-sourcing and missing opportunities). The right benchmark varies by industry and motion — long sales cycle enterprise tends to run lower; faster sales motions tend to run higher.
Who is responsible for creating the MQL and SQL definitions?
Both marketing and sales — together. The most common failure mode is one team writing the definitions alone (usually marketing) and the other team disagreeing without saying so. The right workshop: marketing, sales, and revenue ops in a room, looking at 30-50 recent closed-won customers, then writing the MQL and SQL definitions based on the patterns. Quarterly reviews to refine.
How do I move an MQL to an SQL?
Three steps: (1) sales reviews the MQL within minutes (or hours, max), (2) sales makes contact via email, phone, or LinkedIn to validate fit and timing, (3) if fit and timing both check out, the lead is reclassified to SQL and enters the pipeline as an early-stage opportunity. If either fit or timing fails, the lead is disqualified with a reason code documented for marketing’s feedback loop.
Should every B2B company use MQL and SQL?
Yes — for any B2B company with both marketing and sales functions. Even a 5-person company benefits from having explicit definitions of when marketing’s job ends and sales’ job begins. Without the definitions, leads fall through the cracks, both teams get frustrated, and the pipeline math becomes impossible to optimize.
How is SQL different from an opportunity?
An SQL is a lead that’s been confirmed as worth pursuing — fit and timing both check out. An opportunity is the next stage: sales has identified a specific deal (a problem the prospect is trying to solve, a budget, a timeline, a decision process) and is actively working it through pipeline stages. SQLs are pre-opportunity; opportunities are pipeline. Conversion rate from SQL to opportunity should be 50-70% in a healthy system.
What if marketing and sales can’t agree on definitions?
That’s the problem you actually have — and it’s never solved by either team writing the definitions alone. The fix is a joint workshop: pull 30-50 recent closed-won customers, look at the patterns, and write the definitions based on what’s actually closed. Reality breaks the deadlock. If both teams can’t get into a room together to work through it, that’s an organizational problem that needs leadership escalation — not a definitions problem.
Are MQLs and SQLs still relevant in product-led growth (PLG) companies?
Yes — but the definitions look different. In PLG, an MQL might be “signed up for a free trial and invited 2+ teammates”; an SQL might be “trial team is using the product daily AND has 50+ employees AND a usage pattern that suggests they’re approaching the paid tier.” The signals are product-usage-based instead of marketing-content-based, but the underlying logic of “marketing/product hands off → sales qualifies → pipeline” still holds.
The Bottom Line
MQL vs. SQL isn’t a definition argument. It’s the structural agreement between marketing and sales about how leads flow through the company.
When the definitions are tight and documented, conversion is high, both teams are aligned, and pipeline grows predictably. When the definitions are loose or implicit, marketing optimizes for vanity volume, sales rejects most of what it receives, and both teams blame each other while pipeline stagnates.
The fix isn’t more leads. It’s tighter definitions, faster handoff, and a closed feedback loop. Run that for 90 days and conversion rates double — usually without any change to marketing spend or sales headcount.
Rooting for you,
Tom