Sales Qualified Lead (SQL)
A Sales Qualified Lead (SQL) is a lead that has been validated by sales as having real interest, need, and budget timing. Validation is typically performed by an SDR through outreach and discovery conversation, confirming real interest, real need, real budget timing, and ICP fit. The SQL is then ready to be handed off to an Account Executive and enter the sales pipeline as an opportunity. It's the gate between marketing-qualified leads and actual sales pipeline.
The MQL → SQL transition:
A lead becomes an MQL when marketing criteria are met (ICP fit + behavior signals). The SDR then contacts the MQL and validates it through conversation. If the SDR confirms:
- Genuine interest (not just curious browsing).
- Real pain point the product can solve.
- Reasonable budget timing (within 6-12 months, not "maybe someday").
- Authority or path to authority (decision-maker reachable).
- ICP fit confirmed (sometimes marketing criteria are off).
...the MQL becomes an SQL and an opportunity is created in the CRM, handed off to an AE.
Common SQL qualification frameworks:
BANT (Budget, Authority, Need, Timing): IBM-originated, simple but limited.
MEDDIC (Metrics, Economic buyer, Decision criteria, Decision process, Identify pain, Champion): more thorough, common in enterprise.
SPICED (Situation, Pain, Impact, Critical event, Decision): newer framework, popular in modern SaaS.
CHAMP (Challenges, Authority, Money, Prioritization): challenges-first variant.
ANUM (Authority, Need, Urgency, Money): authority-first variant.
Each framework is essentially a checklist for "is this a real opportunity?" SDRs validate against the framework during outreach.
Volume math: MQL → SQL conversion:
Typical 2025 SaaS benchmarks (by lead source):
| Lead source | MQL → SQL rate | SQL → opportunity rate |
|---|---|---|
| Demo request (high intent) | 50-70% | 80-90% |
| Pricing page form (medium-high) | 30-50% | 70-80% |
| Content download (medium) | 15-30% | 60-70% |
| Webinar attendee | 20-35% | 65-75% |
| Cold outbound response | 10-25% | 50-65% |
| List-based outbound | 5-15% | 40-55% |
If MQL → SQL is below 10%, the MQL criteria are probably too loose. If above 70%, MQL criteria are too tight (marketing isn't generating enough lead volume).
The SQL-to-opportunity handoff:
Once an SQL is validated, the SDR books a discovery meeting between the AE and the prospect. The AE then leads:
- Discovery call to fully understand needs.
- Demo or solution presentation.
- Proposal and pricing.
- Negotiation.
- Closed-won or closed-lost.
The SDR's job ends at the SQL handoff; the AE owns the opportunity through close.
Common SQL pitfalls:
Over-qualification: SDRs require too much from MQLs before promoting to SQL. Volume drops, AEs starve.
Under-qualification: SDRs promote everything to SQL to hit meeting quotas. AEs waste time on bad opportunities. AE/SDR trust breaks.
Stale leads becoming SQLs: leads that have been sitting for weeks suddenly qualified. Usually low-quality.
No SQL feedback: AEs don't tell SDRs which SQLs were actually qualified. SDRs can't improve. Quality stagnates.
Ryan's Take
SQL is the most important quality gate in B2B sales, and you can break it in both directions. Too loose and your AEs burn time on junk; too tight and your SDRs become the bottleneck. The fix is a shared definition SDRs and AEs agree on, a weekly look at SQL-to-opportunity conversion to catch drift early, and AE feedback on every SQL ('became an opp' or 'not qualified, here's why'). The failure is SDRs pushing anything that moves to hit meeting quota while AEs trash the quality, until the whole motion goes slow and distrustful. Shared standards beat unilateral ones every time.
What founders get wrong: Letting SDR and AE teams use different SQL definitions. SDRs hit their meeting quota by promoting low-quality SQLs; AEs reject most of them; conversion suffers; trust breaks. The right discipline: SDR and AE agree on SQL definition together; track conversion rate; refine criteria quarterly based on what actually converts.
Related: Marketing Qualified Lead · Lead Scoring · Sales Pipeline · Sales Development Representative · ICP
FAQ
What is a Sales Qualified Lead (SQL)?
A lead that has been validated by sales (typically an SDR) as having real interest, real need, real budget timing, and ICP fit. Ready to be handed off to an AE and enter the sales pipeline as an opportunity.
What's the difference between MQL and SQL?
MQL is qualified by marketing criteria (ICP fit, behavior signals, lead score). SQL is qualified by sales after actual outreach conversation. SQL is the higher bar.
What qualification framework should I use?
BANT (simple), MEDDIC (enterprise), SPICED (modern SaaS), CHAMP, or ANUM. Pick one and use it consistently. Frameworks are tools; the discipline matters more than the choice.
What's a typical MQL → SQL conversion rate?
Varies by source. Demo requests: 50-70%. Pricing page: 30-50%. Content downloads: 15-30%. Webinars: 20-35%. Cold outbound: 5-15%. Below 10% suggests MQL criteria too loose.
Find this article helpful?
This is just a small sample! Register to unlock our in-depth courses, hundreds of video courses, and a library of playbooks and articles to grow your startup fast. Let us Let us show you!
Submission confirms agreement to our Terms of Service and Privacy Policy.