MQL to SQL: Why It Fails & How to Fix It

Your company generates 300 leads/month from marketing. Sales says 80% are garbage. Marketing says sales just doesn't follow up. Meanwhile, 240 leads a month fall into a black hole—never contacted, never qualified, just... gone.

This is the MQL-to-SQL problem. And it's fixable in 4 weeks. Here's how.

Why Most Companies Have Broken MQL-to-SQL Conversion

There are usually 3 reasons:

Reason 1: No clear definition of MQL

Marketing says: "An MQL is someone who filled out a form." Sales says: "An MQL is someone ready to talk to us." These are completely different things.

Reason 2: No sales-marketing SLA

An SLA (Service Level Agreement) defines the handoff. When marketing says a lead is qualified, sales commits to contact within X hours. Without an SLA, leads sit in a queue until sales gets around to them—if ever.

Reason 3: No feedback loop

Marketing doesn't know which leads actually converted to customers. They optimise for "more leads" without knowing if those leads are any good. Sales complains about quality but never sits down with marketing to define quality. They operate in silos.

Fix these three, and your MQL-to-SQL conversion will jump from 20% to 50%+ in 8 weeks.

Step 1: Define MQL (With Sales Involved)

An MQL should answer three questions:

1. Fit: Are they in our target company size, industry, and geography?
2. Intent: Have they shown interest in the last 30 days (form fill, email open, content download)?
3. Authority: Are they a decision-maker or influencer (not a random person)?

An MQL is someone who scores YES on at least 2 of 3, preferably all 3.

Step 2: Define SQL

An SQL is ready for sales conversation. They've taken an explicit action:

• Requested a demo
• Filled out a "contact us" form (not a gated content form)
• Booked a calendar meeting
• Replied to an email from sales
• Participated in a live chat with your team

Or they meet MQL criteria PLUS have shown recent engagement 3+ times in a 2-week period.

Key difference: MQL = qualified lead. SQL = lead ready for sales conversation now. Not all MQLs will become SQLs immediately—some need nurturing first. But a lead that meets SQL criteria should be contacted the same day.

Step 3: Create the SLA

This is the binding agreement between marketing and sales. Here's a template:

Step 4: Route Leads Automatically

Don't rely on manual handoffs. Use your CRM and marketing automation to route automatically:

• SQL-qualified leads → Instant Slack notification to assigned SDR + auto-add to sales sequence
• MQL leads → Auto-enroll in nurture email sequence
• Low-fit leads → Auto-tag, hold for monthly re-qualification

The goal: Remove the human delay. A 4-hour sales response is meaningless if the lead sits in a Salesforce queue for 2 days before being assigned.

Step 5: Track and Report

Create a weekly dashboard showing:

• MQLs generated (by source)
• MQLs converted to SQL (conversion rate %)
• SQLs converted to closed-won (by sales rep)
• Average time from MQL → SQL
• Average time from SQL → Closed

This transparency forces accountability. When you see that "form fill from webinar" has a 50% MQL-to-SQL conversion but "form fill from gated PDF" has 8%, you know where to invest.

Real Case Study: 20 → 75 SQLs/Month

A logistics SaaS was generating 300 MQLs/month but only 20 SQLs. Sales was overwhelmed. Marketing thought sales was lazy. Here's what we fixed:

The broken process:

• MQL = anyone who filled a form (no qualification)
• No SLA; sales responded when they had time (avg 5–7 days)
• No feedback loop; marketing didn't know which MQLs actually converted
• Leads sat in Salesforce for days before being assigned

What we fixed:

• Redefined MQL: Form fill + company size 50-500 + job title is director+ (reduced pool from 300 → 120/month, but all qualified)
• Created SLA: 4-hour response for demo requests, 48-hour for other MQLs
• Auto-routing: SQLs auto-assigned to next available SDR + Slack alert
• Weekly review: Marketing and sales reviewed conversion rates every Friday

Results (Month 3):

• MQL-to-SQL conversion: 20% → 65%
• SQLs/month: 20 → 75
• Sales response time: 5 days → 3.5 hours avg
• Deal cycle shortened: 75 days → 52 days

The best part? Both sales and marketing were happy. Sales got better-qualified leads. Marketing got credit for real pipeline, not just lead count.

5 Common Mistakes to Avoid

Mistake 1: Making MQL too broad. "Anyone who visited the website" is not an MQL. If your MQL pool is 500+ leads/month, your definition is too loose.

Mistake 2: Making SLA unrealistic. "Sales responds to every MQL within 1 hour" sounds good but won't happen. Make it enforceable (4–24 hours, depending on lead type).

Mistake 3: Ignoring disqualification. Leads that go 30 days without engagement are cold. Mark them as disqualified and move on. Don't let dead leads clog your pipeline.

Mistake 4: No feedback loop. Sales converts lead to customer, but marketing never hears about it. Do weekly or monthly review: "Of the 120 MQLs we sent this month, 78 became SQLs and 12 closed. What worked?"

Mistake 5: Expecting perfection month 1. It takes 4–6 weeks to lock in a good MQL-to-SQL process. There will be friction. Stick with it.

30-Day Action Plan

• Week 1: Sales + marketing workshop to define MQL and SQL. Agree on definition. Write it down.
• Week 2: Create and sign the SLA. Agree on response times, follow-up schedules, and disqualification rules.
• Week 3: Implement auto-routing in your CRM/marketing automation. Test with real leads.
• Week 4: Run first full week under new process. Review metrics. Adjust.

Need help designing your MQL-to-SQL process? This is core to my MarTech implementation service. I've built this for 10+ B2B companies and have SLA templates ready to go.