MQL vs SQL vs SAL

SAL sits in a spot most funnels skip entirely, which is exactly why it exists. It's the checkpoint nobody built until the handoff kept breaking.

HubSpot's MQL and SQL definitions are the two ends most teams already know: an MQL has engaged with content and shown interest but isn't ready for a pitch, and an SQL has been vetted and is ready for a direct sales conversation, someone requesting a demo or asking about pricing. A Sales Accepted Lead sits between the two, an MQL that a sales rep has actually reviewed, agreed meets the handoff criteria, and committed to working inside an agreed window.

What SAL fixes that MQL to SQL alone doesn't

Without a SAL stage, a rep can quietly ignore an MQL and nobody notices for weeks, because there's no recorded moment where sales agreed to take it. SAL forces that moment into the open. It isn't a quality judgment on the lead, it's a procedural one: sales isn't promising the lead will close, sales is promising to work it inside the SLA. That distinction is what makes each stage of the handoff worth tracking separately instead of lumping the whole thing into one conversion number.

Sources

HubSpot, "MQL vs. SQL: What they are and how they differ," https://blog.hubspot.com/sales/sales-qualified-lead. Demand Spring, "Sales Accepted Lead (SAL)," https://demandspring.com/glossary/sales-accepted-lead/.