1. PostKit
  2. /Glossary
  3. /SQL (Sales Qualified Lead)
Glossary

SQL (Sales Qualified Lead)

A Sales Qualified Lead (SQL) is an MQL that sales has personally vetted and accepted as a real prospect worth working — meeting fit, need, and timing thresholds for active deal pursuit. The transition from MQL to SQL is the most consequential funnel step in B2B.

Updated
—
Words
918
Category
Sales / Outreach

SQL (Sales Qualified Lead)

An SQL (Sales Qualified Lead) is a lead that a sales rep has personally engaged with and accepted as worth pursuing for an active deal — typically after a discovery call or qualifying conversation. SQL is the sales-side counterpart to MQL: where MQL is qualified by marketing's automated criteria, SQL is qualified by a human sales rep's judgment.

The MQL → SQL transition is the most consequential — and most contested — handoff in B2B funnels. It's where marketing's lead generation work either gets validated as real pipeline or gets rejected as junk. The MQL → SQL conversion rate is often the single most-debated metric in revenue-team meetings.

How an SQL is qualified

A sales rep designates a lead as SQL when the lead meets criteria set by their qualification framework. Most common:

  • BANT — Budget, Authority, Need, Timing all confirmed.
  • MEDDIC — Metrics, Economic Buyer, Decision Criteria, Decision Process, Identify Pain, Champion present.
  • CHAMP — Challenges, Authority, Money, Prioritization established.

In practice, SQL designation usually requires:

  • A real conversation with the prospect (not just an email reply).
  • Confirmed pain or use case.
  • Identified decision-maker (or at least champion).
  • Some indication of timeline (even rough).
  • Reasonable budget range or budget-discovery process possible.

The bar varies by ACV: a $500/month SaaS deal might require only "interested + decision-maker reached" while a $200k enterprise deal might require all MEDDIC criteria documented.

MQL → SQL benchmarks (2026)

2026 funnel benchmarks (HubSpot, Bridge Group, Salesforce):

  • MQL → SQL conversion — 13–20% healthy range
  • Below 10% — Marketing is passing too many low-quality leads
  • Above 30% — Marketing is sitting on leads sales would work
  • SQL → Opportunity — 35–50%
  • Opportunity → Closed-won — 20–30%

Combined: roughly 1–4% of MQLs end up as closed-won customers.

The MQL → SQL conversion rate is highly diagnostic of marketing-sales alignment. Sustained low conversion indicates either bad MQL criteria or weak first-touch sales process. Sustained high conversion indicates either marketing is under-qualifying or sales is over-accepting.

What kills MQL → SQL conversion

Common pathologies:

  • Slow response time — Each minute of delay between MQL trigger and sales contact halves conversion. <5 minute contact wins.
  • Wrong sales rep assigned — Generic AE round-robin underperforms persona-matched assignment by 30%.
  • Generic outreach — Treating MQLs as cold prospects ignores the engagement context.
  • No SLA on handoff — Without enforced response-time SLAs, MQLs go cold.
  • Misaligned ICP between marketing and sales — Marketing optimizes for volume; sales optimizes for ACV; SQL conversion suffers.
  • No feedback loop — Sales doesn't share why leads were rejected; marketing doesn't refine criteria.

Best-in-class teams instrument MQL → SQL conversion at granular level (per source, per persona, per campaign) and continuously calibrate.

Examples of SQL discipline

  1. Salesforce's State Selling methodology — Rigorous SQL acceptance criteria; rejected MQLs get returned to marketing with reason codes.
  2. HubSpot's SLA model — Defined response-time SLAs (5 min for high-score leads); auto-escalation if missed.
  3. Drift's "no SQL without conversation" rule — Leads can't reach SQL without verified live conversation; drives quality.
  4. Gong's SQL conversation analysis — Records every SQL-establishing call to identify patterns of acceptance vs rejection.
  5. PostKit's PQL-style SQL — Product-usage signals replace traditional discovery for self-serve tier; higher conversion.

How PostKit thinks about SQL

PostKit's Product-Led Growth model collapses the traditional MQL → SQL transition. The product itself qualifies users behaviorally:

  • Free-tier user → engaged free-tier user (analogous to MQL): generated multiple batches, set up multiple lines.
  • Engaged free-tier user → paying customer (analogous to SQL converting to opportunity): upgraded to Starter, Pro, or Agency tier.

For the small subset of high-ACV opportunities (Agency tier white-label, custom integrations), PostKit runs a more traditional discovery → SQL → opportunity flow. Founder Tadeáš Raška handles these personally, applying lighter MEDDIC discipline — confirming use case, evaluating fit, qualifying timing.

The PLG approach radically improves PostKit's effective SQL conversion: the typical PLG SQL rate (where SQL = "actively converting from free to paid") runs 20%+, vs traditional B2B SaaS at 3–6%. The reason: the product has done more qualification work than any sales conversation could.

Frequently asked questions

What's the difference between SQL and Opportunity? SQL = sales has accepted the lead as worth working. Opportunity = an active deal in progress with confirmed budget/timing. SQL → Opportunity conversion: 35–50%.

Who decides if a lead is an SQL? Sales — specifically, the SDR or AE who first engaged the lead. Marketing proposes via MQL status; sales accepts or rejects.

Can a lead skip MQL and go straight to SQL? Yes — high-intent inbound (demo request from ICP-fit company) often skips MQL and is immediately accepted as SQL. The MQL stage exists for nurtured leads requiring marketing validation first.

What's a healthy SQL → Opportunity conversion? 35–50%. Below 35%: SQL bar is too loose. Above 60%: SQL bar may be too tight (over-screening leads).

How do I improve MQL → SQL conversion? Faster response time, better persona matching on rep assignment, deeper MQL criteria (intent + engagement + fit), continuous feedback loop with marketing on rejected leads.

Is SQL the same as "discovery-completed"? Closely related. SQL designation typically requires a discovery call or equivalent qualifying conversation. Some teams use "SQL" and "discovery-completed" interchangeably.

What happens to rejected MQLs? Returned to marketing nurture with reason codes (wrong company size, no budget, bad timing). Re-qualified later as criteria change.

Related terms

  • MQL (Marketing Qualified Lead)
  • Lead qualification
  • Prospecting
  • Cold email
  • Warm email
  • Sales sequence
  • Demo (sales)
  • Discovery call
  • Pipeline (sales)
  • Conversion rate

Sources

  • HubSpot — State of Sales 2026
  • The Bridge Group — SDR Metrics Report 2026
  • Salesforce — State of Sales Report 2026
  • InsideSales — Lead Response Time Study 2025

Related comparisons

  • PostKit vs Anyword: 2026 Comparison & Best Choice for Performance Marketers
    PostKit vs Anyword compared: end-to-end social and ad generator vs predictive copywriting platform. See pricing, features, real reviews.
  • PostKit vs Brandwatch: 2026 Comparison & Best Choice for Different Buyers
    PostKit vs Brandwatch compared: solopreneur AI content generator vs enterprise consumer intelligence platform. See pricing, features, real reviews.
  • PostKit vs Buffer: 2026 Comparison & Best Choice for Solo Creators
    PostKit vs Buffer compared: native AI image + caption generation in your browser vs per-channel scheduling. See pricing, features, real reviews.
  • PostKit vs Canva: 2026 Comparison & Best Choice for Social Content
    PostKit vs Canva compared: AI-native end-to-end generator vs design-first manual workflow with scheduling. See pricing, features, real reviews.
  • PostKit vs ContentStudio: 2026 Comparison & Best Choice for Multi-Platform Creators
    PostKit vs ContentStudio compared: focused browser AI generator vs broad SMM suite with content discovery. See pricing, features, real reviews.
  • PostKit vs Copy.ai: 2026 Comparison & Best Choice for Social Content
    PostKit vs Copy.ai compared: end-to-end social and ad generator vs GTM AI workflows for sales and marketing copy. See pricing, features, real reviews.
  • PostKit vs CoSchedule: 2026 Comparison & Best Choice for Content Calendar Workflows
    PostKit vs CoSchedule compared: web AI generator vs marketing project management calendar. See pricing, features, real reviews.
  • PostKit vs Crowdfire: 2026 Comparison & Best Choice for Modern Creators
    PostKit vs Crowdfire compared: AI-native end-to-end content generator vs legacy Twitter follow/unfollow tool with light scheduling. See pricing, features, real reviews.
  • PostKit vs FeedHive: 2026 Comparison & Best Choice for Indie Creators
    PostKit vs FeedHive compared: web AI content generator vs web-based scheduler with AI writing + recycling. See pricing, features, real reviews.
  • PostKit vs Flick: 2026 Comparison & Best Choice for Instagram Creators
    PostKit vs Flick compared: web AI carousel generator vs Instagram-first hashtag tool with light AI. See pricing, features, real reviews.
  • PostKit vs Hootsuite: 2026 Comparison & Best Choice for Solopreneurs
    PostKit vs Hootsuite compared: native AI generation in your browser for $19-79 vs enterprise-grade dashboards from $99/mo. See pricing, real reviews.
  • PostKit vs Hypefury: 2026 Comparison & Best Choice for Multi-Platform Creators
    PostKit vs Hypefury compared: 5-platform AI content generator vs X/Twitter-first automation and recycling. See pricing, features, real reviews.