What Is a Sales Qualified Lead (SQL)?

A sales qualified lead is the point where a lead stops being a guess and becomes a commitment from the sales team. Marketing can say that a person looks interesting. Only a salesperson who has actually talked to that person can say that there is a buying project behind the interest. That is the whole difference, and it is why the decision comes after a conversation, never before.

In most B2B teams, this is one stage in a sequence. The names vary from one company to the next, but the order is stable:

1. Lead. A contact who entered your database: a form, a sign-up, an event list, an outbound list.
2. MQL. A lead that marketing judges ready for a first sales conversation, based on fit and engagement. The details are on the marketing qualified lead page.
3. SAL (sales accepted lead). Sales has looked at the MQL and agreed to work it. Nobody has qualified anything yet: the rep simply commits to reaching out.
4. SQL. The rep has spoken to the lead and the agreed criteria are confirmed.
5. Opportunity. A deal record in the CRM, with an amount, a close date and a stage, that the team forecasts and works until it is won or lost.

Not every lead goes through every step. An inbound demo request from a perfect account can skip the MQL scoring and go straight to a call. An outbound prospect never was an MQL at all. But the qualification step stays the same in every path: a conversation, a check against written criteria, a decision recorded in the CRM.

What makes a lead an SQL

The criteria differ by company, but they almost always cover four questions. Each one has to be answered by the buyer in the conversation, not inferred from clicks.

• Is there a confirmed need? The person described a problem your product solves, in their own words. "We are curious" is not a need. "Our reps lose two days a month cleaning lists by hand" is.
• Is there a project? Someone inside the company intends to change something: a budget line, an initiative, a replacement of the current tool, a new team to equip.
• Is there a timeline? The project has a date, even an approximate one: this quarter, before the next hiring wave, at the renewal of the current contract.
• Can you reach the people who decide? Your contact either is a decision maker or can bring you to them. In larger accounts, you also know roughly who sits in the buying committee.

Many teams use BANT as the grid for these questions: budget, authority, need, timing. BANT works well as a checklist for a first call, as long as budget is read loosely. Early in a cycle, few buyers have a fixed amount approved, so "a budget exists or can be found for this project" is a more honest bar than "the budget is signed". The BANT framework page covers the grid itself; choosing between BANT and other qualification methods is a separate topic, covered in our guide on how to qualify sales leads.

Who decides that a lead is an SQL

The person who had the conversation. In teams with a sales development function, that is usually the SDR, who runs the first call and then hands the qualified lead to an account executive. In smaller teams, the account executive qualifies and works the deal alone. Either way, the decision has three parts that should all be visible in the CRM: the date, the name of the person who made the call, and which criteria were confirmed. A status change with no notes is not qualification, it is a guess with a new label.

SAL vs SQL vs opportunity

These three stages are often mixed up because they follow each other closely, sometimes on the same day. The cleanest way to keep them apart is to ask two questions for each: what proof must be in the CRM, and how can the record leave this stage?

• SAL. Proof in the CRM: an owner is assigned and the first contact attempt is logged. Possible exits: a conversation happens and the lead becomes an SQL; no answer after the agreed number of attempts and the lead goes back to marketing; the lead turns out to be out of scope and is rejected with a reason.
• SQL. Proof in the CRM: notes from a real conversation, with each criterion marked as confirmed (need, project, timeline, access to the decision makers). Possible exits: an opportunity is created; the lead is requalified as not ready and returns to nurturing with a date to try again; the lead is disqualified with a reason.
• Opportunity. Proof in the CRM: an estimated amount, an expected close date, a stage, and a next step booked with the buyer. Possible exits: won, lost (with a loss reason), or pushed to a later period.

The SAL is a commitment to act. The sales qualified lead is a judgment about the buyer. The opportunity is a forecast. When a team skips the SAL, leads wait in queues without an owner. When it merges qualification and opportunity, the pipeline fills with deals that nobody can size or date.

From SQL to opportunity: what must be true in the CRM

This is the step most definitions skip, and it is where qualification pays off or falls apart. A qualified lead should become an opportunity when the rep can fill these fields with facts the buyer gave, not hopes:

• A named contact with a role, and at least one other person involved in the decision when the deal size calls for it.
• The problem, written in the buyer's words. One or two sentences that someone else on the team could read and understand.
• A next meeting on the calendar, accepted by the buyer: a demo, a technical review, a call with the decision maker. Without a booked next step, the deal is not moving.
• A rough deal size, from the number of users, the volume, or the plan the buyer is likely to need.
• A target date tied to the buyer's timeline, not to your quarter end.
• The decision process, at least in outline: who signs, who else must agree, whether procurement or security reviews are needed.

Some teams create the opportunity at the moment of the qualification decision; others wait until these fields are filled. Both work if the rule is written down and everyone applies it the same way. What does not work is creating opportunities with empty amounts and default close dates, because every number built on the sales pipeline inherits the gaps.

Where lead scoring fits

A score never qualifies a lead on its own, but it decides which leads get a call first. Lead scoring ranks contacts by fit and engagement before sales talks to them, so reps start with the leads most likely to pass the criteria. The score is the filter in front of the conversation; the conversation is still the test.

The example below is an illustration written by us. The company and the people are fictional; the steps are the ones most B2B teams follow.

One lead, from first visit to opportunity

The account. A 150-person company that sells software to logistics firms. Its sales team of eight reps builds call lists by hand from several sources, and the head of sales operations, Marcus, has been asked to cut that time.

Lead to MQL. Marcus reads two articles on list building, then visits the pricing page twice in one week and books a demo through the website form. His company matches the target size and industry, and his role influences tool purchases. Marketing scores him above the threshold and routes him to sales with a note listing what he read and when.

MQL to SAL. The SDR who owns the account accepts the lead the same morning and logs a first email and a call attempt. Marcus is now a sales accepted lead: someone is responsible for him, but nobody has qualified anything.

The conversation. On the call, the SDR asks open questions and lets Marcus talk. Need: reps spend about a day a week finding and checking contact details before they can call anyone. Project: the head of sales has asked Marcus to bring a proposal to the next leadership meeting. Timeline: they want a tool in place before two new reps join in about ten weeks. Access: the head of sales signs, and finance reviews anything above a set amount. Budget: nothing is approved yet, but Marcus says the cost of the reps' lost time is the argument he will use.

The qualification decision. Need, project, timeline and access are all confirmed in Marcus's own words. Budget is open but plausible. The SDR changes the lead status in the CRM, ticks the four criteria, pastes the notes and hands the account to an account executive.

Qualified lead to opportunity. Before ending the call, the SDR books a second meeting with Marcus and the head of sales. With that meeting accepted, the account executive creates the opportunity: an estimated amount based on ten users, a close date two weeks before the new reps start, the stage "discovery done", and the head of sales and finance listed as people involved in the decision.

What would have changed the outcome. If Marcus had said "we are just looking, nothing planned this year", the SDR would have recorded the need, marked the lead as not ready and sent it back to nurturing with a date to call again. Same lead, same interest, different decision, because the project and the timeline were missing. If the head of sales had refused the second meeting, the lead would have stayed qualified without an opportunity, with a follow-up task, instead of becoming a deal that nobody can forecast.

This is the first stage that sales owns and answers for. Everything upstream belongs to marketing, everything downstream is pipeline. That position makes the definition one of the few levers that changes both the forecast and how account executives spend their week.

It decides how reliable the forecast is

A sales forecast is built from opportunities, and opportunities are built from qualified leads. When the bar is loose, weak leads enter the pipeline, sit there with optimistic close dates and inflate the number leadership plans against. When the bar is written down and applied, each stage of the pipeline means something, and the forecast can be read without a long round of "is this deal real?" in every review.

It protects the time of account executives

Account executives have a fixed number of hours for discovery calls, demos and proposals. Every qualified lead handed to them takes a slot. If a third of those turn out to have no project, that time is lost on deals that were never going to close, and the good leads wait. A strict definition is less about volume and more about giving the people who close deals a queue they can trust.

How to measure SQL conversion

The upstream health checks, the MQL to SQL rate and the time to first contact, belong to the marketing side of the handoff; both are covered on the MQL page and in lead response time. For the sales qualified lead itself, four measures tell you whether the definition works:

1. SQL to opportunity rate. The share of qualified leads that become opportunities within a set delay. It is the main test of the definition. A low rate means leads are qualified too easily; a rate close to 100% can mean the team only qualifies leads once the deal is already certain, which hides early-stage work.
2. Time to opportunity. How many days pass between the two decisions. A long delay usually means the next step is not booked during the qualifying call.
3. Requalification and disqualification reasons. Not a rate but a list: no project, no timeline, wrong person, budget out of reach. When one reason keeps coming back, the criteria or the first-call script need to change.
4. Closed-won rate. The share that end up as customers, and how long that takes. It reads slowly, but it is the only measure that ties the qualification decision to revenue. See closed-won for how that stage is recorded.

Benchmarks for these rates vary widely with the market, the deal size and how strict the definition is. The most useful comparison is your own rate over time, before and after each change of criteria.

Why contact data matters at the qualification step

The criteria depend on reaching the right people: the decision maker, the other members of the buying committee, sometimes finance. When the CRM only holds the one contact who filled in a form, the rep cannot check access to the decision makers, and the opportunity starts with a single name. Teams that complete the account with the other relevant roles and verified contact details before the qualifying call, through lead enrichment, can test the access criterion on the first call instead of the third.

For a wider view of what "qualified" can mean across marketing, product and sales, see the qualified lead definition.

One email every 2 weeks on go-to-market and sales tactics: subscribe to the Fill Down newsletter.

• Declaring an SQL without a conversation. A high score, a demo request or a pricing page visit can justify a call, not a qualification. When the CRM flips the status automatically, the count goes up and the conversion to opportunities goes down, because nobody checked the need, the project or the timeline.
• Leaving qualified leads in place forever. A lead that has not become an opportunity, been sent back to nurturing or been disqualified after several weeks is not a lead, it is noise in the pipeline. Set a maximum age for the stage and force a decision when it is reached.
• Keeping the criteria in people's heads. If each rep has a personal idea of what qualifies, the numbers cannot be compared between reps, teams or quarters. Write the criteria on one page, add them as fields in the CRM and make the rep tick each one.
• Setting targets on volume alone. When SDRs are paid on volume alone, the bar slides down, and account executives quietly stop trusting the handoff. Pair any volume target with the rate of conversion to opportunities, so that volume and quality are measured together.