SQL (Sales Qualified Lead)

What an SQL Is

A Sales Qualified Lead is a prospect that has cleared the human verification step — a rep or SDR has made contact, confirmed organizational fit, and judged the lead ready for an active sales opportunity. The line between an MQL and an SQL is the line between marketing's guess and sales' opinion. MQL status comes from behavioral scoring: content downloads, webinar attendance, email clicks. SQL status comes from a conversation. One is automated, one is a judgment call, and the two should never be treated as the same number on the same dashboard.

The transition happens at a defined handoff point. Sales receives the MQL, works it, and either accepts it as an SQL or rejects it back to marketing with a disqualification reason. That rejection loop — when it actually exists — is one of the most underused levers in demand generation. Most orgs have the acceptance path wired; almost none have the rejection feedback flowing back into campaign targeting.

How SQL Status Is Determined

There is no universal formula. SQL status is a binary gate, and every org defines its own criteria. Common requirements:

• Company matches the ICP on size, industry, geography, and tech stack
• A confirmed pain point or trigger event exists
• A real human at the right level of the org has been reached
• The prospect agrees to a defined next step — demo, discovery call, or proof of concept

Some orgs formalize this with BANT or MEDDIC criteria at the handoff stage, requiring reps to log answers before SQL status is grantable in the CRM. The more explicit the gate, the harder it is to inflate. That specificity is the point.

The key derived metric is MQL-to-SQL conversion rate: SQLs created ÷ MQLs worked. A healthy range for inbound SaaS sits between 40–60%, varying sharply with ICP breadth and lead source quality.

SQL Conversion Worked Example

A mid-market SaaS company runs 250 MQLs through the SDR team in Q1. SDRs contact 200 of them; 50 time out after six unanswered attempts. Of the 200 contacted, 90 are disqualified — wrong company size, existing competitor contract, or no confirmed pain. The remaining 110 are accepted as SQLs, a 44% MQL-to-SQL conversion rate.

Of those 110 SQLs, 60 advance to open opportunities. Of those 60 opportunities, 18 close. The SQL-to-close rate is 16.4% (18 ÷ 110). That downstream number is where lead quality actually shows up — not in SQL volume alone.

Who Tracks SQLs and Why

RevOps uses MQL-to-SQL conversion to hold marketing accountable for lead quality, not just lead quantity. A campaign generating 500 MQLs with a 12% SQL acceptance rate is a different animal than one generating 80 MQLs with a 70% acceptance rate, and the comp implications are opposite. VP of Sales watches SQL volume as a pipeline leading indicator — if SQL creation drops in week 3 of the quarter, the coverage problem surfaces before it becomes a missed number. Finance models SQL-conversion assumptions into pipeline-to-bookings forecasts. Recruiters cite SQL quotas in SDR job postings as a proxy for role scope.

How SQL Metrics Get Manipulated

Two opposing directions. The first: SDRs accept every MQL as an SQL to hit sourced-pipeline creation targets, regardless of fit. The resulting SQL has no real qualification behind it; it becomes a zombie opportunity that clogs the AE's forecast and dies quietly at first demo. High SQL acceptance paired with low SQL-to-close rate is the fingerprint of this pattern — and the pipeline coverage ratio downstream will confirm it.

The second direction is cherry-picking: SDRs only accept MQLs they are highly confident will close, protecting their SQL-to-close metric while rejecting borderline leads that marketing correctly scored. Both behaviors are incentive problems, not people problems. If the comp plan rewards SQL volume independently of SQL quality, expect inflation. If it rewards only closed bookings traced to SDR-sourced SQLs, expect extreme selectivity. The data tells you which disease you have; the comp plan tells you who prescribed it.