Sales Ops Glossary · Pipeline & Forecast
A Sales Qualified Lead (SQL) is a prospect that has been reviewed by a sales development representative and confirmed to meet the organization's minimum criteria for direct selling — typically involving confirmed budget, authority, need, and timeline. When a prospect reaches SQL status, an account executive takes ownership and an opportunity is created in the CRM.
The SQL designation marks the formal handoff point between marketing/SDR activity and the account executive's direct selling motion. Before this point, a prospect is either uncontacted (a raw lead), being nurtured by marketing (an MQL), or being qualified by an SDR. Once they pass the SQL threshold, they enter the sales pipeline as an opportunity — with a stage, a close date, and a rep responsible for driving it to close. The SQL is the moment a lead becomes a business.
What separates an SQL from an MQL or a general contact is confirmed fit — not just inferred intent. An MQL might have visited the pricing page and downloaded a whitepaper. An SQL has spoken with a rep, confirmed they have a problem the product can solve, indicated there is budget available or a buying process underway, and agreed to continue the conversation. The SQL threshold exists to protect the AE's time: every deal they work should have a baseline probability of closing that justifies the investment.
Organizations that don't define or enforce an SQL threshold waste significant AE time on unqualified prospects. An AE who runs discovery calls on prospects with no budget, no authority, or no timeline burns hours that could go toward higher-probability deals. Research from Gartner suggests that 50% of sales time is spent on prospects who will never buy — a problem that a well-enforced SQL threshold directly addresses. The SQL exists to ensure that every hour an AE spends is spent on a prospect who could plausibly become a customer.
For RevOps teams, the MQL-to-SQL conversion rate is one of the most important leading indicators of pipeline quality. If marketing is generating 500 MQLs per month and only 8% become SQLs, there's either a lead quality problem upstream (marketing is optimizing for volume over fit) or a conversion problem at the SDR layer (reps aren't connecting effectively or qualification criteria are too strict). Tracking MQL-to-SQL conversion weekly allows RevOps to surface these misalignments before they compound into a pipeline shortage downstream.
Evaluating pipeline & forecast tools?
Browse software →The most common failure in SQL processes is an undefined or loosely enforced SQL threshold. When the standard is vague — 'the prospect seems interested' — SDRs under pressure to hit SQL quotas pass through unqualified leads to hit their numbers. AEs receive low-quality handoffs, conversion rates drop, and the AE team loses trust in the SDR pipeline. Fixing this requires a written SQL definition with specific, observable criteria that any SDR or manager can evaluate consistently.
SQL criteria should be reviewed quarterly and updated as the business evolves. Early-stage companies often start with a loose SQL definition because they need deal flow to learn. As the ICP sharpens, the SQL threshold can be tightened to improve quality. Conversely, if pipeline is thin and the team is missing quota, loosening the SQL threshold temporarily while investing in pipeline creation can be a deliberate short-term strategy — as long as AEs understand the context.
The handoff from SDR to AE is a moment where deal information is frequently lost. Best-practice handoffs include: a standardized qualification summary field in the CRM (filled out by the SDR) covering pain points, decision-makers identified, budget signals, and timeline; a warm transfer call where the SDR introduces the AE to the prospect directly; and a clear SLA for AE follow-up after the handoff (typically within 24 hours). Teams that invest in handoff quality typically see a 10–15% improvement in SQL-to-close rates.
When SDRs are measured on SQL volume without quality controls, they learn to create SQLs by lowering the bar rather than improving qualification. AEs end up working deals that were never real, trust in the pipeline breaks down, and the underlying pipeline shortage that drove the volume pressure goes unaddressed — often for multiple quarters.
If marketing defines an SQL as 'passed to sales' and sales defines an SQL as 'AE accepted the opportunity after qualification,' the two teams are measuring different things. This creates metric conflicts at QBRs — marketing reports 200 SQLs delivered; sales reports 80 SQLs accepted — and prevents meaningful diagnosis of where conversion is breaking down. A shared, written SQL definition signed off by both teams is non-negotiable.
SQLs that fail to advance after the first AE meeting should be formally disqualified and removed from active pipeline — not left open indefinitely. Dead SQLs inflate pipeline coverage metrics and distort forecast accuracy. Teams without a clear disqualification process typically carry 15–25% dead weight in their pipeline, which leads to chronic forecast overstatement and missed quarters.
SQLs are typically created and managed in a CRM — Salesforce Lead Conversion and HubSpot Deal Creation are the most common workflows. Revenue operations platforms like LeanData and Chili Piper automate lead routing and handoff logistics. Sales engagement tools like Outreach and Salesloft run the SDR qualification sequences that feed the SQL creation process.
An MQL (Marketing Qualified Lead) is a lead that marketing has identified as worth pursuing based on behavioral signals — page visits, content downloads, email engagement, or form fills — combined with firmographic fit. An SQL is a step further: a prospect that a sales development rep has personally qualified against specific criteria involving confirmed need, budget, authority, and timeline. The key difference is human verification — MQLs are scored by automation; SQLs are confirmed by a person.
SQL criteria vary by company and ICP, but most B2B organizations use some version of BANT (Budget, Authority, Need, Timeline) or MEDDIC (Metrics, Economic Buyer, Decision Criteria, Decision Process, Identify Pain, Champion). At minimum, an SQL should have a confirmed pain point the product addresses, a budget or budget process in place, access to a decision-maker or strong internal champion, and a timeline that suggests a decision will be made within a reasonable window. These criteria should be documented and consistently applied by every SDR.
Industry benchmarks for B2B SaaS typically put MQL-to-SQL conversion between 13% and 20%. Below 10% usually signals a lead quality problem — marketing is generating volume but not fit. Above 25% sometimes indicates the SQL threshold is too low and unqualified leads are being counted as SQLs. The right rate depends on your ICP definition and how tightly marketing controls the MQL gate. More important than the absolute rate is the trend — if conversion drops from 18% to 11% over two quarters, there's a problem worth diagnosing.
Yes — AE acceptance or rejection of SQLs is an important quality control mechanism. When an AE reviews a handoff and determines the prospect doesn't actually meet the SQL threshold, they should be able to send it back to the SDR with a documented reason. Tracking rejection rates by SDR reveals who needs qualification coaching. Tracking rejection reasons reveals systemic problems — if 'no budget confirmed' is the top rejection reason, the SQL criteria need to be updated to require budget confirmation before handoff.
The SQL-to-close rate measures what percentage of SQLs eventually become closed-won deals. For mid-market B2B SaaS, a typical benchmark is 20–30%. Enterprise deals often close at lower rates (15–20%) due to longer cycles and more stakeholders. If your SQL-to-close rate is below 15%, either the SQL definition is too loose (low-quality deals are entering the pipeline) or there's a selling problem at the AE layer. Either way, the SQL-to-close rate is the key metric for evaluating the overall efficiency of your lead qualification process.