MQL-to-SQL Handoff SLAs That Actually Work

The MQL-to-SQL handoff is where most revenue leaks. Marketing passes leads, sales ignores them, and both teams blame each other when pipeline goals slip. The problem is rarely effort - it's the absence of a shared, enforced agreement about what "qualified" means, when follow-up must happen, and what happens when either side drops the ball.

This post walks through how to build MQL-to-SQL SLAs that have teeth: clear definitions, realistic timelines, measurable accountability, and a review cadence that keeps both teams honest.

Start With a Shared Definition of MQL and SQL

SLAs collapse when marketing and sales are secretly using different definitions. Marketing might consider an MQL anyone who downloads a whitepaper and scores above a threshold. Sales might consider an SQL only someone who has budget authority and a defined project timeline. If those definitions aren't written down and agreed upon, every handoff is a negotiation.

Define MQL Criteria in Writing

Your MQL definition should specify:

• Fit criteria - firmographic signals like company size, industry, job title range, and geography that indicate the lead matches your ICP
• Intent criteria - behavioral signals like page visits, content downloads, pricing page views, or demo requests that indicate active interest
• Threshold logic - the minimum combination of fit and intent required for the MQL status to trigger
• Disqualifiers - explicit exclusions like competitors, students, existing customers, or contacts already in active deals

Define SQL Criteria With Equal Specificity

SQL criteria should describe what sales has verified, not just what marketing has inferred. Common SQL gates include confirmed budget authority, an identified need or pain point, a realistic timeline for purchase, and an active conversation with a decision-maker. Whatever your criteria, write them down in a shared document that both teams can reference - and revisit them at least quarterly.

A visual dependency map of your lead scoring and lifecycle stage workflows can expose where your MQL logic sits across multiple automation rules, which makes it much easier to audit whether the scoring criteria you documented actually match what your systems are doing.

Set Realistic, Tiered Follow-Up Timelines

The most common SLA failure is a single blanket rule like "sales must follow up within 24 hours." That ignores the reality that not all MQLs are equal, and sales prioritization is a real constraint.

Tier Your MQLs by Urgency

A tiered SLA structure works much better in practice:

• Tier 1 - High intent signals (demo requests, pricing page + contact form, free trial signups): follow-up within 4 business hours
• Tier 2 - Moderate intent signals (content download + return visit, webinar attendance + engagement): follow-up within 1 business day
• Tier 3 - Lower intent, fit-based MQLs (lead scoring threshold met, mostly fit criteria): follow-up within 2-3 business days

This tiering respects both the urgency of hot leads and the bandwidth of your sales team. It also makes SLA compliance measurable - you can report on each tier separately rather than averaging across wildly different lead types.

Define What "Follow-Up" Actually Means

Another common failure: the SLA says "contact the lead" but doesn't define what counts. Does a LinkedIn connection request count? Does leaving a voicemail count? For SLA reporting purposes, define follow-up as a logged outbound activity - call attempt, email sent, or LinkedIn message - recorded in your CRM within the specified window. This closes the loophole where a rep claims to have "reached out" without any logged activity to verify it.

Build in Accountability Mechanisms

An SLA without consequences is a suggestion. Both sides need skin in the game.

Marketing Accountability

Marketing should be accountable for:

• MQL quality - measured by the percentage of MQLs that convert to SQL within a defined window (30 or 60 days is common)
• MQL accuracy - the percentage of MQLs that sales accepts rather than rejects on grounds of poor fit
• Routing speed - the time between a lead meeting MQL criteria and appearing in the sales queue

If your MQL-to-SQL conversion rate is consistently below target, that's a signal that your scoring model needs recalibration, not that sales is slow to follow up.

Sales Accountability

Sales should be accountable for:

• SLA compliance rate - the percentage of MQLs contacted within the agreed window by tier
• Rejection quality - when a rep rejects an MQL as unqualified, they must log a specific reason, not just click "not a fit"
• Speed-to-SQL - the average time from first contact to SQL conversion

A flow timeline view of your lifecycle stage transitions can surface whether leads are stalling in the MQL stage longer than your SLA allows, which helps you identify whether the bottleneck is routing, rep behavior, or definition gaps.

Establish a Joint Review Cadence

SLAs go stale. Market conditions change, your ICP evolves, product launches shift what "qualified" means. A quarterly review cadence between marketing ops and sales ops is the minimum - monthly is better in a high-growth environment.

What to Review Each Quarter

• MQL-to-SQL conversion rate by source and tier
• SLA compliance rate by tier and by rep
• Rejection reason breakdown - look for patterns that suggest a definition mismatch
• Average time to first contact and time to SQL
• Pipeline influenced by MQL channel versus direct sourced

How to Run the Review

Bring a data pull, not opinions. Prepare a one-page summary of the above metrics, flag any tier where performance fell below target, and come with a hypothesis about why. The goal isn't to assign blame - it's to identify whether the problem is in the definition, the process, or the tooling, and then make a specific change to test.

Documenting these reviews alongside your SLA agreement keeps both teams anchored to the same history. Teams working at RevOps scale often find that a shared documentation layer prevents the tribal knowledge problem where only one person remembers why a rule was set the way it was.

Common Failure Modes to Avoid

Even well-designed SLAs break down in predictable ways:

• No routing automation - if reps have to manually claim leads from a queue, SLA compliance will depend on whoever checks Slack first
• SLA lives in a deck, not the CRM - if the follow-up window isn't enforced through task creation, alerts, or ownership rules in your CRM, it will be ignored under pressure
• Rejection reasons are vague - "not a fit" as a rejection reason tells marketing nothing; require structured reasons tied to your fit criteria
• No feedback loop on rejected MQLs - marketing should see rejected leads and the reasons within days, not at the end-of-quarter review
• Threshold set too low to appease both teams - if marketing sets a low MQL bar to hit volume targets and sales rejects most of them, the SLA is covering for a broken scoring model

Getting the MQL-to-SQL handoff right is one of the highest-leverage things a RevOps team can do. When definitions are shared, timelines are tiered, and both sides are held to specific metrics, pipeline predictability improves significantly - and the finger-pointing stops.