MQL vs. SQL: Defining the Handoff That Kills Most Pipelines

The most expensive conversation in most B2B companies is the recurring argument between marketing and sales about lead quality. Marketing says they are sending over qualified leads. Sales says the leads are garbage. Both believe they are right, and both are correct, because they are using the same words to mean completely different things.

The undefined MQL/SQL handoff is where B2B revenue gets lost. When marketing's definition of "qualified" and sales's definition of "ready to talk" do not align, the consequences are systemic: sales cherry-picks leads and ignores the queue, marketing loses visibility into what actually converts, pipeline forecasts become fiction, and the mutual blame cycle accelerates until leadership forces a truce that does not fix the underlying problem.

The fix is not a meeting about alignment. It is a contract: a precise, data-driven definition of MQL and SQL that both teams helped build and both teams are accountable to.

---

Defining MQL: Marketing's Output, Not Marketing's Opinion

A Marketing Qualified Lead (MQL) is a lead that has met a defined threshold of fit and engagement sufficient to justify sales attention. Specifically: SDR or inside sales outreach. The definition must be:

1. Objective: Based on measurable criteria, not subjective judgment
2. Mutually agreed upon: Defined jointly by marketing and sales leadership
3. Tied to conversion data: Anchored in what historically converts to pipeline, not what feels like a good lead

The most common mistake in MQL definition is building it entirely on behavioral signals. A lead who downloads three assets, opens five emails, and visits the product page twice is not necessarily an MQL. They might be a researcher, a student, or someone who will never buy. Behavioral signals must combine with fit signals to produce a meaningful MQL threshold.

A working MQL definition structure:

Fit minimum threshold (firmographic requirements that must be met):

• Company size between 50 and 500 employees
• Industry in defined target verticals
• Job title within buying persona range
• Geographic market match

Engagement threshold (behavioral minimum that must be exceeded):

• Lead score of 50 or more points (combining fit and behavioral scoring)
• OR: Explicit high-intent action (demo request, pricing page 3 or more visits, trial sign-up)

A lead must satisfy both the fit minimum AND the engagement threshold to be classified as MQL. Either dimension alone is insufficient. A perfectly fit company whose lead downloaded one blog post is not an MQL. A highly engaged lead from a personal email address with no company data is not an MQL.

MQL timing: Trigger MQL status immediately upon crossing the threshold, with automatic notification to the SDR queue. Latency between MQL trigger and SDR notification directly impacts conversion. Studies consistently show that follow-up response time within the first 5 minutes produces dramatically higher contact rates than follow-up after 30 minutes.

---

Defining SQL: Sales's Confirmation, Not a Rename

A Sales Qualified Lead (SQL) is an opportunity that a sales rep has personally verified meets minimum qualification criteria sufficient to enter the active pipeline. The key distinction: MQL is a system determination; SQL is a human confirmation.

The transition from MQL to SQL happens after an SDR or rep makes contact, runs a qualification conversation, and confirms that the lead meets criteria the scoring model can only partially verify:

• Confirmed need: The prospect has articulated a specific problem your product solves
• Confirmed authority: The contact is a decision-maker or has direct access to one
• Confirmed timeline: The prospect plans to make a decision within a defined window (typically 90 days for active pipeline)
• Confirmed budget feasibility: The prospect has or can access budget in the right range

These are BANT or MEDDIC dimensions that require human conversation to validate. Behavioral scoring can imply them but not confirm them. An SQL is created when a rep completes a discovery call and formally logs the qualification assessment in the CRM.

What SQL is not: SQL is not "the rep decided to pursue this lead." SQL requires documented evidence in the CRM that specific qualification criteria have been met. Without that documentation, pipeline becomes inflated with wishful thinking rather than real opportunities.

---

The SLA Layer: Accountability at Each Stage

Defining MQL and SQL is necessary but insufficient without SLAs that create accountability on both sides of the handoff.

Marketing's SLA to sales: Marketing commits to delivering MQLs that meet the jointly defined fit and engagement criteria. The metric: what percentage of MQLs passed to sales convert to SQL within 30 days? This is marketing's quality metric. If MQL-to-SQL conversion drops below an agreed floor (typically 20 to 30%), marketing investigates and recalibrates.

Sales's SLA to marketing: Sales commits to following up on every MQL within a defined time window. Typically 24 hours for leads scoring above the MQL threshold, 4 hours for leads who made a direct inquiry. The metric: what percentage of MQLs receive a first contact attempt within SLA? This is sales's responsiveness metric.

The feedback loop: When sales disqualifies an MQL after contact, they must document the reason in the CRM. Acceptable disqualification reasons:

• Budget confirmed unavailable
• No authority: contact is too junior and cannot access decision-makers
• No genuine need: the problem described does not match any of your use cases
• Timeline too far out: decision not planned for 12 or more months
• Duplicate or incorrect contact information

"Just does not seem interested" is not an acceptable disqualification reason. It means the lead was not properly engaged, not that it was not qualified.

Review disqualification reasons monthly to identify systemic issues. If 40% of MQLs are disqualified for "no budget," the MQL definition needs a budget signal added. If 30% are disqualified for "no authority," the job title scoring needs recalibration.

---

The SAL: The Stage That Prevents Arguments

Many high-performing teams add a middle stage: SAL, or Sales Accepted Lead. This is the moment a sales rep formally acknowledges receipt of an MQL and commits to pursuing it, before completing the qualification conversation that would make it an SQL.

The SAL stage solves a specific problem: MQLs that are acknowledged by sales but never officially reach SQL because the rep has not completed the CRM qualification steps. Without SAL, there is no visibility into whether the MQL handoff is being worked or ignored.

The SAL process:

1. Lead crosses MQL threshold: automatic notification to SDR queue
2. SDR accepts the MQL (marks it SAL) within 4 hours
3. SDR completes discovery call within 48 hours
4. SDR documents qualification assessment: lead advances to SQL or returns to marketing with a reason code

The SAL acceptance rate tells you whether your MQL criteria are credible to sales. If SDRs are accepting 95% of MQLs, the criteria are working. If they are accepting 60%, they are cherry-picking, which means either the criteria are wrong or the SDRs need training.

---

Rebuilding the Definition When It Is Broken

If your current MQL/SQL definitions are producing a broken handoff, here is the rebuild process.

Step 1: Pull 6 months of closed-won deals. Map backwards to the MQL event for each one. What fit and engagement signals existed at the point of MQL designation?

Step 2: Pull 6 months of MQLs that were disqualified after sales contact. What signals were present that were not predictive of a real opportunity?

Step 3: Run a joint workshop with marketing and sales leadership. Present both analyses. Let the data drive the threshold discussion, not intuition.

Step 4: Write the new MQL criteria in plain language. Both teams sign off. Post it somewhere everyone can see it.

Step 5: Run the new criteria on the last 90 days of leads. Identify how many would have been classified differently. Discuss the implications with both teams.

Step 6: Implement the new criteria, set SLAs, and build a 60-day review into the calendar from day one.

---

Common Mistakes in MQL/SQL Definition

Defining MQL by volume, not quality: When marketing is measured on MQL volume, incentives push toward lower thresholds that produce more leads, even if those leads do not convert. Measure marketing on MQL-to-SQL conversion rate, not MQL count.

Not updating the definition after product or market changes: An MQL definition built for your 2022 SMB-focused product may not be right for your 2025 mid-market expansion. Review and update definitions annually at minimum, and whenever you make a significant product or market shift.

Letting SQL become a rep's discretionary judgment: If SQL creation is not tied to documented qualification evidence, different reps will create SQLs at different standards. Pipeline forecasts become unreliable. Require CRM documentation of specific qualification criteria for SQL status, not just the rep's intent to pursue.

Ignoring the SAL stage: Without SAL, you have no visibility into handoff acceptance. MQLs either convert to SQLs or disappear. The SAL stage creates accountability for the transition and gives you the data to identify whether the problem is MQL quality or SDR follow-through.

---

MQL and SQL are not technical definitions. They are organizational contracts. A lead that marketing calls qualified must genuinely be worth a sales rep's time. A lead that sales accepts must be worked with documented qualification.

Get the definitions right, add SLAs with accountability, and build in a feedback loop. That is how you turn the most expensive argument in B2B revenue into a repeatable system.