What to Do When Sales Says B2B Lead Quality Is Bad
Content Syndication · Published 2026-10-23
When sales says B2B lead quality is bad, work through five checks in order before you reject the batch: definition, timing, routing, verification and the data itself. Each check takes under an hour and points at a different owner, so the order tells you who has to fix what. Rejecting leads or switching vendors comes after those five, because a vendor swap cannot fix a lead that sat in an unowned queue for four days.
Diagnosing B2B lead quality complaints in the right order
B2B lead quality complaints arrive as one sentence and hide five separate problems. Checking them in the wrong order wastes a sales cycle: teams re-brief the supplier or add a scoring layer before anyone confirms the lead reached a rep in a callable state. The sequence below runs from the cheapest check to the most expensive, which is also the order in which each one tends to explain the complaint.
1. Definition mismatch
“Bad lead” often means “this does not match what I expected” and sometimes means “this contact is fake”. If marketing qualifies on firmographic fit and intent signal while sales judges on budget authority and active buying stage, both sides are applying a real standard and the complaint never resolves. Pull the last twenty rejected leads and score them against the written MQL definition, not the definition either team remembers agreeing to. Many disputes end at this step.
2. Timing
A lead that waits four days for a first call is a different lead from the one that arrived on day one. B2B interest decays quickly, and a rep dialling into a cold contact will call the lead bad even when the record was accurate. Measure the gap between lead creation and the first outreach attempt. If it runs in days rather than hours, fix the handoff before you touch anything upstream.
3. Routing
Leads that land in the wrong territory, the wrong rep’s queue or a shared inbox nobody owns read as low quality because nobody follows them up. Audit where every lead from the last batch went and how long it sat there before a person touched it. Routing faults are common in programmes that deliver by email attachment or CSV, where assignment depends on someone remembering to upload the file.
4. Verification
Verification is a stack of three layers: a syntax check, a deliverability check, and confirmation that the contact opted in to hear about this topic. A supplier who confirms only that an email address is well formed has validated a string and verified nothing about the person. Ask your provider which layers they run and how each one is documented, and use how to vet a content syndication vendor as the checklist. Reject a batch on verification grounds only after you have confirmed what “verified” was meant to cover in the contract.
5. Poor source data
If the first four checks come back clean, the data source is the problem and you have the evidence to say so. The next step is a conversation about the replacement policy: a supplier should replace leads that fail the agreed criteria without a negotiation. If the contract does not spell out replacement terms, settle that before the next batch ships.
A worked example of the five checks
Take a hypothetical programme that delivered 200 leads in a month, with sales rejecting 60 of them as bad. Nothing below describes a real client, and the numbers exist only to show how the sorting works. Pull the 60 rejected leads and assign each one a single cause using the table.
| Check |
Evidence to pull |
Owner of the fix |
| Definition |
Rejected lead against the written MQL criteria |
Marketing and sales together |
| Timing |
Hours from creation to first call attempt |
Sales operations |
| Routing |
Queue or owner the lead landed in, and when it was opened |
Revenue operations |
| Verification |
Bounce result and opt-in record per contact |
Supplier, under the contract |
| Source data |
Wrong company, wrong role, duplicate or fabricated record |
Supplier, under the replacement policy |
If most of the 60 land in the first three rows, the supplier has no replacement to owe you and a new supplier would receive the same complaint. If most land in the last two, you hold a dated list of records to send back. Either result gives the next conversation a fact base, and it keeps the argument about specific leads instead of about opinions.
What to bring to the supplier conversation
If the sorting points at steps four or five, send the supplier a file and keep the message short. List each affected lead with its delivery date, the check it failed and the contract clause that covers replacement. A dated list moves faster than a general complaint about quality, because the supplier can match each row to a batch and a verification log.
If the sorting points at steps one to three, the file goes to your own team instead. Share the twenty-lead definition test with sales leadership, put the time-to-first-touch number on the weekly pipeline report, and name an owner for every queue that receives delivered leads. Set a target of a first attempt within one business day for the next batch, then rerun the same sort on that batch so you can see which causes shrank.
Why the order matters
Running the checks in sequence changes what gets fixed. A team that starts at step five can end up changing suppliers every quarter while the leak in routing or timing stays open and produces the same complaint under each new name. Every re-brief also resets the learning curve: the new supplier has to relearn the account list, the exclusion rules and the messaging, which is the work the previous one had already done.
Programmes that stop having this argument agree on a shared MQL definition before the first lead ships and track time to first touch as a reported metric. They also treat verification as something to document and not assume. The fuller version of that audit, with scoring across a whole quarter, is in how to run a B2B lead quality audit.
What good verification looks like in practice
A programme that has this working can answer four questions about any lead in the file without opening a support ticket:
- What definition it was scored against
- When it was delivered and when it was first contacted
- Who owned it, and how long it sat in their queue
- Which verification steps it passed
If any of those four answers is a shrug, close that gap before you open a conversation about the source. Our smart syndication programmes are built around that audit trail, so each delivered lead carries its definition, delivery time and verification record.
If your team runs the diagnostic every quarter and still ends at step five, the source needs fixing properly, and that conversation should include the replacement terms.
Talk to the team