TL;DR: The average MQL-to-SQL conversion rate is 13%. Hitting or beating that requires shared criteria between marketing and sales, a behavioral scoring model built from closed-won data, nurture tracks that move leads through intent stages, and a clean handoff SLA.

MQL to SQL: How to Convert Marketing Qualified Leads Into Sales Opportunities

Last updated: June 2026

Most revenue teams treat MQL and SQL as arbitrary CRM fields someone set up years ago. Defined correctly, they force alignment between marketing spend and pipeline quality.

What Makes a Lead Marketing Qualified vs. Sales Qualified

A Marketing Qualified Lead (MQL) is a contact who fits your ICP and has engaged enough to justify marketing's attention, but not enough to warrant a sales conversation yet. A Sales Qualified Lead (SQL) is a lead that sales has reviewed and agreed to pursue: there is budget, authority, a relevant use case, and some level of active intent.

The line between the two varies by company, but the core logic is the same. MQL status is marketing's way of saying "this person is worth nurturing." SQL status is marketing's way of saying "sales, take this." The problem is most teams never explicitly agree on where that line sits.

Without written criteria, the handoff becomes noise. Sales ignores low-quality MQLs. Marketing inflates the MQL count to hit pipeline targets. Both teams argue about lead quality in the quarterly review. The fix is a shared definition.

MQL criteria typically combine two signals:

• Fit: Does the lead match your ICP? Title, company size, industry, tech stack.
• Behavior: Has the lead shown intent? Page visits, content downloads, demo requests, email clicks.

A lead that fits but has not engaged stays in a nurture sequence. A lead that has engaged but does not fit gets deprioritized. MQL status requires both.

SQL criteria layer in readiness signals: BANT (Budget, Authority, Need, Timeline) or similar frameworks. Many teams add a third requirement: a completed discovery call, or at least a two-way exchange like a reply to a sequence email or a demo booking.

Think of MQL-to-SQL as a two-step gate. Marketing owns the MQL gate (fit + behavior). Sales owns the SQL gate (readiness + intent). Both gates need written criteria your entire GTM team reviews at least quarterly.

How to Set MQL and SQL Criteria Your Team Actually Agrees On

The most common failure mode: marketing sets MQL criteria unilaterally, sales rejects 70% of the leads as "not ready," and the relationship degrades from there. Fix it by building the criteria together, with sales as the validation layer.

Start with your closed-won data. Pull the last 50 deals and map what the contact looked like at first sales touch. What was their title? Company size? What did they do before sales reached out? These are your MQL criteria, not best-guess templates from a playbook.

Define MQL criteria across two dimensions:

1. Fit score (static): Title match (VP Sales, Head of RevOps, Founder), company size (20–500 employees), industry, tech stack signals (uses Salesforce, HubSpot, etc.)

2. Behavioral score (dynamic): Weighted points for actions: +10 for demo request, +8 for pricing page visit, +5 for content download, +3 for email click, +2 for return visit. Set an MQL threshold. for example, fit score of 4/5 plus behavioral score of 15 or more.

SQL criteria should map to what sales learns in a first conversation. BANT is a reasonable starting framework, but many B2B SaaS teams simplify it: (1) Does this person have decision-making authority? (2) Is there a live initiative driving urgency? (3) Does their timeline fit your sales cycle?

Document both as a shared spec, get sales leadership to sign off, and review quarterly. Learn how to build ICP-aligned qualification criteria.

Building a Lead Scoring Model That Reflects Sales Readiness

Lead scoring works when it is built from real conversion data, not guesswork. Here is a practical framework.

Step 1: Score fit separately from behavior.

Fit is mostly static: company size, title, industry. Behavior is dynamic: actions the lead has taken. Combining them into one score makes it harder to diagnose problems. When conversion rates drop, you want to know whether it is a fit problem or an engagement problem.

Step 2: Weight your behavioral signals by intent proximity.

• High-intent actions (demo request, pricing visit, trial start): 10–15 points
• Mid-intent actions (content download, webinar attendance): 5–8 points
• Low-intent actions (blog visit, email open): 1–3 points
• Decay: no activity for 30 or more days removes 5 points per 30-day window

Step 3: Set your MQL threshold based on SQL conversion data.

Pull your last 100 MQLs. What score range produced the most SQLs? If leads scoring 20–30 convert at 25% to SQL but leads scoring 10–20 convert at 5%, your threshold should be closer to 20. Let the data set the number, not a round figure someone picked during setup.

Step 4: Integrate with your CRM.

In HubSpot, use custom properties and workflow-based scoring. In Salesforce paired with Marketo or Pardot, use the native lead-scoring modules. The logic is not complex. the work is mapping each action to a point value and building the automated rules.

Step 5: Audit monthly.

Lead scoring models drift as your ICP shifts or your content mix changes. Each quarter, check: are the leads reaching MQL status converting at the expected rate? If not, adjust the thresholds or point values rather than the underlying sales process.

See account scoring and ICP scoring rubric for B2B SaaS for related calibration frameworks.

What a Good MQL-to-SQL Conversion Rate Looks Like

The average MQL-to-SQL conversion rate across B2B companies is 13%, based on Geckoboard benchmark data. The median time from MQL to SQL: 84 days.

The average masks significant variation by lead source:

Website leads convert at more than double the overall average. Outbound email converts at under 1%, which is why most outbound-focused teams treat email as a pipeline-volume play rather than a pipeline-quality play.

How to read your own numbers:

• Below 10%: Likely a criteria problem. Either marketing is setting the MQL bar too low (over-qualifying), or sales is rejecting leads at a high rate without clear reasons.
• 10–20%: Roughly average. Worth investigating whether your channel mix is dragging the rate down. if most leads come from outbound email, the baseline is lower.
• Above 30%: Check whether you are being too conservative with MQL criteria. A high conversion rate with low total MQL volume means leaving pipeline on the table.

Track the metric monthly, segment by channel, and treat it as a shared marketing and sales KPI, not a marketing-only one. If the rate shifts more than five percentage points in a month without a clear explanation, something in your scoring model or lead mix has changed.

Nurturing MQLs Until They're Ready for Sales

Most MQLs are not ready to talk to sales when they first cross the threshold. They fit your ICP and have shown some intent, but they are not actively evaluating solutions. Nurture sequences move them from "interested" to "in-market."

Three nurture tracks to run in parallel:

Educational track. For early-stage MQLs who engaged with top-of-funnel content. Sequence: 4–6 emails over six weeks, covering the problem you solve rather than your product. Objective: build familiarity, get them back to your site.

Intent-acceleration track. For MQLs who hit a mid-intent signal: visited pricing, downloaded a template, watched a demo video. Sequence: three emails over ten days, offering a full demo, a case study, or a direct conversation starter. Objective: get a reply or a booking.

Re-engagement track. For MQLs who have gone quiet, meaning no activity for 30 or more days. Sequence: two to three emails with a direct CTA ("Still researching this?"). Objective: either re-activate or move to cold.

Velocity matters as much as total score. A lead that opens three emails in five days is showing different intent than one who opened three emails across three months. Track time-between-actions alongside cumulative score to surface leads with accelerating engagement before they reach your threshold.

See sales signals and speed to lead for related frameworks on catching high-intent moments before competitors do.

The MQL-to-SQL Handoff: Making It Clean Every Time

The handoff is where MQL-to-SQL rates collapse. Marketing passes a "qualified" lead. Sales either never touches it, or follows up three weeks later. By then the lead has gone cold or chosen a competitor.

Three rules for a clean handoff:

1. Define a response SLA. When a lead reaches MQL status, sales has a defined window (24 hours is a common benchmark) to accept or reject it with a reason. No silent drops. If sales does not touch it in that window, an automated alert fires to the sales manager. This is a process decision, not a software decision. the tool just enforces the process.

2. Require structured rejection reasons. When sales rejects an MQL, they must pick from a defined list: wrong title, wrong company size, already a customer, no budget signal, just researching. These reasons are the most valuable data in your pipeline. They tell you which of your MQL criteria are calibrated wrong, and they give you a feedback mechanism that does not depend on anyone remembering to bring it up in a quarterly review.

3. Track speed to first touch. Research consistently shows that the faster a rep responds to a high-intent signal, the higher the conversion rate. Automate the first touch (a templated email sent from the assigned rep's address) while the human follows up within the same business day. This keeps response time fast without putting 24/7 pressure on individual reps.

Document all three as part of your lead qualification process, not just as informal rep habits.

Automate the MQL-to-SQL Workflow

Your CRM and marketing automation platform handle the MQL definition and scoring logic. But converting MQLs to SQLs involves more: the busywork of enriching contact records before routing, matching leads to the right rep, monitoring intent signals across tools, and keeping nurture enrollment current without manual ops overhead.

Miniloop handles that busywork. We build and run GTM automation workflows for your team:

• Contact enrichment on MQL trigger. when a lead hits MQL status, automatically pull firmographic data (company size, funding stage, tech stack) from data providers so the assigned rep has full context before their first touch
• Lead routing by territory and rep capacity. route SQLs to the right rep based on company size, vertical, or round-robin rules, without manual reassignment queues
• Intent signal monitoring. track when MQLs return to your site, open emails, or surface in buyer-intent data sources, and push those signals to the assigned rep in real time
• Sequence enrollment automation. automatically enroll MQLs into the right nurture track based on their scoring profile and channel source, removing manual enrollment from your marketing ops queue
• Rejection-reason analysis. aggregate SQL rejection data and surface patterns in a weekly digest so you catch criteria drift before the quarterly review

Try Miniloop or browse templates.

How to Continuously Improve Your MQL-to-SQL Rate

A 13% MQL-to-SQL rate is a starting point, not a ceiling. Teams that improve it consistently treat it like a product metric: hypothesize, test, measure, adjust.

Monthly: review rejection data. Every lead sales marked as "not SQL" is a signal. Cluster the reasons. If 40% of rejections say "wrong company size," your fit criteria are miscalibrated. Adjust the scoring model, not just the relationship.

Quarterly: recalibrate thresholds against closed-won data. Pull your most recent cohort of closed deals. What score did they have when first passed to sales? If your MQL threshold is 20 points but your best deals were scoring 35 or higher at first touch, you are underweighting high-intent signals.

Test one variable at a time. Do not adjust fit criteria, behavioral weights, and nurture sequence length simultaneously. You will not know what moved the number. Pick one: lower the MQL threshold by 20% for one quarter and see whether SQL conversion holds. If it does, the threshold was too high.

Run a weekly feedback loop between marketing and sales. A 20-minute sync or a Slack thread where reps can flag "good MQL / bad MQL" in real time is more useful than any quarterly dashboard. Make the data two-directional: marketing shares what is entering the pipeline, sales shares what they are seeing in conversations.

Track your MQL-to-SQL rate alongside B2B intent data signals to understand which channels and behaviors are driving the strongest conversion outcomes across your funnel.

Related Reading

• SEO Conversion Rate: What It Is, How to Calculate It, and How to Improve It
• Demand Generation for SaaS: A Practical Guide for 2026
• Landing Page Best Practices: What Actually Drives Conversions
• Google Ads for B2B SaaS: The Complete Setup and Optimization Guide for 2026

Related Resources

• Templates - workflow templates index
• Integrations - integrations index
• AI Automation Tools - Connect your apps and automate with AI
• AI Agent Platform - Build and deploy autonomous AI agents