Sales Accepted Lead (SAL)
A sales accepted lead (SAL) is a lead that the sales team has reviewed and formally accepted as worth pursuing, the checkpoint between a marketing qualified lead and a sales qualified opportunity.
Key takeaways
- A sales accepted lead (SAL) is a lead sales has reviewed and formally accepted as worth pursuing.
- It is the checkpoint between MQL (marketing-qualified) and SQL (sales-confirmed opportunity).
- It creates accountability at the marketing-to-sales handoff: every lead is accepted or rejected with a reason.
- Its value comes from agreed acceptance criteria (often an SLA) and the feedback loop rejections create.
- It is really a marketing-sales alignment mechanism; accepting everything or rejecting without reasons defeats it.
A sales accepted lead (SAL) is a lead that the sales team has reviewed and formally accepted as worth pursuing, the checkpoint between a marketing qualified lead and a sales qualified opportunity. It marks the moment sales agrees a lead meets the criteria to receive active selling effort.
The SAL exists to create accountability and alignment at the handoff between marketing and sales. Without it, marketing passes leads over the wall and sales quietly ignores the ones it doubts, with no shared record of what happened. The SAL stage makes the handoff explicit: sales must accept (or reject) each lead, on agreed criteria.
What a sales accepted lead is
A SAL is a lead that has passed marketing's qualification (becoming a marketing qualified lead) and has then been reviewed and accepted by sales as genuinely worth working. Acceptance means sales agrees the lead fits the criteria, right profile, real potential, and commits to following up. If sales judges the lead unfit, it is rejected with a reason, which feeds back to improve marketing's targeting.
MQL → SAL → SQL
| Stage | Meaning | Owner |
|---|---|---|
| MQL | Marketing judges the lead qualified | Marketing |
| SAL | Sales accepts the lead as worth pursuing | Sales (handoff) |
| SQL | Sales confirms a real opportunity | Sales |
The SAL sits in the middle, the formal acceptance that turns a marketing-generated lead into one sales owns. Only after sales works it and confirms genuine opportunity does it become a sales qualified lead (SQL).
How the SAL stage works
When marketing passes an MQL to sales, sales reviews it against agreed criteria and either accepts it (it becomes a SAL and gets worked) or rejects it (with a documented reason).
The agreed criteria, usually defined in a service-level agreement between marketing and sales, are the heart of the SAL. They specify what makes a lead acceptable, and the acceptance/rejection data creates a feedback loop that sharpens marketing's qualification over time.
Why the sales accepted lead matters
- Accountability. It makes the marketing-to-sales handoff explicit, no leads silently ignored.
- Alignment. Agreed acceptance criteria force marketing and sales to define "good lead" together.
- Feedback loop. Rejection reasons tell marketing exactly how to improve targeting.
- Clean funnel. It ensures only genuinely accepted leads consume selling time and enter the pipeline.
SAL and marketing–sales alignment
The SAL is really an alignment mechanism dressed up as a funnel stage. Its value comes almost entirely from the shared definition of an acceptable lead and the discipline of accepting or rejecting each one with a reason. Where marketing and sales agree on criteria and hold to the SAL process, the perennial "marketing's leads are bad / sales doesn't follow up" conflict largely dissolves into data both sides can act on.
How to set up the SAL stage, step by step
1. Write the acceptance criteria together
Marketing and sales should agree, in writing, what a lead needs before sales accepts it. Typical criteria cover fit (company size, industry, region), the person (a role that can influence or make the purchase), contact quality (a verified work email or phone number) and a minimum signal of interest (a demo request, a pricing inquiry, or a lead score above a set threshold). Keep the list short. Criteria nobody can check quickly will not be applied consistently. The shared definitions live best in the same document as the MQL and SQL definitions.
2. Set a time limit for the decision
Every MQL should be accepted or rejected within an agreed window, often one business day. Leads that sit unreviewed are the silent failure the SAL stage is meant to prevent. The commitment on both sides is usually written into a marketing and sales service-level agreement, for example marketing delivers a monthly volume of qualified leads, and sales reviews each within a day and makes a first contact within hours of acceptance.
3. Make rejection reasons a fixed list
Free-text rejection reasons are hard to analyze. A short picklist works better: wrong company size, wrong role, no valid contact, existing customer, competitor, student or job seeker, no interest on first contact. After a month, the counts tell marketing exactly which part of its targeting to fix.
4. Recycle, do not discard
A rejected lead is not always a dead lead. Someone rejected for timing can return to lead nurturing and come back when their signals strengthen. Only leads that are clearly out of scope should be closed permanently.
SAL metrics worth tracking
| Metric | What it tells you |
|---|---|
| MQL to SAL acceptance rate | Whether marketing's definition of qualified matches sales' |
| Time from MQL to decision | Whether sales is reviewing leads promptly |
| Time from SAL to first contact | Whether accepted leads are actually being worked |
| SAL to SQL conversion | Whether accepted leads turn into real opportunities |
| Rejection reasons by source | Which campaigns or channels produce poor fits |
A low acceptance rate usually means the MQL threshold is too loose. A high acceptance rate with low SAL to SQL conversion means sales is accepting leads it should reject, often to avoid conflict, and the criteria need tightening. A long gap between acceptance and first contact is a speed to lead problem, and our lead response time statistics show how quickly interest fades.
A worked example
In a month, marketing passes 300 MQLs. Sales accepts 180, a 60% acceptance rate, and rejects 120. The rejection picklist shows 70 of the 120 were rejected for company size, almost all from a single paid social campaign aimed too broadly. Of the 180 accepted, 54 become SQLs, a 30% conversion. Marketing narrows the campaign's audience; next month MQL volume drops to 240 but acceptance rises to 75%, and the number of SQLs stays the same with less work for sales. That is the SAL stage doing its job: fewer arguments, better data. Automating the first contact after acceptance, for example with an automated follow-up, closes the last gap in the handoff.
Common sales accepted lead mistakes
- No agreed criteria. Without a shared definition, acceptance is arbitrary and the stage is meaningless.
- Accepting everything. Rubber-stamping every lead defeats the purpose and clogs the pipeline.
- Rejecting without reasons. Rejections that carry no reason break the feedback loop to marketing.
- Skipping the stage. Passing MQLs straight into the pipeline loses the accountability the SAL provides.
The sales accepted lead is the accountable handshake between marketing and sales: the point where sales formally accepts a lead as worth pursuing, on criteria both sides agreed. Used well, it aligns the two teams, cleans the funnel, and turns the old marketing-versus-sales friction into a shared, improvable process.
Frequently asked questions
What is a sales accepted lead?
A sales accepted lead (SAL) is a lead that the sales team has reviewed and formally accepted as worth pursuing, the checkpoint between a marketing qualified lead and a sales qualified opportunity. Acceptance means sales agrees the lead fits the criteria, right profile, real potential, and commits to following up; if sales judges it unfit, it is rejected with a reason that feeds back to improve marketing's targeting.
What is the difference between MQL, SAL, and SQL?
An MQL (marketing qualified lead) is a lead marketing judges qualified. A SAL (sales accepted lead) is one sales has accepted as worth pursuing, the formal handoff. An SQL (sales qualified lead) is one sales has worked and confirmed as a real opportunity. The SAL sits in the middle, turning a marketing-generated lead into one sales owns, before deeper qualification confirms genuine opportunity.
How does the SAL stage work?
When marketing passes an MQL to sales, sales reviews it against agreed criteria and either accepts it (it becomes a SAL and gets worked) or rejects it with a documented reason. The agreed criteria, usually defined in a service-level agreement between marketing and sales, are the heart of the SAL, and the acceptance/rejection data creates a feedback loop that sharpens marketing's qualification over time.
Why does the sales accepted lead matter?
It creates accountability (making the handoff explicit, with no leads silently ignored), alignment (agreed acceptance criteria force marketing and sales to define a good lead together), a feedback loop (rejection reasons tell marketing how to improve targeting), and a clean funnel (only genuinely accepted leads consume selling time). It is really an alignment mechanism that dissolves the old marketing-versus-sales friction into shared data.
What are common sales accepted lead mistakes?
No agreed criteria (acceptance becomes arbitrary and the stage meaningless), accepting everything (rubber-stamping defeats the purpose and clogs the pipeline), rejecting without reasons (breaking the feedback loop to marketing), and skipping the stage (passing MQLs straight into the pipeline loses the accountability the SAL provides).
Related terms
All Metrics termsACV vs ARR
ACV vs ARR is the distinction between two subscription-revenue metrics: ACV (annual contract value) measures the average yearly value of a single customer contract, while ARR (annual recurring revenue) measures the total recurring revenue across the entire customer base, annualized.
ARR vs MRR
ARR vs MRR is the distinction between two recurring-revenue metrics that measure the same thing at different time scales: MRR (monthly recurring revenue) is the predictable revenue earned each month, and ARR (annual recurring revenue) is that figure annualized, so ARR equals MRR times twelve.
Activity Metrics
Activity metrics are measures of the sales actions reps take, calls, emails, meetings, demos, the leading-indicator inputs of selling rather than its results, capturing the effort that produces pipeline and revenue downstream.
Annual Contract Value (ACV)
Annual contract value (ACV) is the average annualized revenue from a single customer contract, the total value of a contract normalized to a one-year figure, so deals of different lengths can be compared on equal footing.
Automation Rate
Automation rate is the share of a process, tasks, interactions, or workflows, that is handled automatically rather than by a human, measuring how much of the work is done by software.
Average Deal Size
Average deal size is the typical revenue value of a closed deal, calculated by dividing total revenue won by the number of deals over a period.
