What’s the Difference Between MQLs, SQLs, and SALs?
Align marketing and sales around clear definitions and SLAs: MQL (meets fit + intent), SAL (sales accepts within SLA), and SQL (rep confirms sales-ready). Instrument it in HubSpot to remove handoff friction and improve pipeline accuracy.
An MQL is a contact who matches ICP fit and crosses an intent threshold (e.g., demo form or score ≥ set band). A SAL is an MQL that the assigned rep accepts within the SLA—reachable, right account, not junk. A SQL is a SAL that the rep has qualified as an opportunity (needs, timing, authority) or has a scheduled qualified meeting. Add SAL between MQL and SQL to separate acceptance from qualification, enforce speed-to-lead, and clean up pipeline reporting.
MQL → SAL → SQL Handoff Plays
Operational Definitions & HubSpot Setup
MQL (Marketing Qualified Lead): Meets ICP fit (industry, employee count, account tier) and intent (high-value form, pricing/product views, score ≥ threshold). Auto-route to the right rep with task + SLA timer. Capture MQL Date.
SAL (Sales Accepted Lead): Rep reviews and accepts within the SLA (reachable, right persona/account, not duplicate/junk). Update Lead Status to “Accepted” and stamp SAL Date. If not acceptable, select a Disqualification Reason (e.g., student email, non-ICP, no consent) and recycle or suppress.
SQL (Sales Qualified Lead): Rep confirms need and potential value (e.g., BANT/CHAMP signals) and either creates an Opportunity or books a qualified meeting. Stamp SQL Date and move Lifecycle to Opportunity when applicable.
HubSpot instrumentation: Add custom fields for SAL Date and standardized Disqualification Reason. Use Active Lists for ready-to-contact pools, Workflows for assignment/alerts/escalation, and dashboards tracking MQL→SAL, SAL→SQL, speed-to-lead, and stage leakage by source and rep.
30-Day MQL/SAL/SQL Alignment Sprint
- Days 1–5: Finalize definitions; document acceptance criteria and SLA (e.g., 24h).
- Days 6–10: Configure properties (SAL Date, Disqualification Reason); map Lifecycle & Lead Status values.
- Days 11–15: Build routing + alert workflows; add recycle/suppression logic and auto-escalations.
- Days 16–20: Train SDR/AEs on accept/return steps; enforce required fields on disqualification.
- Days 21–30: Launch dashboards for MQL→SAL, SAL→SQL, time-to-accept; review weekly and tune thresholds.
Frequently Asked Questions
Clean Handoffs. Faster Pipeline. Better Forecasts.
We’ll implement MQL/SAL/SQL definitions, SLAs, routing workflows, and dashboards—so you see exactly where leads stall and what to fix next.
Contact Us