Quick clarification: this page is about Sales Qualified Leads, the revenue term. If you were looking for the database query language, that is a different topic entirely. In pipeline work, SQL is the moment marketing hands a prospect to sales and the clock starts.
A Sales Qualified Lead, or SQL, is a prospect a sales rep has personally validated as actively evaluating a purchase. Not to be confused with the database query language of the same acronym, an SQL in revenue work is one step past a Marketing Qualified Lead. It requires human verification, documented buying intent, and a real match to the ideal customer profile before pipeline tracking begins.
The six things to know about Sales Qualified Leads before the first handoff from marketing: what makes one, what breaks one, and why the definition decides whether the pipeline is honest.
An SQL is a lead that a sales rep has personally reviewed, spoken with, or researched, and judged as actively evaluating a purchase. The key word is validated. A lead that scored high on a marketing model is still an MQL. The handoff only becomes an SQL when a human on the sales side says the prospect is real, is in-market, and belongs in pipeline tracking.
The signal that separates an SQL from a curious researcher is active evaluation. They have a problem, a timeline, and a willingness to talk to a vendor. They may not be ready to buy this quarter, but they are past the point of casual learning. That intent is confirmed through conversation, not inferred from a form fill or a page view.
Buying intent alone is not enough. An SQL also needs to match the ICP: the right industry, the right company size, the right geography, the right use case. A fast-moving prospect in the wrong segment is not an SQL. It is a lead that would waste a rep hour and distort the pipeline. Fit is the second half of the qualification bar.
The moment a lead becomes an SQL, it leaves the shared marketing queue and lands with a specific sales owner. That ownership is logged in the CRM with a timestamp. From that point, the SLA clock starts, the activity timeline runs under the rep, and the pipeline forecast begins to include the deal. No owner means no SQL.
A healthy SQL pipeline rejects leads. Sales can push back if the prospect is out of ICP, not actually in-market, or missing a decision-maker. The rejection goes back to marketing with a reason, and both teams use that signal to tune scoring and segmentation. A funnel where every MQL converts to SQL is a funnel that is not qualifying anything.
The best teams measure SQL to opportunity conversion, SQL to closed-won rate, and the average cycle time from SQL to close. Those numbers decide whether the definition is working. If win rates are falling, the qualification bar is too low. If conversion to opportunity is near perfect, the bar may be too high and real deals are being rejected.
MQL and SQL are often said in the same breath, but they describe two different moments in the funnel. The MQL is marketing saying "this one looks real." The SQL is sales saying "yes, I agree, and I am taking it." The handoff between the two is the single most contested boundary in the revenue stack, which is why both sides need to agree on the definition in writing before any lead moves.
A Marketing Qualified Lead has crossed a scoring threshold based on firmographic fit and behavioral intent: the right company shape plus signals like pricing-page visits, demo requests, or content downloads. The score is a model, not a judgment. An MQL is marketing saying this lead is worth a rep looking at, nothing more.
A Sales Qualified Lead has been reviewed by a sales rep, usually through a discovery call or a research pass, and judged as actively evaluating a purchase. The qualification is a judgment, not a score. An SQL is sales saying this one is real, I am taking it, and the pipeline forecast now includes it.
Between MQL and SQL sits the qualification motion: a discovery call, a research pass, or a short exchange that confirms intent and fit. Some teams call this stage SAL (Sales Accepted Lead) to mark that sales has agreed to look at the lead but has not yet confirmed it belongs in pipeline. Not every team uses that intermediate step, but every team runs some version of the motion.
The simplest test for whether a lead is really an SQL: would sales include it in the weekly forecast? If yes, it belongs in pipeline and the SQL label is correct. If no, it is still an MQL or an SAL. That question keeps the definition grounded in what the business actually counts on, instead of letting the label drift to inflate marketing numbers.
Different industries and sales motions use different qualification frameworks, but almost every one is a checklist of the same handful of questions: who is buying, why now, how much, with what budget, through what process. The frameworks below are the ones that show up in nearly every sales methodology course. Pick one, standardize on it, and make sure every rep can list the fields in their sleep.
The classic framework, originally from IBM. A lead qualifies when the rep confirms the prospect has a budget, the authority to spend it, a real need the product solves, and a timeline for buying. Simple, fast, and still used broadly. The weakness is that early-stage buyers rarely have all four locked in, so strict BANT can filter out real deals that are still forming.
The complex-sale framework favored in enterprise B2B. The rep documents the business metrics the deal moves, the economic buyer who signs, the criteria competing vendors are judged against, the full process from first call to signature, the business pain in the prospect's own words, and the internal champion who sells for you. More rigorous than BANT, and heavier to maintain.
A BANT update that leads with the prospect's challenge instead of the vendor's budget question. The rep asks what the business is trying to solve first, then layers in authority, money, and priority. The reorder matters: starting with the challenge keeps discovery about the buyer, not about qualifying them out of the pipeline on the first call.
The inbound-era framework associated with the modern SaaS motion. Expands BANT to include the prospect's goals and plans, the implications of not solving the problem, and the consequences of inaction. More time to run on a first call, but the richer picture tends to produce better forecasts, better proposals, and higher win rates in competitive deals.
Underneath the acronyms, every framework asks: who is this person, why do they care, what are they trying to buy, when do they need to buy, and who else is involved. The framework is a memory aid for the rep and a consistency aid for the pipeline. The specific letters matter less than picking one and running every lead through the same checklist.
Whichever framework a team picks, the qualification fields should be first-class on the deal record in the CRM, not notes in an inbox. The rep fills them during discovery. The manager reviews them in pipeline review. The forecast weights deals partly by how complete those fields are. A qualification framework that lives only in training slides is not actually running the pipeline.
The MQL to SQL handoff is where most funnels bleed. Marketing hands over a lead, sales does not pick it up fast enough, the prospect goes cold, both teams blame each other. The teams that avoid this have a set of small, boring rituals that remove the ambiguity. None of them are hard to implement. The hard part is enforcing them week after week.
When a lead crosses the MQL threshold, routing logic assigns a specific rep based on territory, segment, round-robin, or capacity. The rep gets a notification. The CRM record shows the new owner and the timestamp of the handoff. There is no shared inbox, no "whoever picks it up first," no ambiguity about who is responsible.
The team sets a service-level agreement for first response, often five minutes to an hour depending on the motion. The clock starts at handoff. The CRM measures response time per rep and per team. SLA breaches surface in weekly reports. The number stays visible because the single biggest killer of SQL conversion is slow first response.
After the first conversation, the rep either accepts the lead as an SQL and advances it to the first pipeline stage, or rejects it with a reason. Acceptance is a specific CRM action, not an implicit one. The acceptance timestamp is the official SQL creation moment that every downstream metric is measured from.
When a rep rejects a lead, they pick from a short list of reason codes: out of ICP, not in-market, no decision authority, bad data, competitor incumbent, duplicate. The rejected lead flows back into a marketing nurture track, and the reason code aggregates into a weekly report that tells marketing which segments are producing weak leads.
The teams meet weekly, or at minimum bi-weekly, to review the handoff numbers: MQL volume, SQL acceptance rate, rejection reasons, SLA compliance, and SQL to opportunity conversion. The point of the meeting is to tune the scoring model and the routing rules. Without this loop, the definition of SQL drifts and both sides lose trust.
Both teams agree on the exact qualification bar in writing, and both teams sign it. The document covers ICP, intent signals, disqualifiers, and the rep's acceptance checklist. When the market shifts or the product changes, the document is updated and re-signed. Verbal agreements on qualification criteria do not survive a quarter under pressure.
SQL is not a pipeline stage. SQL is the moment of entry into the pipeline, which then runs through its own set of stages toward a closed-won or closed-lost outcome. The stages below are the common skeleton most B2B sales teams use. Specific product motions tune them, but the shape is nearly universal because it tracks the same real-world decisions every buyer goes through.
The first stage after SQL acceptance. The rep runs a structured discovery call using the chosen framework, confirms the fit, and documents the buyer's goals, pains, timeline, and process. The output is a deal record with the qualification fields filled in and a decision about whether to advance to the next stage.
The prospect is actively evaluating the product. Demos are scheduled, trials are provisioned, technical teams compare approaches, and the rep is helping the champion build the internal case. This stage can last days or months depending on deal size. The forecast weight on this stage reflects that uncertainty.
The rep sends a formal proposal with pricing, scope, terms, and often a timeline. The buyer reviews internally and comes back with questions, counter-proposals, or asks for a procurement path. The deal is close enough to real that marketing starts to count it in late-funnel reporting.
The buyer has agreed in principle and is now negotiating the specific terms, running procurement, routing legal review, and preparing for signature. The deal is usually heavily weighted in the forecast at this point, and the rep is coordinating stakeholders on both sides to keep the signature on schedule.
The contract is signed. The deal moves to closed-won. Revenue is booked. The customer success or implementation team is notified and the project tooling takes over. The CRM retains the full history of every touch from MQL through signature, which becomes the base for renewal and expansion motions later.
Deals that do not close are marked closed-lost with a reason: competitor, no decision, timing, budget, bad fit. Those reasons feed back into marketing and product. Lost deals stay in the CRM so the team can re-engage months later, which is often where strong closed-won rates in year two come from.
An SQL definition is only as good as the metrics it produces. Three numbers decide whether the current bar is working: how often an SQL becomes an opportunity, how often an opportunity becomes a win, and how long the full cycle takes. Track those three per source, per segment, and per rep, and the definition tunes itself over the course of two or three quarters.
The percentage of SQLs that advance past discovery into a formal opportunity. A healthy number depends on the motion, but the direction matters more than the absolute: if the conversion rate is falling, the qualification bar may be too low. If it is near perfect, real deals may be getting rejected and the bar may be too high.
The percentage of opportunities that end in closed-won. A rising win rate on a stable volume usually means SQL quality is improving. A falling win rate on rising volume is a signal that the funnel is pulling in leads that look right but do not actually convert, which is a definition problem, not a sales execution problem.
How long it takes a typical deal to move from SQL to signature. Shorter cycles usually mean the SQL definition is tight: deals that enter the pipeline are already real. Longer cycles can mean the bar is too loose and deals are getting stuck in discovery and evaluation. Compare cycle time by source to see which channels produce the fastest-moving pipeline.
The percentage of SQLs that get a rep response within the SLA window. Below 90% is a red flag. Response speed has one of the strongest correlations with conversion in every published study on inbound sales, and the easiest way to raise SQL to opportunity rates is often to raise SLA compliance before touching the scoring model.
The percentage of leads that sales rejects after acceptance, broken down by reason code. A rising rejection rate for "out of ICP" means marketing scoring is pulling in the wrong accounts. A rising rate for "not in-market" means the intent signals are weak. The reason distribution is the most actionable report in the funnel.
The ratio of open SQL and opportunity value against the quota the team is carrying. Standard rule of thumb is three to four times the target, though it varies by motion. Pipeline coverage reads off the SQL volume at the top of the funnel, so if coverage is thin, the fix usually starts with SQL creation rate, not with closing effort on existing deals.
Strkr runs the full motion in one CRM: lead scoring, routing, qualification fields, SLA timers, acceptance and rejection actions, and the reports that tell you whether the definition is actually working. Marketing and sales see the same records, so the handoff stops being contested.
SQL stands for Sales Qualified Lead. It describes a prospect that a sales rep has personally reviewed and validated as actively evaluating a purchase. It is separate from the database query language of the same acronym, which is unrelated to pipeline work. In revenue conversations, SQL almost always means Sales Qualified Lead unless the context is clearly technical.
An MQL (Marketing Qualified Lead) has scored high on a marketing model based on fit and behavior but has not been personally reviewed by sales. An SQL has been reviewed by a rep and confirmed as actively evaluating a purchase. The MQL is a prediction from a model. The SQL is a judgment from a human. The handoff between the two is the moment a lead enters pipeline tracking.
Most teams use a qualification framework: BANT (Budget, Authority, Need, Timeline), MEDDIC, CHAMP, or GPCTBA/C&I. The rep runs a discovery call, documents the answers against the chosen framework, and decides whether the lead belongs in pipeline. The specific framework matters less than picking one and running every lead through the same checklist, with the answers stored on the deal record in the CRM.
Three things, in combination: a confirmed match to the ideal customer profile (ICP), documented buying intent, and a human sign-off from a sales rep. Any one of those alone is not enough. A great fit with no intent is a nurture lead. Strong intent with the wrong profile is a tire-kicker. Both plus the rep sign-off is what distinguishes an SQL from everything else sitting earlier in the funnel.
The sales rep assigned to the lead makes the call. Marketing can promote a lead to MQL based on scoring, but only sales can accept it as an SQL. That acceptance is a specific action in the CRM, with a timestamp, that marks the official entry into pipeline. The reason sales owns the decision is that sales owns the forecast and would not want its forecast definition set by another team.
Fast. Industry studies consistently show that response time within five minutes dramatically increases conversion compared to responses that take an hour or more. Most teams set an SLA somewhere between five minutes and one business hour depending on the motion and lead source. The SLA is tracked and reported weekly because slow first response is the single biggest preventable killer of SQL to opportunity conversion.
Yes, and a healthy funnel rejects some SQLs. If the rep finds the prospect is out of ICP, not actually in-market, missing a decision-maker, or has incomplete data, they reject the lead with a reason code. The rejected lead usually goes back into a marketing nurture track, and the reason codes aggregate into a weekly report that marketing and sales ops use to tune scoring and routing rules.
Three primary metrics: SQL to opportunity conversion rate, win rate on those opportunities, and average cycle time from SQL to closed-won. A healthy funnel shows steady or rising conversion with stable or rising win rate and no runaway growth in cycle time. Rejection rate and SLA compliance are the two leading indicators that move earliest when the qualification bar or the handoff motion starts to slip.
No sales call, no migration consultant, no four-month implementation. Enter your card, get 14 days of the full Pro tier, cancel any time before day 14 with zero charge. Spin up a workspace, import your CSV, and have something useful before lunch.
