How Do You Define a Sales-Accepted Lead?

How do you define a sales-accepted lead?

A sales-accepted lead is a lead that a salesperson has reviewed and agreed to work. Define it with three parts: the criteria a lead must meet before handoff, a time limit for sales to accept or reject it, and a short list of rejection reasons. Write it down, agree it with both teams, and track it in your CRM.

Most fights between marketing and sales come down to one sentence: "These leads are bad." Marketing hears that sales ignores good leads. Sales hears that marketing counts junk to hit a number. Both are often partly right, and neither can prove it.

A clear sales-accepted lead stage settles that argument with data. It creates a moment where sales says yes or no to each lead, on the record, with a reason. That one stage makes the whole funnel easier to manage.

What is a sales-accepted lead, and how is it different from an MQL or SQL?

A marketing-qualified lead, or MQL, meets marketing's criteria for handoff. A sales-accepted lead, or SAL, is an MQL that sales has reviewed and agreed to pursue. A sales-qualified lead, or SQL, is one sales has spoken to and confirmed as a real opportunity. The SAL sits between the two as the handshake.

Without the SAL step, leads jump from "marketing says it is good" to "sales is working it" with nothing in between. That gap is where leads go to die. They sit unworked, and nobody can tell whether sales looked at them and passed, or never looked at all.

The SAL stage closes that gap. It turns a silent handoff into an explicit decision. That decision is the data both teams need to improve.

Why do marketing and sales need a written SAL definition?

Because without a written definition, every rep applies their own standard, and every disagreement becomes an opinion. A written SAL definition gives both teams a shared rule for what gets handed over, how fast sales responds, and what counts as a valid rejection. It turns arguments about lead quality into numbers you can review.

It also protects both sides. Marketing knows exactly what it is being measured on. Sales knows it will not be blamed for ignoring leads that never met the bar. When both teams sign the same page, the conversation shifts from blame to fixing the funnel.

Keep the document short. One page covering the handoff criteria, the response time, the rejection reasons, and who reviews the numbers each month is enough. If you have not yet agreed what a qualified lead is, start with what should count as a qualified lead for a small team.

What criteria should a lead meet before sales accepts it?

A lead should meet fit criteria from your ideal customer profile, show a real signal of interest, and include enough information for a rep to act. Typical fit criteria are company size, industry, and role. Typical interest signals are a demo request, a pricing page visit, or a reply to outreach. Missing contact details should block handoff.

Make the criteria checkable. "Senior decision maker" is vague. "Director level or above in sales, marketing, or revenue operations" is checkable. A rep should be able to look at a lead record and decide in under a minute whether it meets the bar.

Also define what disqualifies a lead outright, so those never reach sales at all. Students, competitors, job seekers, and personal email addresses are common examples. I wrote about this in how to write a disqualification rule for inbound leads.

How fast should sales accept or reject a lead?

Set a time limit, often within one business day for inbound leads and a few days for lower-intent leads. The exact number matters less than having one and measuring it. A lead that waits a week for a decision has usually gone cold, whatever its quality was when it arrived.

Write the time limit into the definition as a service level agreement between the teams. Marketing agrees to deliver leads that meet the criteria. Sales agrees to accept or reject them within the window. Both sides are accountable.

Track response time automatically. Use a date property that records when the lead was handed over and another that records when sales made a decision. The gap between them is your response time. Review it weekly until it stabilizes.

What should happen when sales rejects a lead?

Sales should pick a reason from a short, fixed list, such as wrong company size, wrong role, no real interest, bad contact data, or already in an active deal. The lead then returns to marketing for nurture or is closed out. Rejection reasons are the most useful data in the whole process, so make them required.

Keep the list short, around five to seven reasons. A long list leads to random choices. A free-text "other" field is fine as long as it is not the default answer.

Review rejection reasons monthly. If most rejections say "wrong role," your targeting or form fields need work. If most say "no real interest," your scoring may be counting the wrong signals. Each pattern points to a specific fix.

How do you put the SAL stage into your CRM?

Add a lead status or lifecycle value for "sales accepted," a required rejection reason property, and date stamps for handoff and decision. Build a view that shows each rep their pending leads, and an automation that alerts the owner when a lead passes the time limit without a decision. Keep the setup simple enough that reps actually use it.

In HubSpot, many teams use lead status or lifecycle stage for this, but the exact setup depends on how your account is already configured. Avoid creating a new stage that conflicts with existing reports or workflows. Check what depends on those properties before you change them.

Make accepting or rejecting a lead a one-click action if you can. The more effort the decision takes, the more leads sit undecided. A simple choice with a required reason is easier for reps than a long form.

How do you know the definition is working?

Track three numbers: the acceptance rate of handed-over leads, the median response time, and the share of accepted leads that become sales-qualified. Rising acceptance and steady conversion mean marketing is sending better leads. Fast response times mean sales trusts the process. Review these with both teams together every month.

Watch for warning signs. Very high acceptance with low conversion may mean sales accepts everything without real review. Very low acceptance may mean the criteria are wrong or sales is being too strict. Both are worth a conversation.

The handoff note matters too. A rep who knows why a lead was sent is more likely to accept and work it well. I covered that in what a sales handoff note from marketing should say.

What should you do next?

Draft a one-page SAL definition with handoff criteria, a response time, and five to seven rejection reasons. Review it with one sales leader and one marketing leader together. Then add the status, the rejection reason property, and the date stamps to your CRM, and run it for a month before changing anything.

After a month, look at the rejection reasons with both teams in the room. That meeting will teach you more about your funnel than any dashboard.

I build websites and the automations behind them for lead generation, and the handoff between marketing and sales is where most of that work proves its value. If you want help defining and wiring up a sales-accepted lead stage, reach out and let's chat.