Sales Qualified Lead (SQL)
A Sales Qualified Lead (SQL) is a prospect that sales has reviewed and confirmed as having the fit, intent, and timing to justify active pursuit toward a deal.
Key takeaways
- Acceptance at this stage creates a forecastable opportunity, which is what distinguishes it.
- Every lead should end as accepted, rejected with a reason, or recycled with a date.
- Quota pressure loosens acceptance and inflates pipeline without any change in demand.
- Written exit criteria turn a rep's judgement into something two teams can audit.
- Unreachable and unqualified are different rejection reasons requiring opposite fixes.
In depth
The SQL step is an acceptance decision taken inside the sales system, by a person or by a rule that stands in for one. A lead arrives from marketing or from a direct inbound request, someone works it, and exactly one of three outcomes follows: accepted and converted into an opportunity, rejected with a stated reason, or returned to nurture with a date. What separates this stage from everything earlier is that acceptance creates a record carrying a value and an expected close date, which then enters the forecast.
Two forces move SQL volume: how strict the acceptance criteria are, and how consistently reps apply them under pressure. When quota coverage looks thin, reps accept marginal leads so the pipeline reads as healthy, and the forecast inflates while demand has not changed at all. Stricter criteria protect the forecast but expose a demand gap earlier, which is uncomfortable and useful in equal measure. Speed is the third lever, since a prospect who would take a call today may not next week.
Teams make this workable by writing exit criteria: the facts that must be confirmed before an opportunity exists. Typically a named problem, a contact with influence over the decision, a plausible budget range, and a date by which something has to change. Most organisations place an SDR between the marketing stage and this one to establish those facts on a short call. Where a scorecard quiz has already captured scale and timeline, that call starts on specifics instead of on discovery.
Acceptance is a judgement, and judgements differ between reps, so the same lead can be accepted by one person and rejected by another on the same day. Auditing a sample of rejected leads is the only dependable way to see how wide that variance is. The stage also fits badly onto low-price self-serve products, where nobody qualifies anything by hand, and onto very long cycles, where a genuinely good fit arriving eighteen months early is rejected and never revisited.
Example in practice
How to measure it
Start with acceptance rate and the mix of rejection reasons behind it. A stable acceptance rate with a shifting reason mix tells you the traffic changed even when the headline number did not. Then measure the share of accepted leads that reach a real opportunity stage and the win rate on those, split by source, since a channel can produce leads that reps accept willingly but never close.
Speed and effort are the operational signals. Track the time from handover to first contact attempt and the number of attempts made before a lead is marked unreachable, because most leads written off as bad were simply never reached. Watch stage age as well: opportunities sitting past the typical duration for their stage are usually acceptances that should have been rejections.
Common mistakes
The most costly habit is rejecting leads without a reason code. The record disappears, and marketing is told only that quality is poor, which cannot be acted on. Require a short, closed list of reasons: wrong company size, no budget, no timeline, wrong contact, unreachable. Keep unreachable separate from unqualified, because one is a follow-up cadence problem and the other is a targeting problem, and they need opposite corrections.
The second is converting leads into opportunities early to make coverage look adequate. Deals with no confirmed problem sit in an early stage for months, distort every conversion rate downstream, and make the forecast unreadable. Enforce the exit criteria as a required field rather than a convention, and run a regular sweep that closes opportunities with no activity and no confirmed next step out of the pipeline.
Frequently asked questions
What qualifies a lead as an SQL?
An SQL must show confirmed buying intent and meet fit criteria such as budget, authority, need, and timing, validated by sales rather than marketing alone. Typical triggers include requesting a demo, replying to outreach, or matching strict firmographic rules.
Does every MQL become an SQL?
No, only a portion of MQLs advance to SQL after sales confirms genuine intent and fit. The MQL-to-SQL conversion rate is a key indicator of whether your MQL definition and nurturing are aligned with what sales can actually close.
How do quiz funnels speed up SQL creation?
Because a scorecard quiz captures qualifying answers and intent signals like a demo request in one flow, high-fit respondents can bypass lengthy nurturing. This lets you route the strongest leads to sales as SQLs almost immediately.
What is the difference between an SQL and an opportunity?
An SQL is a lead that sales has agreed to work; an opportunity is the deal record created once qualification is confirmed. In many systems the SQL is the moment of acceptance and the opportunity follows immediately, but keeping them distinct lets you measure how many accepted leads actually survive first contact.
Who decides whether a lead becomes an SQL, the SDR or the AE?
Usually the SDR proposes and the AE accepts, which creates a useful second check. The SDR confirms the basic criteria on a call, the AE decides whether the deal is worth a slot in their pipeline, and the acceptance or rejection is logged. Where only one role decides, acceptance standards tend to drift with quota pressure.
How many contact attempts should you make before giving up?
More than most teams make, and spread across channels rather than repeated on one. A common working pattern is several attempts over a week or two, mixing phone, email and a social touch, before marking the lead unreachable. Record the attempt count, because leads closed as unqualified after a single email are usually not unqualified at all.
Why does sales reject marketing leads?
Most rejections come down to four causes: the company is the wrong size or sector, the contact has no influence on the decision, there is no timeline, or nobody could reach them. Only the first three are quality problems. Logging which cause applies is what turns an unproductive argument about lead quality into a fixable targeting or cadence issue.
What exit criteria should a lead meet to become an SQL?
At minimum a named problem the prospect wants solved, a contact with influence over the decision, an indication that spending is possible, and a date by which something must change. Write them as required fields rather than guidance. Criteria that live only in a playbook get applied differently by every rep and cannot be audited later.
Can a lead skip the MQL stage and go straight to SQL?
Yes, and high-intent leads routinely should. A demo request, a pricing enquiry or a referral already carries the intent that the earlier stage exists to detect, so routing it through a nurture track wastes the window. Keep a direct path for these, with the same acceptance criteria applied once the lead reaches a rep.