Content Marketing Glossary

  • What is Sales Qualified Lead (SQL)?

What is Sales Qualified Lead (SQL)?

Sales Qualified Lead (SQL)

Sales Qualified Lead (SQL) is a lead that has been evaluated by the sales team and deemed ready for direct sales engagement - a discovery call, a demo, a negotiation. An SQL sits one stage beyond an MQL (Marketing Qualified Lead) in the classical B2B funnel: MQLs meet marketing’s criteria for interest; SQLs meet sales’ criteria for opportunity. The handoff between the two is where many B2B revenue teams lose deals.

What makes a lead “sales qualified”

The criteria vary by team but typically cluster around four signals:

Explicit interest. The prospect has asked about pricing, requested a demo, responded affirmatively to a sales outreach, or otherwise signalled intent beyond passive consumption of content.

Fit. The prospect’s company matches the Ideal Customer Profile on firmographic dimensions - industry, company size, geography, tech stack. A misfit prospect who expressed interest is a distraction, not an opportunity.

Budget indication. The prospect has acknowledged budget exists, or is a role that typically controls budget. An individual contributor playing with the free tier is not the same as a VP evaluating a purchase.

Timing. The prospect’s stated or implied purchase timeline is within a range sales can act on - typically 90 days or less, varying by sales cycle.

Frameworks like BANT (Budget, Authority, Need, Timing), MEDDIC, and CHAMP formalise versions of these criteria for specific sales environments.

MQL versus SQL

The distinction matters because the two stages serve different functions:

An MQL is someone marketing has decided is worth sales’ attention. Criteria are marketing-owned: downloaded an asset, visited pricing twice, requested a newsletter, etc. MQL volume measures marketing’s top-of-funnel efficiency.

An SQL is someone sales has accepted as worth sales’ time. Criteria are sales-owned: confirmed fit, expressed intent, credible timeline. SQL volume measures marketing/sales handoff efficiency.

A lead can be MQL-qualified but SQL-rejected. That’s not a failure - it’s the handoff working correctly.

The handoff problem

MQL-to-SQL conversion rates are the single most common source of friction between marketing and sales organisations. Patterns:

Marketing throws everything over the wall. If MQL criteria are too loose, sales spends time disqualifying leads that should never have been handed over. Trust erodes. Sales ignores future MQLs.

Sales rejects everything. If SQL criteria are too strict, marketing’s MQL volume looks useless. Planning gets distorted - marketing over-invests in top-funnel because no amount is enough to break sales’ filter.

No service-level agreement. Without an explicit SLA (e.g. “sales contacts every MQL within 24 hours”, “sales provides feedback on every SQL rejection”), the handoff decays into blame-trading.

The fix is boringly administrative: a written definition of both stages, an explicit SLA on timing and feedback, and monthly calibration meetings where both teams review the handoff metrics together.

How SQL criteria evolve

The criteria shouldn’t be static. Three signals that criteria need updating:

SQL-to-close rate falling. If sales is closing a smaller percentage of SQLs over time, the SQL filter has loosened. Tighten.

Sales complaining about volume. If sales is drowning in SQLs that don’t advance, either marketing is flooding the pipeline or SQL criteria are insufficiently discriminating. Audit the filter, not the volume.

Reps going rogue. If reps are working deals outside the official SQL list, the official list doesn’t match the reality of what they’re willing to sell. Either the list is wrong or the reps are ignoring company strategy. Either way, surface and resolve.

A worked example

A B2B SaaS team measured 600 MQLs/month converting at 25% to SQL (150/month), then 20% of SQLs to closed-won (30 deals/month). A handoff audit found the SQL-rejection reasons clustered into three buckets: 40% rejected for “wrong company size”, 30% for “no budget this fiscal year”, 20% for “individual user, not buying centre”. Marketing adjusted MQL criteria to filter on company size earlier (dropping MQL volume to 420 but improving MQL-to-SQL conversion to 38%), added a budget qualifying question at lead capture, and routed non-buying-centre leads to a product-led nurture track instead of sales. Post-change: 160 SQLs/month (comparable volume), closed-won rose to 28% (45 deals/month). Net: 50% more closed deals at the same lead-generation spend. The lever was handoff quality, not top-of-funnel volume.

We built Penfriend to produce the content that moves MQLs toward SQL status - detailed comparison content, customer stories, technical deep-dives. SQL conversion improvements usually come from better mid-funnel content, which is where Penfriend’s production economics matter most.

Related terms