Growth Marketing Glossary

Sales-Qualified Lead (SQL)

sales-qual-i-fied leadnoun

The handoff sales actually accepts. A sales-qualified lead (SQL) is a prospect a rep has vetted as worth pursuing — not just interested, but ready to be sold.

marketing-qualified leadsales accepts itsales-qualified lead
Schematic — a vetted lead crossing into the sales pipeline
Term
Sales-qualified lead (SQL)
Is
A prospect sales accepts as sell-ready
Sits after
The marketing-qualified (MQL) stage
Note
Unrelated to SQL the database language

Parts of speech & senses

sales-qualified lead · noun
  1. A sales-qualified lead (SQL) is a prospect that the sales team has examined and accepted as ready for direct selling, having met the bar for fit, need, and timing. "Only a third of MQLs became sales-qualified leads."

What a sales-qualified lead is

A sales-qualified lead (SQL) is a prospect that a salesperson has personally reviewed and judged ready to be sold to — someone with a real need, the budget and authority to act, and a reasonable timeframe for buying. The word "qualified" is doing the heavy lifting. A name in your database is just a contact; a contact who shows interest is a lead; a lead that marketing scores as promising is a marketing-qualified lead; and only when a rep accepts that lead as worth their hours does it become sales-qualified. That last acceptance is a deliberate human decision, not an automatic score. One small but real source of confusion deserves a flag here: the same three letters, SQL, name a database query language pronounced "sequel." The two have nothing to do with each other beyond an unlucky acronym collision.

The point of the SQL stage is to protect a rep's most limited resource, which is time spent in live conversation. Sales teams cannot chase every curious visitor, so the SQL label draws a line: below it, marketing nurtures; above it, sales sells. A lead earns the label by clearing an agreed bar — often framed as fit (does this prospect look like a customer you can serve), need (is there a problem worth solving), and readiness (is the timing right). Because the bar is a shared agreement between marketing and sales, the SQL count becomes a number both teams trust. When the definition is loose, reps waste effort on prospects who were never going to buy, and they stop trusting the leads marketing sends at all.

SQL versus MQL versus PQL

The three sit in sequence, and mixing them up causes most of the friction between marketing and sales. A marketing-qualified lead (MQL) is one marketing believes is promising based on behavior and fit — downloads, page visits, a scoring threshold. A sales-qualified lead (SQL) is one sales has reviewed and accepted as worth direct pursuit. The difference is who decides and how. An MQL is graded by marketing's model; an SQL is accepted by a human rep. Many MQLs never become SQLs, and that drop-off rate is itself a useful signal: if it is very high, either the scoring is too generous or the handoff is broken. The cleanest organizations write the SQL bar down so both sides judge by the same rule.

A product-qualified lead (PQL) is a third path, and it changes the qualifying evidence entirely. A PQL has used the product itself — through a free trial or freemium tier — and shown buying intent through real usage, like hitting a usage limit or inviting teammates. An MQL is qualified by marketing signals, an SQL by a rep's judgment, and a PQL by product behavior. In a product-led business the PQL often feeds the SQL stage: usage data tells the rep which trial users are worth a call. So these are not competing definitions but different lenses on readiness — marketing intent, sales acceptance, and product engagement — that a well-run funnel uses together rather than treating as interchangeable.

Using the SQL stage well

Using the sales-qualified lead stage well starts with a written, agreed definition. Marketing and sales should sit down and name the exact criteria a lead must meet — the fit, the need, the timing, the data the rep needs to see — and then both teams hold to it. With that in place, the MQL-to-SQL conversion rate becomes a diagnostic: a low rate points to weak scoring or a sloppy handoff, a high rate to a healthy pipeline. Track how SQLs convert to opportunities and won deals, because the whole funnel is judged on what actually closes, not on volume at the top. A service-level agreement on follow-up speed keeps accepted leads from going cold while a rep is busy.

The discipline is treating qualification as a shared contract rather than a label one team applies and the other resents. When sales rejects leads marketing called qualified, the answer is not to argue but to revise the bar together until the accepted leads convert. Keep the criteria current as the market shifts, and feed closed-deal data back so the scoring model learns which signals actually predict sales. Done this way, the SQL stage stops being a source of inter-team blame and becomes the clean joint at which marketing's nurturing hands off to sales' selling — each side trusting the count because both wrote the rule that produced it.

Worked example. A B2B software firm passes 500 marketing-qualified leads to sales in a quarter, but reps complain most are not ready to buy. Marketing and sales sit down and agree a sales-qualified-lead bar — a named buying problem, a budget owner identified, and activity within thirty days. Reps now accept only the leads that clear it, and the SQL count drops to 180. But those 180 close at three times the old rate, and the friction between the teams largely disappears because both judged by the same written rule. The lesson: a sales-qualified lead is one a rep has accepted as sell-ready, and a shared definition makes the count trustworthy and the handoff clean. (Illustrative; RGM analysis.)
Failure modes to watch. Letting marketing and sales hold different unwritten definitions of "qualified" so reps reject the leads marketing sends; counting SQL volume instead of how SQLs convert to deals; failing to set a follow-up time so accepted leads go cold; and confusing the lead-stage SQL with SQL the database query language.

Synonyms & antonyms

Synonyms

accepted leadsales-ready leadsales-accepted lead

Antonyms

marketing-qualified leadunqualified lead

Origin & history

Sales-qualified lead (SQL) — a prospect sales has accepted as ready for direct selling — sits one stage past the marketing-qualified lead and shares its acronym, by coincidence, with the database query language.

Etymology: source.

Usage trends

Search interest for this term over the last five years:

View interest-over-time on Google Trends →

Common questions

What is a sales-qualified lead (SQL)?
A prospect that a salesperson has personally reviewed and accepted as ready for direct selling — with a real need, the authority and budget to buy, and a reasonable timeframe. It sits one stage past the marketing-qualified lead.
How is an SQL different from an MQL?
A marketing-qualified lead is graded promising by marketing's scoring model. A sales-qualified lead has been accepted by an actual rep as worth pursuing. The difference is who decides and on what evidence — a model versus a human.
Is this SQL the same as the SQL database language?
No. The marketing term and the database query language only share an acronym. A sales-qualified lead is a stage in the funnel; SQL the language is a way to query databases, pronounced "sequel." The collision is purely coincidental.

Resources & people to follow

Curated, non-competitor resources verified per term.

Related training

Disciplines

Areas of marketing where sales-qualified lead (sql) is a core concern:

Sources

  1. trendsGoogle Trends — "sales qualified lead"