What Is SQL (Sales Qualified Lead)?

What is an SQL?

SQL, Sales Qualified Lead, is an MQL that the sales team has formally accepted as worth active pursuit. Sales applies its own qualification criteria (commonly the BANT framework: Budget, Authority, Need, Timing) and either accepts the MQL as SQL or rejects it back to marketing for nurture. The MQL-to-SQL conversion rate is the marketing-sales handoff metric.

The SQL designation matters because it represents sales accountability. Sales reps own the SQLs they accept and are measured on what happens next: pipeline progression, opportunity creation, and ultimately closed deals. Marketing is no longer accountable for an SQL; sales is.

In B2B SaaS practice, the MQL-to-SQL conversion typically runs 20 to 40 percent. SQL-to-customer conversion is typically 15 to 30 percent. Multiplying through gives MQL-to-customer of 5 to 12 percent at funnel-level efficiency.

Why SQL matters

For B2B businesses with structured marketing-sales handoffs, the SQL metric is the central accountability point. It measures whether marketing is producing leads worth sales attention and whether sales is converting them efficiently.

For sales-team performance, individual rep SQL counts and conversion rates reveal who is qualifying well, who is closing efficiently, and where coaching is needed.

For sales process improvement, SQL conversion analysis at stage-by-stage level (SQL to opportunity, opportunity to closed) reveals where the process leaks. Targeted improvements at the leakiest stage produce the biggest conversion gains.

For Indian solar businesses, SQL framework is most relevant for solar SaaS vendors and larger solar EPCs with structured sales operations. Smaller installers handle leads informally without explicit SQL designation, treating most leads as opportunities to pursue.

How SQL qualification works

1. MQL arrives. Marketing-qualified lead reaches sales queue.
2. Sales contact. Rep contacts within SLA (typically minutes to hours).
3. Initial conversation. Discovery call to understand lead's situation.
4. BANT qualification. Budget (can afford), Authority (decision maker), Need (clear problem), Timing (decision timeline).
5. Accept or reject. Meets criteria = SQL accepted. Misses = rejected, returned to nurture or marked unqualified.
6. Disposition recorded. Reason for accept/reject logged in CRM.
7. SQL enters pipeline. Sales begins working the SQL through pipeline stages.
8. Opportunity creation. SQL progresses through proposed, negotiating, closing.
9. Customer or lost. Eventually closes or marks lost with reason.
10. Reporting. SQL count, MQL-to-SQL conversion, SQL-to-customer, by source and rep.

Real example: SQL qualification in a solar SaaS sales process

Sales rep gets MQL. Marketing assigns 12 MQLs to the rep that week.

Initial contact. Rep reaches each MQL within 4 hours via WhatsApp and email.

Discovery calls. 7 MQLs respond and engage in initial 15-minute discovery calls.

BANT assessment. Of 7 discovery calls: 4 meet all BANT criteria (accepted as SQL). 2 lack timing (returned to nurture for 90 days). 1 lacks authority (rep tries to reach decision maker).

SQL count. 4 SQLs created from 12 MQLs. MQL-to-SQL conversion: 33 percent.

Pipeline progression. 2 SQLs progress to opportunity and quotation; 1 stalls; 1 lost to competitor.

Closed deals. 1 SQL converts to paid customer over 90 days.

Funnel arithmetic. 12 MQL → 4 SQL → 1 customer = MQL-to-customer 8.3 percent.

Benefits of using SQL framework

• Accountability handoff. Sales owns SQLs explicitly.
• Quality control on sales pursuit. Forces qualification rather than pursuing everything.
• BANT structure. Standardised qualification criteria.
• Diagnostic. Marketing-sales handoff quality measurable.
• Sales capacity planning. SQL volume matched to team size.
• Pipeline-conversion analysis. Where deals get stuck visible.
• Rep performance attribution. Individual SQL counts and conversion rates.

Limitations of SQL framework

Definition subjectivity. SQL criteria vary by company and rep.

BANT rigidity. Sometimes criteria are too strict (rejects good leads) or too loose.

Misalignment with MQL. If marketing-sales SQL definitions diverge, handoff breaks.

Smaller business overhead. Process for small teams may not justify cost.

Gaming risk. Reps over-accept SQLs to look productive; under-accept to manage expectations.

Disposition reporting discipline. Needs consistent reason coding.

Inbound vs outbound differences. SQL meaning can differ across sources.

SQL in Indian B2B sales

Aspect	Typical pattern
MQL-to-SQL conversion benchmark	20 to 40 percent
SQL-to-customer conversion benchmark	15 to 30 percent (B2B SaaS)
MQL-to-customer overall	5 to 12 percent
Indian B2B SaaS sales cycle	30 to 180 days from MQL to closed
Common framework	BANT; MEDDIC for enterprise
Indian solar EPC adoption	Larger EPCs and SaaS vendors; smaller informal
CRM systems supporting	Salesforce, HubSpot, Zoho, QuickEstimate, others

Quick facts

Full form	Sales Qualified Lead
Position in funnel	After MQL, before opportunity
Accepted by	Sales team based on qualification criteria
Common framework	BANT (Budget, Authority, Need, Timing)
Advanced framework	MEDDIC (Metrics, Economic buyer, Decision criteria, Decision process, Identify pain, Champion)
Typical MQL-to-SQL conversion	20 to 40 percent
Typical SQL-to-customer conversion	15 to 30 percent
Primary use	Marketing-sales handoff, pipeline management, capacity planning

Common mistakes about SQL

1. No SQL definition. Treating all MQLs as pursued misses qualification value.
2. Skipping BANT or equivalent. No standard criteria leads to inconsistency.
3. Too-loose acceptance. Sales accepts everything; conversion drops.
4. Too-tight acceptance. Sales rejects too much; misses opportunities.
5. No disposition reason tracking. Loses pattern data.
6. Misalignment with marketing. SQL definition does not match what marketing optimised for.
7. Skipping response SLA. Slow response loses SQLs to competitors.
8. Static definition. Quality patterns shift; recalibrate periodically.
9. Inbound vs outbound mixed. Different source patterns muddle metrics.
10. Confusing SQL count with opportunity count. Different stages.

Key takeaways

• SQL is a Sales Qualified Lead, the formal acceptance of an MQL by the sales team.
• BANT (Budget, Authority, Need, Timing) is the classic qualification framework.
• Typical MQL-to-SQL conversion: 20 to 40 percent.
• Typical SQL-to-customer conversion: 15 to 30 percent for B2B SaaS.
• The MQL-to-SQL handoff is the marketing-sales accountability point.
• Larger Indian solar SaaS and EPCs use formal SQL framework; smaller players informal.
• Stage-by-stage conversion analysis reveals process leaks.

Frequently Asked Questions

Sources

• HubSpot Inbound Sales Methodology. MQL-SQL framework.
• Salesforce State of Sales Reports. SQL conversion benchmarks.
• SiriusDecisions / Forrester. Demand waterfall framework.
• BANT methodology. Classic sales qualification framework.
• SaaSBoomi. Indian SaaS sales process benchmarks.
• NASSCOM SaaS Reports. Indian B2B SaaS conversion data.
• MEDDIC framework documentation. Advanced sales qualification methodology.