Sales-Accepted Lead (SAL)
A sales-accepted lead (SAL) is a marketing-qualified lead that a sales rep has reviewed and formally agreed to pursue based on shared acceptance criteria.
Key takeaways
- An SAL is a recorded accept decision by a rep, not a score threshold.
- The stage produces two timestamps: marketing handoff and sales decision.
- Strict acceptance criteria shrink SAL volume but protect seller hours.
- Criteria written by one team alone get ignored by the other.
- Product-led and founder-led motions gain little from a formal SAL stage.
In depth
SAL is a status change, not a scoring model. A qualified record lands in a rep's queue carrying a handoff timestamp. The rep opens it, compares it against written acceptance criteria such as firmographic fit, a named contact with buying involvement, and a stated problem, then sets the record to accepted or rejected inside the agreed response window. Two timestamps result: when marketing passed it and when sales decided. Everything else about the stage, including service-level compliance and acceptance rates, is derived from that pair.
The volume of SALs moves with three levers: how strict the criteria are, how much rep capacity exists to review records, and how much upstream volume arrives. Strict criteria push more leads back into nurture and keep seller hours on winnable accounts, but they shrink the pool marketing gets credit for. Loose criteria produce flattering acceptance numbers while burying waste in the rep's calendar. The criteria must be written jointly, because a list authored by one side alone is quietly ignored by the other.
In practice the stage is a CRM workflow: a status field with accepted and rejected values, a mandatory reason code on rejection, and a timer that escalates records left undecided. Teams pair it with a standing weekly review of rejected records so the criteria evolve rather than calcify. When leads come from a scorecard quiz, the tier plus the individual answers travel with the record as an evidence packet, which is why an accept or reject decision can be made in under a minute instead of requiring separate research.
The stage adds nothing where there is no real handoff. In founder-led sales, or in product-led signup flows where a user provisions an account without a human touching it, the ceremony creates admin work and no information. It also measures agreement between two teams, not revenue: a quarter can post excellent acceptance and still miss target if accepted leads never close. And it lags, because acceptance is visible within days while the outcome that validates the criteria takes a full sales cycle to appear.
Example in practice
How to measure it
Two numbers describe the stage. Acceptance rate is accepted records divided by records decided in the period. Response time is the gap between the handoff timestamp and the decision timestamp, read as a median rather than an average so a few forgotten records do not hide a fast norm. Track the share of passed records that were never decided at all separately, because they vanish from acceptance rate while still representing lost demand.
Neither number is meaningful alone. Pair acceptance rate with the rate at which accepted records become opportunities, then with the rate at which they close. Rising acceptance alongside flat opportunity creation means the bar is dropping, not that quality is improving. Break both figures down by source campaign and by rep, since a single rep with a habit of blanket acceptance or blanket rejection will distort the team-level figure.
Common mistakes
The most common failure is accepting everything to avoid an argument. Reps learn that a rejection triggers a conversation with marketing, so they accept, then let the record rot untouched. Acceptance looks near perfect while working behavior says otherwise. The fix is to make rejection cheap and normal: a required reason code, no approval needed, and a standing agreement that a high rejection rate is data about targeting rather than an accusation.
The second failure is letting the acceptance criteria go stale. A list written when the company sold to one segment stays in force after the product moves upmarket, so reps reject good-fit records and marketing keeps producing the wrong ones. Both sides then work around the stage informally. Put the criteria under a fixed review cadence, and change them whenever a rejection reason appears repeatedly on records that later close through another route.
Frequently asked questions
Why bother with a formal SAL stage?
It creates accountability on both sides of the handoff and produces acceptance and rejection data you can act on. Without it, lead quality problems stay invisible and friction between teams grows.
Who decides whether a lead becomes an SAL?
A sales rep or SDR makes the acceptance decision against criteria agreed with marketing in a service-level agreement. The decision should be logged in the CRM within a defined timeframe so the process stays measurable.
What is the difference between an MQL and an SAL?
An MQL is marketing's judgment that a lead meets the qualification bar; an SAL is sales confirming it and taking ownership. The MQL is created by a score or a rule, the SAL by a human decision recorded in the CRM. A lead can be an MQL and never become an SAL, which is exactly the gap the stage exists to make visible.
How long should sales have to accept or reject a lead?
Set a window short enough that the lead is still warm, which as a rule of thumb means one business day for inbound requests and up to two for lower-intent sources. The exact figure matters less than enforcing it. Add an automatic escalation so an undecided record reassigns or alerts a manager instead of sitting silently in a queue.
Who owns the acceptance criteria?
Both teams own them jointly, usually documented in a service-level agreement signed off by the demand generation lead and the sales leader. Marketing needs the criteria to be specific enough to build campaigns against; sales needs them to reflect what actually converts. Criteria authored by one side and handed to the other are ignored within a quarter.
Should an SAL stage exist in a product-led company?
Usually not in the self-serve motion, where users provision accounts without sales involvement. It becomes useful once a sales-assisted tier exists and someone has to decide which product signups deserve a human. In that case the acceptance criteria are usage-based, such as seat count or activation depth, rather than the firmographic checks used for form fills.
Can lead acceptance be automated?
Parts of it can. Hard disqualifiers such as personal email domains, out-of-territory records, or company sizes below the threshold can be filtered before a rep sees them. The judgment that remains, whether the stated problem is one you solve now, resists automation. Automating the whole decision returns you to scoring and removes the accountability the stage was created to provide.
What happens to a lead sales rejects?
It should be routed, not deleted. Records rejected for timing go back into nurture with a recycle date; records rejected for fit are suppressed from sales routing but can stay on a newsletter; records rejected for bad data go to enrichment or verification. Rejection with no defined next step is the main reason recycled demand never returns to pipeline.