What Is SQL (Sales Qualified Lead)?

A Sales Qualified Lead (SQL) is a lead that sales has vetted and accepted as a genuine opportunity — a prospect with a real need the product addresses, plausible budget, enough authority to advance a purchase, and a workable timeline. The SQL stage follows the MQL stage in the classic funnel: marketing flags interest, sales confirms substance. Qualification typically applies a framework such as BANT (budget, authority, need, timing) or a lighter set of company-specific criteria checked during a first conversation. In outbound motions the path is more direct: a prospect who fits the ideal customer profile, replies positively to outreach, and agrees to a meeting is usually treated as an SQL once the first call confirms fit. The SQL designation matters because it is the funnel's handoff point into active selling — the count of SQLs, their conversion to opportunities, and their source are the numbers that connect lead generation activity to revenue.

SQL (Sales Qualified Lead) in Practice

A working SQL definition is written down and shared by everyone it affects. Example criteria for a B2B SaaS team: company within the ICP (industry, 50-500 employees), contact at manager level or above in the buying function, an acknowledged problem the product solves, and agreement to a next step. Whether budget must be confirmed at this stage is a deliberate choice — early-stage deals often have need before they have budget — but whatever the bar is, it should be explicit. The definition matters doubly when lead generation is outsourced: an agency compensated on SQLs or qualified meetings needs the same written criteria the client's sales team uses, plus a dispute process for borderline cases, or the relationship degrades into arguing about what counts. The common mistake is fuzziness — counting every booked meeting as an SQL regardless of fit, which inflates the metric while closers quietly stop trusting the calendar. SQL volume only means something when the definition behind it has teeth.