Sales qualified lead (SQL): what it means
A sales qualified lead (SQL) is a prospect a salesperson has checked and judged worth actively pursuing: they fit your ideal customer, have a real need, can influence or make the decision, and have a plausible timeline. It is the point where a lead becomes a likely deal rather than a name.
Qualification frameworks
Most teams use a checklist so that "qualified" means the same thing to everyone.
| Framework | Checks | Best for |
|---|---|---|
| BANT | Budget, Authority, Need, Timeline | Simple, transactional sales |
| CHAMP | Challenges, Authority, Money, Prioritisation | Leading with the problem |
| MEDDIC | Metrics, Economic buyer, Decision criteria, Decision process, Identify pain, Champion | Large, multi-stakeholder deals |
For a founder or a small team, a short version is enough: do they have the problem, can they decide, and is there a reason to do it now?
A worked qualifying conversation
Say you sell a staff scheduling tool to restaurants. A restaurant group's operations manager replies to your cold email: "Interesting, we use spreadsheets for rotas across our three sites."
On a 15-minute call you learn:
- Need: managers spend several hours a week on rotas, and two sites ran short-staffed last month.
- Authority: she chooses the tool; the owner approves anything over a set monthly amount, and your price is under it.
- Timeline: she wants it running before the Christmas season.
- Budget: not discussed directly, but the approval limit covers it.
All four boxes are ticked. She becomes an SQL, and you create a deal in the CRM. If she had said "we might look at this next year", she would stay a nurtured lead.
How to measure SQL quality
Count SQLs, but judge them by what happens next.
- SQL to opportunity rate: of SQLs created, how many became deals with a value.
- SQL to won rate: the ultimate check on whether your definition means anything.
- Source breakdown: SQLs per source, and win rate per source.
Say outbound produced 40 SQLs last quarter and 6 closed (15%), while inbound produced 25 SQLs and 7 closed (28%). Inbound SQLs are worth nearly twice as much each, which should change where you spend time, or prompt a stricter outbound definition.
Common mistakes
- Qualifying on enthusiasm. A friendly reply is not a need.
- Skipping authority. A keen user who cannot buy leads to long, stalled deals.
- Letting quotas set the bar. If reps are measured on SQL count, the definition drifts looser.
- Never disqualifying. A clean "not a fit" frees time for real prospects.
Related terms
An SQL usually follows a marketing qualified lead; see MQL vs SQL. Upstream, lead scoring and buying signals decide who gets a first message at all.
Where Sluice fits
Sluice works before the SQL stage. It finds people, scores them against your profile and drafts first messages from what they said. The conversation that turns a reply into an SQL is yours. With HubSpot connected, leads arrive with a note explaining why they are a lead, which shortens that first call. See Sluice for small sales teams for how teams use it.
Questions people ask
- What makes a lead sales qualified?
- A confirmed problem you solve, a person who can decide or strongly influence the decision, and a reason to act within a reasonable time. Budget matters too, though it is often settled later in smaller deals.
- What is BANT?
- A qualification checklist: Budget, Authority, Need and Timeline. It is old but still useful as a reminder of the four things that most often stall deals.
- Who decides whether a lead is an SQL?
- Sales, usually the person who will work the deal or a development rep who qualifies leads for them. Marketing can suggest, but sales accepts.
Try it on your own market
Sluice quotes the worst-case price before anything runs and charges only for lookups that found something, so finding out costs close to nothing.
Get started