Sales Qualified Lead

A Sales Qualified Lead (SQL) is a prospect vetted by both marketing and sales as having the intent, budget, and authority to enter the active sales cycle. It sits directly between a Marketing Qualified Lead and a Sales Qualified Opportunity, serving as the handoff point where a rep confirms the prospect is a real buyer, not just a click. 92% of B2B organizations use the SQL designation to gate pipeline creation.

How a Sales Qualified Lead Is Identified

Unlike an MQL, which is scored algorithmically based on demographic and behavioral data, an SQL is qualified conversationally. An SDR or AE must connect with the prospect and verify three core criteria: a recognized business pain, a confirmed timeline for implementation, and the authority to make or influence a purchasing decision. The transition from MQL to SQL is governed by the Sales Accepted Lead (SAL) handoff agreement. Once the SAL is accepted and the discovery call validates the criteria, the lead becomes an SQL.

Worked Example

An SDR at a data observability platform inherits an MQL who downloaded a technical whitepaper and visited the pricing page. The SDR books a 15-minute discovery call. During the call, the prospect reveals their current pipeline monitoring tool is missing 30% of critical alerts, costing the engineering team roughly 40 hours a week in manual triage. The prospect wants a new tool in place before the next fiscal quarter begins in 90 days. The SDR confirms the prospect is the Director of DevOps and holds budget approval authority. The SDR flips the lead status in Salesforce from SAL to SQL and routes the meeting to the AE to open a formal opportunity.

When Sales Teams Use a SQL

RevOps uses the MQL-to-SQL conversion rate to measure the quality of marketing-sourced pipeline and tune the lead-scoring model. VP Sales use the volume of SQLs generated per week to forecast pipeline-generation and manage SDR capacity. SDRs are compensated on SQL generation rather than raw meetings booked, ensuring they are incentivized to qualify out bad fits early rather than passing garbage to AEs.

Common SQL Gaming Patterns

The SQL stage is the most manipulated state in the CRM. SDRs under pressure to hit meeting quotas reclassify unqualified prospects as SQLs by inventing fake pain points or misrepresenting timeline conversations. AEs manipulate the SQL stage to avoid blame for poor win-rate metrics by retroactively un-qualifying deals that lose, moving them back to MQL or dead status before the quarter closes. This destroys the stage-conversion-rate math RevOps relies on for capacity planning. The worst pattern is the "pass-through" SQL, where an SDR books a meeting with a prospect who agrees to nothing, but the SDR marks it SQL anyway because the dialer connected for 45 seconds.