Sales-Accepted Lead (SAL) Velocity

What is Sales-Accepted Lead (SAL) Velocity?

Sales-Accepted Lead velocity is the speed, typically measured in hours or days, at which sales formally accepts a marketing-passed lead into active working status after handoff. A lead becomes an SAL when a sales representative reviews it against agreed criteria and confirms it as worth pursuing, distinct from simply being delivered as an MQL. SAL velocity is tracked alongside SAL rate, what percentage of MQLs get accepted, as a pair of metrics that together describe both the quality and the responsiveness of the marketing-to-sales handoff.

Where is Sales-Accepted Lead (SAL) Velocity used?

SAL velocity is used in B2B revenue operations reporting as a leading indicator, tracked in the CRM alongside MQL volume and pipeline contribution. It is most relevant in organizations that have formalized a distinct SAL stage between MQL and SQL in their funnel definitions.

Why is Sales-Accepted Lead (SAL) Velocity Important?

• Trust signal: a fast SAL velocity signals that the MQL definition is producing leads sales trusts enough to act on quickly, without a secondary internal debate about fit.
• Early warning: a slow or declining SAL velocity is an early warning sign of MQL definition drift, visible weeks before it would show up as a flat pipeline number.
• Fast feedback: unlike pipeline contribution, which lags marketing activity by 60 to 90 days, SAL velocity is measurable within days of handoff, making it one of the fastest available signals of program health.

How does Sales-Accepted Lead (SAL) Velocity Work and Where is it Used?

SAL velocity requires two timestamps in the CRM: the moment a lead is passed from marketing (MQL creation) and the moment sales marks it accepted (SAL status). The difference between the two timestamps, averaged across a cohort of leads, is the SAL velocity for that period. Organizations typically track this by lead source and by campaign, since velocity often varies significantly across channels even when overall MQL volume looks stable.

Key Takeaways/Elements:

• Leading indicator: SAL velocity surfaces MQL quality problems faster than pipeline contribution can.
• Defined SAL stage required: it requires a formally defined SAL stage in the CRM, distinct from MQL and SQL.
• Source-level diagnosis: declining SAL velocity by source is typically the first visible sign that a specific channel’s targeting has drifted.

Real-World Example:

A demand gen team at a 250-person B2B company noticed pipeline had gone flat despite steady MQL volume. Reviewing SAL velocity by source revealed one channel’s leads were sitting unaccepted for an average of six days, far above the two-day company average, pointing sales leadership to a specific channel-level trust problem weeks before it would have shown up in the pipeline number.

Use Cases:

• Early warning on definition drift: monitoring SAL velocity by source to catch a quality problem before it shows up in lagging pipeline data.
• Diagnosing handoff bottlenecks: distinguishing a slow SAL velocity caused by an SDR capacity issue from one caused by lead quality.
• Complementing SAL rate: pairing velocity with acceptance rate to separate how many leads are accepted from how fast that acceptance happens.

Machintel Perspective

Across 4,000+ campaigns annually, what we see at Machintel is that SAL velocity moves before pipeline does, and teams that only watch pipeline contribution are always diagnosing a problem two months after it started. We track SAL velocity by source in every program we run because it is the fastest honest signal we have that a qualification definition needs attention.