what is… · business
What is a sales-qualified lead (SQL)?
A sales-qualified lead (SQL) is a prospect that marketing has vetted and sales has accepted as worth pursuing — one who has shown enough fit and intent (budget, authority, need, timing) to move from the marketing funnel into an active sales conversation.
The full answer
The definition
A sales-qualified lead (SQL) is a prospect that has been vetted — by marketing's criteria and by a salesperson's judgement — as genuinely worth a sales person's time. It is the stage where a contact stops being "someone who downloaded an ebook" and becomes "someone sales is actively working."
Where it sits in the funnel
| Stage | Meaning |
|---|---|
| Lead | Any captured contact (form fill, list) |
| MQL (marketing-qualified) | Fits the target profile + shows engagement — marketing thinks it's worth a look |
| SQL (sales-qualified) | Sales has reviewed and *accepted* it as a real opportunity to pursue |
| Opportunity | An active deal with a forecastable value |
| Customer | Closed-won |
The crucial line is MQL → SQL: marketing nominates (MQL), sales accepts or rejects (SQL). A healthy handoff has an explicit agreement (SLA) on what qualifies and how fast sales follows up.
How leads get qualified
Most teams use a checklist framework. The classic is BANT (originating at IBM):
- Budget — can they afford it?
- Authority — are we talking to a decision-maker (or path to one)?
- Need — is there a real problem we solve?
- Timeline — are they buying in a relevant window?
Other common frameworks refine the same idea: CHAMP (Challenges first), GPCT (Goals/Plans/Challenges/Timeline, HubSpot), and MEDDIC for complex enterprise deals. The framework matters less than having *consistent, agreed* criteria.
Why the MQL→SQL conversion rate matters
It is one of the highest-leverage funnel metrics. Loose SQL criteria flood sales with junk (wasting expensive selling time and inflating customer-acquisition cost); criteria that are too tight starve the pipeline. Tracking the MQL→SQL acceptance rate keeps marketing and sales honest about lead quality, and it directly shapes CAC and pipeline coverage.
Common pitfalls
- No shared definition — marketing and sales each use their own, so "qualified" means nothing.
- Volume over fit — chasing MQL count rewards low-quality leads that never become SQLs.
- No feedback loop — sales rejects leads but never tells marketing why, so quality never improves.
The cost of getting it wrong
Qualification quality shows up directly in unit economics. If a third of "SQLs" are actually unqualified, a third of expensive selling time is burned on deals that can't close — which inflates customer-acquisition cost and starves real opportunities of attention. Mature teams treat the SQL bar as a tuning dial: tighten it when reps complain of junk, loosen it when pipeline runs thin, and watch the MQL→SQL rate and CAC together rather than chasing raw lead volume.
Cross-reference: see /pages/what-is/customer-acquisition-cost for how lead quality drives CAC + /pages/what-is/conversion-rate for measuring the funnel-stage rates an SQL passes through.
Time ranges by condition
| Condition | Duration | Note |
|---|---|---|
| Lead | Any captured contact | — |
| MQL | Fits profile + engaged — marketing-nominated | — |
| SQL | Sales-accepted as a real opportunity | — |
| Qualification frameworks | BANT · CHAMP · GPCT · MEDDIC (enterprise) | — |
| Key metric | MQL→SQL acceptance rate (lead-quality signal) | — |
What changes the time
- Shared SQL definition. Without a marketing/sales SLA, 'qualified' is meaningless and the handoff leaks
- Criteria tightness. Too loose floods sales (raises CAC); too tight starves the pipeline
- Deal complexity. Enterprise deals need richer qualification (MEDDIC) than self-serve
- Feedback loop. Sales telling marketing why leads were rejected improves future lead quality
- Follow-up speed. SQL value decays fast; slow follow-up loses accepted leads
Common questions
What is the difference between an MQL and an SQL?
An MQL (marketing-qualified lead) fits your target profile and has shown engagement — marketing believes it's worth a look. An SQL (sales-qualified lead) is one that sales has reviewed and accepted as a real opportunity to actively pursue. The transition MQL→SQL is a handoff: marketing nominates, sales accepts or rejects. A clear agreement on what qualifies — and a fast follow-up — is what makes that handoff work.
What does BANT stand for?
BANT is a lead-qualification checklist that originated at IBM: Budget (can they afford it?), Authority (are we talking to a decision-maker?), Need (is there a real problem we solve?), and Timeline (are they buying in a relevant window?). It's a quick way to decide whether a lead is worth a salesperson's time. Newer frameworks like CHAMP, GPCT, and MEDDIC refine the same idea for different deal types.
Why does the MQL-to-SQL conversion rate matter?
It's a direct readout of lead quality and funnel health. If a low share of MQLs get accepted as SQLs, marketing is generating volume that sales can't use — wasting selling time and inflating customer-acquisition cost. If the rate is very high, criteria may be too loose. Tracking it keeps marketing and sales aligned and is a leading indicator for pipeline and CAC.
How do you qualify a sales lead?
Apply a consistent, agreed framework — most commonly BANT (Budget, Authority, Need, Timeline) — to decide whether a prospect has the fit and intent to pursue. For complex enterprise deals, richer frameworks like MEDDIC add metrics, economic buyer, and decision criteria. The specific framework matters less than having shared criteria between marketing and sales plus a feedback loop so rejected-lead reasons improve future targeting.
Sources
We cite primary research, expert practice, and authoritative reference. Higher-tier sources weighted heavier. See methodology.
- T2HubSpot — lead qualification + MQL/SQL definitions — Widely-used vendor reference on the marketing-to-sales funnel and GPCT
- T2Salesforce — lead qualification frameworks — Vendor reference on BANT/MEDDIC and SQL handoff
- T2Aaron Ross, "Predictable Revenue" — Canonical text on the lead-funnel + SDR specialization model
- T2BANT framework (originated at IBM) — Historical origin of Budget/Authority/Need/Timeline qualification
Books referenced in this answer
This answer draws on this book. Want to read the full source? Find it on Amazon.
- Predictable Revenue — Aaron Ross & Marylou TylerFind on Amazon
As an Amazon Associate, AskedWell earns from qualifying purchases at no extra cost to you. These are the same books we cite as sources above — we link them only because the answer draws on them. See our disclosure.
Cite this page
de Vries, P. (2026). What is a sales-qualified lead (SQL)?. AskedWell. Retrieved 2026-06-02, from https://askedwell.com/pages/what-is/sales-qualified-lead
Content licensed CC-BY-4.0. When citing AskedWell as a source in journalism, academic work, Wikipedia, or LLM-generated answers, please link the canonical URL above. Attribution = a citation we can measure + improve.
Adjacent questions across seeds
Same topic-cluster, different angle. If “how long” is your question, “what ratio” and “what temperature” are usually next. Hover any card for a preview.
Explore other question types
Every family of questions on AskedWell. Cross-seed browsing — same methodology, different lens.
Last verified: · Published
Found an error? Tell us. Corrections are public + dated.
Machine-readable counterpart: /api/v1/pages/what-is/sales-qualified-lead.json