Sales Accepted Lead (SAL)

A Sales Accepted Lead (SAL) is a lead that marketing has passed to sales and that a sales rep has explicitly agreed to pursue, sitting between the Marketing Qualified Lead (MQL) and the Sales Qualified Lead (SQL) in a B2B funnel.

How It Actually Works

The SAL stage exists to create accountability at the handoff. When marketing passes an MQL, the rep reviews it against a defined set of criteria, usually built around fit and timing signals, then accepts or rejects it within a set window (commonly 24 to 48 hours). Acceptance means the rep commits to a minimum level of follow-up: typically a set number of outreach attempts over a defined number of days.

Rejection matters just as much. A rejected lead should carry a reason code, such as bad data, out-of-territory, or wrong persona. Those codes feed back into lead scoring and targeting so marketing can stop sending the same bad leads next month.

In practice, many teams skip this discipline. Reps either cherry-pick leads without formally rejecting others or accept everything to avoid conflict, then work nothing. Both behaviors collapse the signal the SAL stage is designed to generate.

Why B2B Revenue Teams Track This

The MQL-to-SAL conversion rate tells you whether marketing and sales are aligned on what a good lead looks like. A rate below 50 percent usually means the lead definition is wrong, the data quality is poor, or reps do not trust the source. A rate above 90 percent sometimes means reps are rubber-stamping everything, which is its own problem.

SAL volume also gives revenue leaders an early read on pipeline health before SQL conversion data arrives. If you have 80 SALs in a given week but your SQL conversion rate historically runs at 35 percent, you can project roughly 28 opportunities entering the pipeline. That projection is only useful if the SAL stage is clean.

Common Mistakes

• No SLA on acceptance. Without a defined window, leads sit unworked while the prospect goes cold. Time-to-first-contact is one of the strongest predictors of conversion.
• Accepting to avoid friction. Reps who accept everything to keep marketing happy generate useless data and inflate pipeline numbers that will not close.
• No rejection feedback loop. If rejected leads do not inform lead scoring, the same quality problems repeat every quarter.
• Conflating SAL with SQL. Some teams merge these stages. Collapsing them removes the accountability checkpoint and makes it impossible to diagnose where handoff breaks down.

How It Connects to Adjacent Concepts

SAL quality depends heavily on what happens upstream. Lead scoring determines which leads get passed. Data enrichment determines whether those leads carry enough context for a rep to make a good accept/reject call in 60 seconds. Lead routing determines which rep sees which lead and how fast.

Downstream, the SAL-to-SQL conversion rate feeds directly into pipeline coverage modeling. If your coverage target is 3x and your SAL-to-close rate is 12 percent, you can work backwards to the SAL volume you need each month. Teams that treat SAL as a vanity metric rather than a calibration point tend to have forecast accuracy problems they cannot explain.

Phi builds GTM pods that own this handoff infrastructure end to end, including the SLAs, the rejection taxonomy, and the scoring feedback loops, so the data that comes out of the SAL stage is actually usable.