Sales Qualified Lead (SQL)
A Sales Qualified Lead (SQL) is a prospect that sales has vetted and accepted as worth actively pursuing.
Also known as: SQL
A Sales Qualified Lead (SQL) is a prospect that the sales team has reviewed and formally accepted as worth active pursuit. Unlike a lead that simply shows interest, an SQL has cleared a bar of qualification: sales believes there is a genuine opportunity to win business and is committing time to work it. In most B2B organizations, becoming an SQL is the point at which a contact moves from marketing's care into a live sales conversation.
The concept matters because it protects sellers' time and creates a shared definition of readiness between marketing and sales. When both teams agree on what makes a lead sales-qualified, marketing stops passing over contacts that go nowhere, and sales stops complaining about lead quality. A clear SQL definition is one of the most important alignment tools a revenue team can build.
How a lead becomes an SQL
A lead usually reaches SQL status through a two-step handoff. First it may become a Marketing Qualified Lead (MQL) based on behavior and fit, such as requesting a demo or matching an ideal customer profile. A salesperson or SDR then reviews the lead, often through research or a discovery conversation, and decides whether it meets the criteria to be actively pursued.
Qualification frameworks like BANT (Budget, Authority, Need, Timeline) or MEDDIC help sellers judge whether a lead is truly sales-ready. The defining feature of an SQL, however, is not the framework itself but the act of acceptance: a salesperson signs off that this is a real opportunity worth their time.
- Fit: the lead matches the target company profile and buyer role.
- Intent: there is an identified need or problem your product addresses.
- Feasibility: budget, authority, and timing suggest a deal is possible.
- Acceptance: a salesperson has agreed to work the lead.
Where SQLs come up day to day
SQLs appear constantly in pipeline reviews, CRM stages, and marketing-to-sales handoff conversations. When a team measures how many leads convert into opportunities, the SQL is often the gatekeeping stage that everything downstream depends on.
SDRs and AEs use the SQL label to decide where to focus. Marketing teams track their MQL-to-SQL conversion rate to judge lead quality, while sales leaders use SQL volume to forecast future pipeline. A rejected SQL, sent back to marketing for nurturing, is also a normal and healthy part of the process.
- CRM pipeline stages that separate raw leads from accepted opportunities.
- Service level agreements between marketing and sales on lead follow-up.
- Conversion reporting such as MQL-to-SQL and SQL-to-opportunity rates.
- Weekly pipeline reviews where SQLs are inspected or disqualified.
How SQL relates to neighbouring terms
An SQL sits in the middle of a common progression. A raw lead becomes a Marketing Qualified Lead when marketing signals it is ready, then a Sales Qualified Lead when sales accepts it, and finally an opportunity once active selling begins. Some teams use a Sales Accepted Lead (SAL) as an intermediate step that records sales' agreement to review a lead before full qualification.
The line between these terms varies by company, which is why the definitions must be written down. What one organization calls an SQL another might call an opportunity. The value is in the shared agreement, not in matching any universal standard.
- MQL: qualified by marketing based on fit and engagement.
- SAL: formally accepted by sales for review, a step before SQL in some models.
- SQL: vetted and accepted by sales as worth actively pursuing.
- Opportunity: an SQL that has entered the active deal pipeline.
Common mistakes with SQLs
The most frequent problem is having no agreed definition, so marketing and sales argue about lead quality while good leads slip through the cracks. Another is treating any MQL as an SQL without genuine review, which inflates pipeline numbers and wastes seller time.
Teams also err by making the SQL bar so high that almost nothing qualifies, or so low that everything does. The goal is a definition strict enough to protect focus but realistic enough to keep the pipeline flowing, with a feedback loop that returns unqualified leads for nurturing rather than discarding them.
- Skipping real review and auto-promoting every MQL to SQL.
- Never documenting the criteria, causing marketing-sales friction.
- Failing to send disqualified SQLs back for nurturing.
- Confusing SQL volume with actual opportunity or revenue.
Frequently asked questions
What is the difference between an MQL and an SQL?
An MQL is qualified by marketing based on fit and engagement signals, while an SQL is a lead that sales has reviewed and accepted as worth actively pursuing. The MQL shows potential; the SQL has sales' commitment behind it.
Who decides when a lead becomes an SQL?
Sales makes the final call. An SDR or AE reviews the lead, often through research or a discovery conversation, and either accepts it as sales-qualified or sends it back to marketing for further nurturing.
Does every SQL turn into a deal?
No. An SQL only means sales considers the lead worth pursuing; many will be disqualified as more is learned. Tracking SQL-to-opportunity and SQL-to-close rates shows how well your qualification bar is set.