How to Define a Sales Qualified Lead (SQL)
How to Define a Sales Qualified Lead Your Reps Will Actually Call
Your sales team keeps saying the leads are bad. Marketing keeps showing a chart that says lead volume is up 40%. Both are telling the truth, and the gap between them usually comes down to one missing sentence: a written definition of what counts as a sales qualified lead.
When that sentence does not exist, every rep invents their own version. One closes anything with a pulse. Another ignores half the pipeline because "those never buy." You lose deals to slow follow-up on the good ones and waste hours dialing the dead ones.
This guide gives you a definition you can ship this week. We will cover what separates an SQL from an MQL, the criteria worth scoring (and the ones that just feel important), a rubric you can copy, and the handoff that keeps sales and marketing from blaming each other. Example numbers are illustrative, so swap in your own.
What a sales qualified lead actually is
A sales qualified lead is a contact your sales team has agreed is worth a direct sales conversation, right now. Two parts of that matter. Sales has to agree, and the timing has to be now.
A marketing qualified lead (MQL) downloaded your pricing guide, opened three emails, and matches your target industry. That is interest. An SQL is the subset where interest plus fit plus timing line up enough that a rep working the account is a good use of a paid salesperson's hour. The promotion from one to the other is a decision, and someone has to own the criteria behind it. If you are still untangling the two stages, our breakdown of MQL versus SQL walks through where the line sits.
Here is the practical test. Read the lead record out loud to a rep and ask: "Would you call this person in the next hour?" If the honest answer is "I'd need to know X first," then X belongs in your SQL definition.
Fit, interest, and timing: the three things to score
Most teams overcomplicate qualification by listing twenty fields. You need three buckets. Score each one, and a lead becomes an SQL when all three clear a bar you set.
Fit. Does this account look like a customer who stays and pays? Company size, industry, geography, the job title of the contact, the tech they already run. Fit is mostly knowable before anyone talks to the lead, which is why it belongs in marketing's qualification too. If your best customers are 50-to-500-person logistics firms, a 4-person startup scores low on fit no matter how engaged it is. Build this from your ideal customer profile; if you have not written one down, define that before you tune anything else.
Interest. What has this person actually done? Requested a demo, replied to an email asking about pricing, attended a webinar and stayed for the Q&A, visited your pricing page three times. Interest is behavioral evidence, and it carries more weight than a form fill. A demo request from a mid-fit account often beats an ebook download from a perfect-fit one.
Timing and authority. Is there a reason to buy soon, and is this person able to push it forward? A contract renewal, a new mandate, a budget that resets next quarter. The classic BANT shorthand (budget, authority, need, timeline) lives mostly here. You rarely confirm all of it before the first call, so treat timing signals as a tiebreaker, not a gate.
Score those three, weight them by what predicts revenue in your data, and you have a defensible definition instead of a gut feeling. The full mechanics of turning this into points live in our guide to lead scoring.
A simple scoring rubric you can copy
You do not need a data science team to start. A weighted table on a whiteboard works for the first version. Here is one shape that teams use, with illustrative point values.
| Signal | Bucket | Points (illustrative) |
|---|---|---|
| Company size in ICP range | Fit | +20 |
| Target industry | Fit | +15 |
| Decision-maker or influencer title | Fit | +15 |
| Requested a demo or quote | Interest | +30 |
| Visited pricing page 2+ times | Interest | +15 |
| Opened or clicked 3+ emails | Interest | +10 |
| Mentioned a deadline or active project | Timing | +20 |
| Free email (gmail, outlook) | Fit | -15 |
| Job seeker, student, competitor | Fit | disqualify |
Set the SQL threshold at, say, 60 points, with one rule: a lead cannot hit SQL on interest alone. A perfect engagement score from a company that fails fit is still a no. That single guardrail kills most of the "these leads are garbage" complaints.
Two cautions. First, negative points matter as much as positive ones. A free email address or a competitor signing up for your demo should pull the score down hard. Second, recency decays. Someone who downloaded a guide eight months ago and went quiet is not as warm as the points suggest, so build in a decay rule or a freshness window.
The MQL-to-SQL handoff is where deals leak
A clean definition fails if the handoff is sloppy. The two failure modes are familiar. Marketing dumps leads into a shared queue and assumes sales will sort them. Sales cherry-picks the obvious wins and lets the rest rot. Both happen when nobody owns the moment a lead crosses the line.
Fix it with a service level agreement, even an informal one. Spell out three things: what marketing guarantees about an SQL (it meets the agreed criteria and includes the fields sales needs), how fast sales must act, and what happens to leads sales rejects. That last part is the one teams skip, and it is the most valuable.
SQL handoff SLA (template)
Marketing delivers an SQL with:
- Verified company + contact fields
- Score >= 60, fit bucket >= 30
- Source and last activity timestamp
Sales commits to:
- First touch within [4 business hours]
- Disposition logged within [1 business day]
- One of: Accepted / Recycle (not ready) / Reject (bad fit)
Rejected leads route back to marketing with a reason code.
Reason codes feed the next scoring review.
Speed is not a soft target here. The odds of reaching a lead drop sharply after the first hour, and a fast first touch is one of the cheapest conversion levers you have. We pulled the data and tactics together in a piece on lead response time. The reject loop is the other half: when a rep marks a lead "wrong title" or "no budget," that reason should change your scoring model next month. Without the loop, the same bad leads keep arriving and trust keeps eroding. This is the heart of aligning sales and marketing, and it is mostly a process problem, not a personality one.
Common mistakes that quietly inflate your SQL count
Counting form fills as SQLs. A whitepaper download is interest with no fit check and no timing. Calling it sales-ready trains your reps to ignore the label entirely.
Scoring only positive signals. If your model can only add points, every active lead eventually crosses the threshold, including the students and the competitors. Negative scoring keeps the bar honest.
One definition for wildly different products. A $500/month self-serve tool and a $200k enterprise contract need different bars. If you sell both, you need two SQL definitions, not an average.
Never revisiting the model. The definition that fit last year drifts as your ICP sharpens and your channels shift. Review it quarterly against closed-won data and adjust the weights toward what actually buys. Tying SQL criteria back to revenue keeps the whole qualification system honest instead of decorative.
Treating the score as the decision. The number routes a lead to a human faster. A rep still reads the record and uses judgment. Scoring is triage, not a verdict.
How an SQL definition shows up in your numbers
A working definition moves real metrics, and it is worth watching the right ones so you can prove it.
Track your MQL-to-SQL conversion rate and your SQL-to-opportunity rate separately. If lots of MQLs become SQLs but few become opportunities, your SQL bar is too low. If almost no MQLs reach SQL, marketing is sending the wrong fit or your bar is too high. The two rates together tell you which lever to pull.
Watch cost per SQL alongside cost per lead. A cheaper raw lead that never qualifies is more expensive than a pricier lead that closes. The SQL definition is what lets you measure that difference instead of guessing. Connecting this back to deals, watching where qualification sits in the larger funnel math shows you which stage is leaking value.
Frequently asked questions
What is the difference between an MQL and an SQL? An MQL has shown enough interest and fit for marketing to keep nurturing it. An SQL has cleared a higher bar, usually adding timing or a direct buying signal, and a rep has agreed it is worth a sales call now. The promotion is a deliberate decision with criteria behind it.
Who decides whether a lead is sales qualified? Sales and marketing decide together on the criteria, in advance. Marketing applies them at handoff; sales confirms or rejects on first contact and logs why. The reason codes from rejections feed back into the scoring model, so the definition keeps improving.
Should I use BANT to qualify leads? BANT (budget, authority, need, timeline) is a useful checklist for the parts of qualification you confirm in conversation, especially authority and timeline. It is weak as a gate before the first call, because you rarely know budget early. Use it to structure the discovery call, not to block leads from reaching a rep.
What SQL score threshold should I set? Start by looking at your last 50 to 100 closed deals and find the score most of them carried when they converted. Set the threshold a little below that, then watch your SQL-to-opportunity rate for a month. If too many SQLs stall, raise the bar. There is no universal number; it is specific to your data.
How many SQLs should marketing deliver per month? Work backward from revenue. If you need 10 new deals, your SQL-to-opportunity and opportunity-to-close rates tell you how many SQLs that requires. A target divorced from those conversion rates just pressures marketing to inflate the count and lower the quality.
Can I automate sales qualification? You can automate the scoring and routing inside your CRM so qualified leads reach a rep in minutes, which is worth doing. Keep a human in the final loop. Automation handles triage and speed; a rep still reads the record and decides how to open the conversation. Setting this up cleanly is mostly a CRM and pipeline job.
Quick checklist
- Write one sentence defining an SQL, and get both sales and marketing to sign it.
- Score three buckets: fit, interest, timing. Require fit to clear a minimum on its own.
- Add negative scoring for free emails, competitors, and stale activity.
- Set a threshold from your own closed-won data, not a borrowed benchmark.
- Put an SLA on the handoff: response time, disposition logging, and a reject loop with reason codes.
- Review the model quarterly against deals that actually closed.
A sales qualified lead is only as good as the agreement behind it. If your reps and your marketers are still arguing about lead quality, the fastest fix is rarely more leads, it is a shared definition with a number attached and a handoff that closes the loop.
If you want a second pair of eyes on yours, book a 30-minute working session with Lead The Way. We will look at your last quarter of closed deals, find the score and the signals that predicted them, and leave you with an SQL definition your reps will actually trust. Bring your CRM export and we will start from your real numbers.