Sales Accepted Lead (SAL)

A Sales Accepted Lead is the moment a marketing lead becomes the sales team's problem. Marketing scores a lead, hands it over, and sales has 24-48 hours to either accept it (turning it into a SAL) or reject it back. The SAL is a contractual artifact — a paper trail that exists primarily so the VP Marketing and the VP Sales can argue about the funnel using shared definitions instead of vibes.

How a Sales Accepted Lead Differs from MQL and SQL

The standard B2B funnel has three handoff stages: MQL (Marketing Qualified Lead — marketing thinks it's worth a call), SAL (sales agrees to work it), and SQL (Sales Qualified Lead — discovery is done, pain is real, opportunity created in the CRM). The SAL sits in the middle as a buffer. It exists because without it, the MQL→SQL conversion becomes a black box where marketing claims it sent 500 good leads and sales claims it received 50.

Acceptance criteria are negotiated in a service-level agreement (SLA): firmographic fit (company size, industry, geography matching the ICP), contact role (decision-maker or influencer), engagement signal (demo request, pricing-page visit, content download), and freshness (under 14 days). A lead that meets the SLA, gets routed to a rep, and is rejected without an attempt is the source of approximately 100% of marketing/sales fights at any company over 50 people.

Worked Example: A Month of MQL-to-SAL Conversion

Marketing generates 240 MQLs in April. The SDR team works through them and accepts 156 as SALs. That's a 65% MQL→SAL conversion rate — within healthy range. Of those 156 SALs, 72 become SQLs after discovery (46% SAL→SQL). 22 of those eventually become closed-won deals over the next two quarters. Funnel math: 9% MQL→customer, which is solid for outbound-heavy or self-serve-resistant categories.

When Sales Teams Use the SAL Definition

RevOps uses SAL volume to enforce the marketing-sales SLA — if marketing isn't sending enough SAL-grade leads, demand-gen budget gets reviewed. The CMO uses MQL→SAL conversion to validate scoring models. The VP Sales uses SAL→SQL conversion to coach SDRs (a rep accepting leads but not converting them is doing intake, not selling). Recruiters interviewing SDRs ask for SAL→SQL rates because it's a cleaner signal of qualification skill than raw meeting count, which any SDR with a calendar can inflate.

CFOs care when CAC payback math depends on attributing pipeline to marketing investment. If 90% of SQLs trace back to outbound, marketing's MQL and SAL volume is theater regardless of how impressive the conversion rates look on the dashboard.

Common Sales Accepted Lead Gaming Patterns

The handoff gets gamed in both directions. SDRs measured on SQL conversion reject borderline leads aggressively to protect their downstream rate — the SAL→SQL number stays clean while marketing's MQL volume looks worthless. The opposite happens when SDRs are measured on activity: every MQL gets accepted as a SAL because rejection requires a comment field and acceptance is a single click. Then marketing's MQL→SAL rate looks great while half the "accepted" leads sit untouched for weeks before going stale.

The other classic exploit is sourced-pipeline laundering. A rep finds a contact through cold outbound prospecting, then routes the contact through a marketing landing page so it lands in the database as an MQL — converting it to a SAL gives marketing credit for pipeline that was actually outbound-sourced. This shows up as suspiciously high MQL-to-opportunity conversion in territories with aggressive SDR teams. The metric doesn't tell you whether the lead originated where it claims to have originated. Only the activity log does, and nobody reads the activity log.