Sales Qualified Lead (SQL)

A sales qualified lead (SQL) is a lead that sales has worked and confirmed as a genuine opportunity worth pursuing, a prospect who has been vetted for fit, need, and intent, and judged ready for active selling. It is the stage where a lead becomes a real, working deal.

The SQL is the point in the funnel where marketing's and sales' earlier judgments are validated by direct engagement. A lead can look promising on paper, but only after sales has actually qualified it, through conversation and discovery, does it earn the SQL label and a place in the active pipeline.

What a sales qualified lead is

An SQL is a lead that sales has personally assessed and deemed a real opportunity: there is a genuine need, the prospect fits the profile, there is intent and a realistic path to a deal. Unlike earlier stages based on marketing engagement or initial acceptance, the SQL designation comes from sales' own qualification, usually after a discovery conversation, which makes it the strongest pre-opportunity signal in the funnel.

MQL → SAL → SQL

The progression tightens at each step. A marketing qualified lead is qualified on engagement and fit; a sales accepted lead is one sales agreed to work; and an SQL is one sales has worked and confirmed as a real opportunity, the last gate before it becomes a formal pipeline opportunity.

How a lead becomes an SQL

A lead reaches SQL status through sales qualification, typically a discovery conversation that tests fit, need, authority, and timeline.

The work happens in the discovery call and the broader qualification process: sales engages the accepted lead, uncovers whether there is a genuine opportunity, and either promotes it to SQL (and into the pipeline as an opportunity) or disqualifies it. The SQL bar should be defined clearly so the designation is consistent across reps.

Why the SQL matters

• Pipeline quality. SQLs are the vetted opportunities that populate a trustworthy pipeline.
• Forecasting. A pipeline built of true SQLs forecasts far more reliably than one of raw leads.
• Conversion focus. The SQL stage concentrates selling effort on leads judged genuinely worth it.
• Funnel measurement. MQL-to-SQL conversion is a key diagnostic of lead and qualification quality.

SQL and funnel conversion

The rate at which leads convert from MQL to SQL is one of the most revealing funnel metrics. A low MQL-to-SQL rate signals that marketing's leads are not as qualified as their MQL status suggested, or that sales' bar differs from marketing's, exactly the misalignment the SAL stage is meant to catch. Tracking this conversion, with agreed definitions, keeps marketing and sales honest about what a quality lead really is.

Writing an SQL definition that holds up

An SQL definition works when two reps looking at the same lead reach the same answer. That means turning judgment into a short checklist sales can confirm during discovery. A typical version has four parts.

Some teams add budget, others treat budget as something to establish later in the deal. Frameworks such as BANT and MEDDIC provide ready-made structures. Whatever the choice, the criteria should be written into the CRM as required fields at the SQL stage, so the designation is backed by recorded facts rather than a rep's impression.

A worked example

In a quarter, a company generates 1,000 MQLs. The illustrative funnel:

Reading across stages is more useful than any single rate. If the target were 60 new customers, the team would need 240 SQLs at a 25% win rate. Working backwards, at the current SAL to SQL rate of 30%, that means 800 SALs, and at 60% acceptance about 1,330 MQLs. Alternatively, better discovery that raises SAL to SQL conversion to 40% reaches the same number from 1,000 MQLs. Funnel math like this is how a revenue target turns into concrete demand generation and sales goals. Our lead generation statistics collect external conversion benchmarks for comparison.

SQL vs opportunity

Some companies use SQL and opportunity interchangeably; others keep them separate, with SQL meaning "qualified in discovery" and opportunity meaning "a deal with an amount and close date in the forecast." Either approach works if it is applied consistently. The mistake is having both labels with no clear difference, so reps use them differently and the funnel numbers stop meaning anything. Where both exist, the SQL criteria above decide entry, and the opportunity requires a value, a stage and a next step. The distinction between the two lead types is covered in MQL vs SQL, and the general mechanics of stage-by-stage drop-off in the conversion funnel overview.

Where AI fits in qualification

Qualification depends on information the buyer shares across emails, calls and forms, and much of it never makes it into the CRM. AI helps by capturing it: meeting notetakers record budget, timeline and decision makers from the call itself, and intent scoring reflects how the buyer is engaging. An autonomous CRM such as Outsales writes these facts to the contact record and rescores buy intent after each interaction, which gives a rep the evidence to decide on SQL status instead of relying on memory. See also AI lead qualification.

Common sales qualified lead mistakes

• Vague SQL criteria. Without a clear, shared bar, SQL status is inconsistent and the pipeline unreliable.
• Promoting too eagerly. Labeling weak leads as SQLs inflates the pipeline and distorts the forecast.
• Skipping real qualification. Treating an MQL as an SQL without genuine sales vetting defeats the stage.
• No feedback to marketing. Not tracking MQL-to-SQL conversion hides lead-quality problems.

A sales qualified lead is the prospect sales has personally confirmed as a real opportunity, the last and strongest qualification gate before the active pipeline. Defined with a clear, shared bar and tracked through MQL-to-SQL conversion, it is what keeps the pipeline genuine and the forecast trustworthy.