MQL-to-SQL conversion is the process by which a lead that has been qualified by marketing (MQL) transitions to a lead that is accepted and pursued by sales (SQL). The MQL represents marketing's assessment that the lead has sufficient characteristics and intent to be worth a sales conversation; the SQL represents sales's assessment that the lead is genuinely ready for a sales process. The gap between MQL and SQL -- leads that marketing sends to sales and sales rejects or does not contact -- is one of the most common sources of marketing-sales misalignment in B2B.
How to define MQL and SQL criteria
- Define the MQL based on observable signals, not assumptions: an MQL should be defined by a specific combination of firmographic criteria (company size, industry, geography) and behavioural criteria (content downloaded, pages visited, events attended, form submitted) that marketing has observed are correlated with conversion to SQL and ultimately to revenue. Avoid defining MQLs based on criteria that cannot be observed (e.g., "has budget") or that are too easy to meet (e.g., "opened one email").
- Define the SQL based on confirmed qualification, not assumed qualification: an SQL should be a lead where a sales rep has made direct contact, confirmed that the prospect has a relevant problem, has an approximate budget, and is interested in having a sales conversation. The SQL definition should specify what the rep must confirm (via a discovery call or an initial qualification exchange) before the lead advances from MQL to SQL. An SQL that is defined as "a MQL that was assigned to a rep and not rejected" is not a meaningful qualification -- it is just a MQL that was not returned.
- Agree on MQL-to-SQL criteria in a joint marketing-sales SLA: the MQL and SQL definitions should be documented in a formal service level agreement signed off by the heads of marketing and sales. The SLA should specify: what criteria constitute an MQL, the timeline within which sales must respond to an MQL (typically 24-48 hours), the criteria sales must evaluate to accept or reject a MQL, and the process for returning a rejected MQL to marketing with a rejection reason.
- Review and recalibrate the definitions quarterly: MQL and SQL definitions decay as the ICP evolves, the product changes, and the market shifts. A quarterly review of MQL-to-SQL conversion rates, acceptance rates, and SQL-to-close rates allows marketing and sales to identify whether the current definitions are producing leads that convert, and to update the criteria accordingly.
Common causes of low MQL-to-SQL conversion
- Misaligned MQL and SQL definitions: the most common root cause. Marketing defines an MQL as "a lead who downloaded a whitepaper and is in the target company size range"; sales defines a SQL as "a lead who has confirmed budget and is actively evaluating solutions." The gap between these two definitions means most MQLs will not meet the SQL bar, producing a high rejection rate and an ongoing marketing-sales conflict about lead quality.
- Slow sales follow-up: research consistently shows that MQL-to-SQL conversion rates drop dramatically with follow-up delay. Leads followed up within 5 minutes of the initial action convert at 3-5x the rate of leads followed up 24 hours later. Many B2B teams are operating with average lead response times of 24-72 hours -- a significant conversion opportunity being left on the table.
- MQL volume pressure creating quality dilution: when marketing is measured on MQL volume (leads generated per month), the incentive is to lower the MQL qualification bar to generate more leads. The result is high MQL volume with low conversion to SQL -- exactly the dynamic that creates sales team frustration about lead quality. Measuring marketing on SQL volume (or on pipeline contribution from marketing-sourced leads) aligns marketing incentives with actual revenue impact rather than top-of-funnel vanity metrics.
- Insufficient lead context at handoff: sales reps who receive an MQL notification with only the prospect's name, email, and company name have no context for a relevant follow-up call. Including the specific action the prospect took (what they downloaded, which pages they visited, what form they filled out), any firmographic data (company size, role, industry), and any prior interaction history in the lead notification dramatically improves the quality of the initial sales outreach and the MQL-to-SQL conversion rate.
Frequently asked questions
- What is a good MQL to SQL conversion rate in B2B?
- MQL-to-SQL conversion rate benchmarks for B2B: Industry averages (from Salesforce and HubSpot benchmark data): average MQL-to-SQL conversion across B2B industries is approximately 13-20%. B2B SaaS: 13-25% MQL-to-SQL conversion is typical for well-run SaaS teams. Companies with strong ICP targeting, fast lead response times, and clear MQL definitions are at the upper end of this range; companies with loose MQL definitions and slow follow-up are at the lower end. Enterprise B2B: lower MQL-to-SQL conversion rates (often 10-15%) are typical in enterprise sales because the qualification bar for a genuine SQL is higher -- enterprise SQLs require confirmed budget, confirmed decision-maker access, and a confirmed fit with a complex product. Context matters for benchmarking: these percentages are only meaningful if the MQL and SQL definitions are consistent. A team that defines an MQL as "visited any page on the website" and an SQL as "had a discovery call" will have a very low conversion rate (most website visitors are not ready for a sales conversation); a team that defines an MQL as "attended a demo webinar and is in the ICP company size range" will have a much higher conversion rate because the bar for MQL is already higher. The most useful benchmark is not the industry average but your own historical conversion rate -- focus on the trend (is it improving quarter over quarter?) rather than the absolute number.
- Who is responsible for MQL to SQL conversion?
- MQL-to-SQL conversion is a shared responsibility between marketing and sales, but the responsibilities are distinct: Marketing is responsible for: (1) Generating MQLs that meet the agreed-upon definition (the right company type, with observable intent signals, with sufficient engagement to warrant a sales conversation). (2) Providing complete, useful context at the handoff (what the prospect did, who they are, what they are likely interested in). (3) Nurturing MQLs that are not yet ready for sales (returning unready leads to a nurture track rather than pushing all MQLs to sales). Sales is responsible for: (1) Responding to MQLs within the agreed SLA (typically within 24-48 hours of the MQL notification). (2) Making a genuine qualification attempt before accepting or rejecting the MQL. (3) Providing clear, specific rejection reasons when an MQL is returned to marketing (not just "bad timing" but "company is too small at 20 employees" or "prospect already bought a competitor 2 months ago"). The joint responsibility: both teams are responsible for maintaining the MQL and SQL definitions and reviewing them regularly to ensure they reflect real buying behaviour. A quarterly MQL-to-SQL conversion review -- attended by both the marketing and sales leadership -- should examine conversion rates, acceptance rates, rejection reasons, and the revenue generated from marketing-sourced leads to identify where the handoff is working and where it is broken.
- How do you improve MQL to SQL conversion in B2B?
- The most effective interventions for improving MQL-to-SQL conversion in B2B: (1) Align on definitions: hold a joint marketing-sales session to agree on specific, measurable MQL and SQL criteria. Document the agreed definitions in an SLA and review them quarterly. This single intervention has the largest impact on conversion because it eliminates the primary cause of most MQL-to-SQL friction. (2) Reduce lead response time: implement a lead assignment and response workflow that ensures every MQL is assigned to a specific rep within 1 hour and followed up within 24 hours. Use automation (CRM routing rules, Slack notifications, email alerts) to eliminate the manual steps that delay response. (3) Improve lead context at handoff: ensure that every MQL passed to sales includes: the specific action the prospect took, firmographic data (company size, role, industry, technology stack), any prior engagement history (prior downloads, prior conversations, prior demo requests), and a recommended approach for the initial outreach. (4) Measure and reward lead quality, not lead volume: shift the primary marketing metric from MQL volume to SQL conversion rate (or to pipeline generated from marketing sources). This aligns marketing incentives with producing leads that sales actually wants, rather than with generating volume that inflates funnel metrics without improving revenue outcomes. (5) Implement a faster routing model for high-intent MQLs: leads who take the highest-intent actions (request a demo, visit the pricing page multiple times, start a free trial) should bypass the standard MQL-to-SQL process and be routed immediately to an AE or senior SDR for same-day follow-up.
Keep reading
- B2B marketing qualified lead: what MQL means and how to define one
- B2B sales qualified lead: what SQL means and how to define one for your pipeline
- B2B lead response time: how fast should you follow up on B2B leads?
- Lead scoring: how to score B2B leads and prioritise the right ones
- B2B inbound lead routing: how to route inbound leads to the right sales rep