Sales Qualified Lead (SQL): Criteria, Handoff, and Measurement
A sales qualified lead (SQL) is a prospect that a sales team, applying criteria its own organization has agreed on, judges ready for a meaningful sales next step. That judgment rests on evidence: a relevant need, a reasonable fit, some sign of intent, and enough understanding of timing and the buying process to know what should happen next. It does not have to mean the buyer is ready to sign a contract.
That last point trips up a lot of teams. An SQL is a decision about readiness for sales engagement, made by someone responsible for it, and the exact rules differ from one company to the next.
One note on the acronym: in data work, SQL means Structured Query Language, used to query databases. This page covers the sales term only.
What Sales Qualification Actually Decides
Qualification answers a narrow question. Should a salesperson spend real time on this prospect now, and if so, on what next step?
Because the answer depends on the business, an SQL works best as a documented decision with three parts: who makes it, which criteria they apply, and what record they leave behind. Product documentation shows how much this varies. HubSpot's lifecycle stage documentation separates marketing qualification, sales qualification, and the point where a record is associated with a deal, and it lets companies customize those stages. That describes one CRM's model rather than a universal definition, but it illustrates a useful idea, which is that qualifying a lead and creating a deal are different events.
The person deciding may be an account executive, a sales development rep, or a dedicated qualification team. Some organizations support the decision with configured rules or routing. Either way, someone should own the outcome, and the criteria should be written down where both marketing and sales can read them. If two reps would classify the same prospect differently, the criteria aren't clear yet.
Uncertainty is normal here. A qualification decision is always made with incomplete information, so the record should say what is still unknown instead of pretending the picture is complete. In larger B2B marketing and acquisition programs, the SQL definition is where marketing's reporting meets sales capacity, so it deserves explicit agreement.
The Evidence Behind an SQL Decision
Most qualification criteria fall into a handful of evidence dimensions. Treat them as adaptable, not as a checklist every prospect must complete.
Need, fit, and intent
Need asks whether the prospect has a problem your offering addresses. Fit asks whether the organization or person matches the customers you can serve well, by size, industry, region, use case, or whatever matters in your market. Intent asks whether there is a signal that the prospect wants to explore a solution, not just read about the topic. Salesforce guidance on sales qualified leads puts buying intent and readiness for sales engagement at the center of the idea. The specific criteria still differ from one organization to another.
Timing, buying process, and the next action
Timing and process evidence tells sales how to engage. Is there a known timeframe? Who else is involved? What would the buyer need to see before moving forward? These details rarely arrive complete. The goal is to know enough to propose a useful next action, such as a discovery call, a technical review, or a conversation about a tailored proposal.
Buying processes can also be more complicated than a single contact suggests. Forrester's revenue waterfall announcement describes a model built around buying groups and different opportunity types, including opportunities with existing customers. The lead being qualified isn't always one new person. Sometimes the meaningful unit is a group of people inside an account you already serve.
Where BANT and scoring fit
BANT is a familiar shorthand. Salesforce's explanation of BANT qualification covers its four elements, budget, authority, need, and timeline, and it recognizes that rigid use can struggle with complex purchases where several people share the decision. Use BANT as a prompt for good questions, not as a test every SQL must pass in full.
Lead scoring plays a similar supporting role. HubSpot's lead scoring tool overview describes scoring fit and engagement either separately or together, for different kinds of records. Researchers have also studied predicting lead outcomes from CRM data, and one B2B lead prioritization case examined records from a single software company. One case can't establish a universal effect. A score also isn't universal proof of sales readiness. Some organizations let a configured process record a lead as sales qualified once it meets an agreed threshold, and that can work when the threshold reflects the agreed qualification criteria and the data behind it is sound. Whether a score is enough depends on those criteria and on the quality of the evidence it summarizes, not on the score alone.
Two hypothetical situations
Hypothetical example one. A prospect requests a product demo through a website form. The request shows interest, but nobody has confirmed that the company fits your market or that it has a relevant problem. Many teams would hold a short qualifying conversation first. A demo request is a signal. It isn't proof.
Hypothetical example two. Another prospect describes, in a call with a sales development rep, a problem your product clearly addresses, and agrees to a working session with an account executive. Purchase timing is still open. Under many reasonable sets of criteria this prospect could qualify as an SQL, because there is evidence of need and a useful sales next step, even though the buying date is unknown.
SQL Compared With MQL, SAL, and Opportunity
These four labels are often drawn as a straight line. In practice they are configurable, and some organizations skip one or more of them entirely. The table describes common meanings, not mandatory stages.
| Label | What it usually records | Who typically decides | Common caveat |
|---|---|---|---|
| Marketing qualified lead (MQL) | A lead that meets marketing's agreed criteria for interest or fit | Marketing, often supported by rules | Not always a required step before SQL |
| Sales accepted lead (SAL) | Sales has accepted the lead and taken ownership of follow-up | Sales | Optional label; acceptance is not the same as qualification |
| Sales qualified lead (SQL) | Sales has judged the prospect ready for a meaningful next step | Sales or a qualification team | Criteria are local; contract readiness is not required |
| Opportunity | A potential deal being tracked toward a decision | Sales, inside the CRM | Its relationship to SQL depends on process and system settings |
Two distinctions matter most. First, acceptance and qualification are separate. Recording that a rep has picked up a lead says who owns it. It doesn't say the evidence supports a sales next step. The Salesforce guidance cited above treats SAL as an optional stage and notes that prospects can enter the SQL stage directly, so you shouldn't add an acceptance step just because a diagram somewhere shows one.
Second, an SQL and an opportunity are not automatically the same moment. Microsoft's lead qualification documentation for Dynamics 365 Sales shows that the records created when a lead is qualified are configurable, and that a lead can reach a Qualified status without an opportunity being created. That is one product's behavior. In your own CRM, decide whether an opportunity is created at qualification, later, or only for some SQLs, and write the rule down.
Direct-to-sales leads deserve a mention too. A prospect who calls sales, arrives through a partner, or is sourced by outbound prospecting may never receive an MQL label. That's fine. The SQL decision applies to them just the same; they simply don't belong in a marketing-to-sales conversion rate.
Building a Handoff Sales Can Act On
An SQL label only helps if the next person can act on it. Research on the sales and marketing interface reviews how companies configure the relationship between the two functions in different ways and how communication across that boundary varies. There's no single correct setup. What follows is a practical recommendation, not a tested standard.
What the handoff record should carry
- Owner. The person responsible for the next step, by name.
- Context. How the prospect arrived and what they engaged with. Note any content used in sales conversations they have already seen, so the rep doesn't repeat it.
- Supporting evidence. What was learned about need, fit, intent, and timing, and who learned it.
- Open questions. What is still unknown, stated plainly.
- Next action. The agreed step and its date.
- Disposition. The current outcome, updated whenever it changes.
- Feedback. A short note back to whoever qualified or routed the lead.
Upstream data capture matters too. When inquiry forms and landing pages collect the details qualification actually needs, reps start conversations with better context. That is partly a question for lead capture website development, not only a CRM setting.
Reading a returned lead correctly
Sometimes sales sends a lead back. The reason matters more than the return itself, and a single "bad lead" bucket hides useful information. Four reasons are worth separating:
- Poor fit. The prospect isn't someone you can serve well. Check targeting or the criteria.
- Incomplete information. The prospect may fit, but the evidence was thin. Check data capture or the qualification questions.
- Bad timing. Need and fit are real, but the buyer isn't ready to engage now. Nurture the relationship and revisit later.
- Routing mistake. The lead went to the wrong team, territory, or product line. This is an operations fix, not a marketing problem.
A return isn't automatically an SQL failure. A lead returned for timing may come back qualified months later.
Measuring SQLs Without Misleading Yourself
SQL metrics look simple and are easy to get wrong. The suggestions below are an editorial measurement design rather than findings from a study, and there is no universal target to hit.
Build conversion rates on cohorts
MQL-to-SQL conversion should start from the eligible entities that entered the MQL stage during a defined period, then follow them through a declared observation window. Leads that went straight to sales don't belong in that denominator. SQL-to-opportunity and SQL-to-customer rates need the same discipline: a consistent unit (lead, contact, account, or buying group), clear association rules, deduplication, and cohorts old enough for outcomes to have happened.
Separate the clocks
Time to first response and time to qualification are different measures. So are business hours and elapsed hours. Report each one explicitly, so a fast reply is never mistaken for a fast qualification decision.
Give cost per SQL a declared scope
If you calculate cost per SQL, state which costs are included and match them to the same period as the SQLs being counted. Media alone and full program cost tell very different stories. For wider reading on how digital marketing performance is reported in one market, Arfadia publishes Indonesia digital marketing benchmarks; treat that as background, because it is not a benchmark for SQL rates.
Putting the Definition Into Practice
Writing a usable SQL definition is mostly a coordination job. Marketing, sales, and whoever administers the CRM need to agree on the criteria, the owner, the handoff record, and the measurement rules, then revisit them when returned-lead reasons start to repeat. Start small. A one-page definition both teams use beats a detailed policy nobody reads. Teams that want outside help connecting acquisition, content, and lead capture can look at Arfadia's coordinated digital marketing services, but the criteria themselves still have to come from your own sales process.
Frequently Asked Questions
Who decides whether a lead is a sales qualified lead?
Usually a person or team on the sales side, such as a sales development rep, an account executive, or a qualification team, applying criteria the organization has agreed on. Some companies support the decision with configured rules or routing. What matters is that someone owns the decision and the criteria are written down where marketing and sales can both see them.
Can a lead become an SQL without being an MQL first?
Yes. Prospects who contact sales directly, arrive through a partner, or come from outbound prospecting may never receive a marketing qualified label. They can still be qualified for a sales next step. Just keep them out of the denominator when you calculate marketing-to-sales conversion rates.
Is a demo request automatically a sales qualified lead?
Not necessarily. A demo request shows interest, but it doesn't confirm that the prospect fits your market or has a relevant need. Many teams hold a short qualifying conversation first. Whether a demo request alone is enough depends on the criteria your organization has agreed on.
Do we need a sales accepted lead (SAL) stage?
No. A sales accepted lead stage is optional. It records that sales has taken ownership of a lead, which is different from judging that the evidence supports a sales next step. Some organizations find it useful for accountability, and others qualify prospects directly without it.
Is a sales qualified lead the same as an opportunity?
Not always. An opportunity usually represents a potential deal tracked in the CRM, and whether it is created at qualification, later, or only for some SQLs depends on the process and the system settings. Decide the rule for your own CRM and document it.
How should SQL conversion rates be measured?
Use cohorts. Start from the eligible entities that entered a stage during a defined period and follow them through a declared observation window. Keep the entity unit consistent, remove duplicates, apply fixed association rules, and wait until the cohort has had time to mature. There is no universal target rate.
References
- HubSpot Knowledge Base, Use lifecycle stages, updated July 17, 2026. HubSpot lifecycle stages guide
- Salesforce ANZ, What Is a Sales Qualified Lead?, June 9, 2026. Salesforce sales qualified lead article
- Microsoft Learn, Qualify and convert a lead to opportunity, updated April 30, 2026. Microsoft Dynamics 365 qualification documentation
- Gabie Caballero, BANT qualification guidance, Salesforce, September 3, 2024. Salesforce BANT qualification guide
- HubSpot Knowledge Base, Overview of the lead scoring tool, updated September 2, 2026. HubSpot lead scoring overview
- Forrester, announcement of the next-generation B2B Revenue Waterfall, May 4, 2021. Forrester B2B Revenue Waterfall announcement
- González-Flores and colleagues, The relevance of lead prioritization, Frontiers, March 7, 2025. Frontiers lead prioritization study
- Biemans, Malshe, and Johnson, The sales-marketing interface, online February 15, 2022, university-hosted version of record. Sales-marketing interface review paper
Related Terms
- Marketing Qualified Lead (MQL)
- Lead Scoring
- Lead Generation
- Lead Nurturing
- Qualified Lead
