What makes a lead a sales qualified lead?

Sales has made contact and confirmed it is worth pursuing against a stated criterion. The distinguishing feature versus an MQL is that a human on the receiving side has assessed it.

What is the difference between MQL, SAL and SQL?

MQL is marketing's judgement. SAL is sales accepting the lead for work. SQL is sales confirming, after contact, that it merits pursuit. Not every organisation needs all three — each stage must correspond to a real decision or it is reporting overhead.

Why is our SQL count meaningless?

Two usual causes: acceptance with no possible rejection, so the step does no filtering; or a criterion that exists on paper but is not applied, so the label records that someone answered the phone.

Who should own the SQL definition?

Sales, because sales applies it — but agreed with marketing, because marketing is measured against it. A definition owned by the function it constrains rather than the one that applies it will not hold.

Sales Qualified Lead (SQL)

A lead that sales has examined and accepted as a genuine opportunity worth working. The point at which pipeline responsibility formally transfers.

What the label asserts

That a seller has made contact and judged the lead worth pursuing against a criterion agreed in advance. The judgement, and the possibility of it going the other way, is the entire value of the stage.

A stage with no rejection path is not a stage

If every lead passed becomes an SQL, the step filters nothing and the count is a restatement of the MQL count with a delay attached. The measure of a working stage is that a meaningful share does not pass it.

The two failure modes

Ceremonial acceptance. Rejection is technically possible but socially discouraged, or requires effort nobody has time for. The rate approaches 100% and the label stops carrying information.
Unapplied criteria. A written definition exists and sellers work from instinct. Detectable by asking three sellers to qualify the same five records independently.

Making it work

Require a reason code on rejection and route it back to marketing. Rejection without feedback improves nothing upstream.
Measure the acceptance rate deliberately and watch its trend. A rate climbing toward 100% is usually the stage decaying rather than lead quality improving.
Pair the count with downstream conversion from a later period, or the SQL count becomes trivially improvable by accepting more.
Audit periodically by re-qualifying a sample blind. Agreement between assessors is the health check for the definition.

Whether you need this stage at all

Each qualification stage costs handoff time and creates a place for records to sit. It earns its place only if a real decision happens there and a meaningful share of records are stopped by it. Where acceptance is near-universal, removing the stage loses no information and returns the time — the stage was recording that work happened, not that a judgement was made.

RELATED TERMS

Sales Accepted Lead (SAL)

A lead sales has acknowledged and agreed to work, sitting between marketing qualification and genuine pipeline.

Stage-to-Stage Conversion

The proportion of opportunities moving from each stage to the next. The most localised view of where pipeline dies.

Marketing Qualified Lead (MQL)

A lead that marketing considers ready for sales attention, according to a definition both teams have agreed. Without that agreement it is a marketing activity metric wearing a pipeline costume.

Lifecycle Stages

The shared sequence describing a contact's relationship with the company over time — subscriber through customer — used to align marketing, sales and customer success on where someone is.

COMMON QUESTIONS

What makes a lead a sales qualified lead?: Sales has made contact and confirmed it is worth pursuing against a stated criterion. The distinguishing feature versus an MQL is that a human on the receiving side has assessed it.
What is the difference between MQL, SAL and SQL?: MQL is marketing's judgement. SAL is sales accepting the lead for work. SQL is sales confirming, after contact, that it merits pursuit. Not every organisation needs all three — each stage must correspond to a real decision or it is reporting overhead.
Why is our SQL count meaningless?: Two usual causes: acceptance with no possible rejection, so the step does no filtering; or a criterion that exists on paper but is not applied, so the label records that someone answered the phone.
Who should own the SQL definition?: Sales, because sales applies it — but agreed with marketing, because marketing is measured against it. A definition owned by the function it constrains rather than the one that applies it will not hold.