Lead vendor renewal cleanup
Lead Vendor Renewal Cleanup Before A Contractor Buys Another Month Of Leads
A contractor lead vendor renewal cleanup guide for checking source cost, owner, first response, second touch, fit, and response proof before buying another month of paid leads.
Short Answer
Before a contractor renews another month with a lead vendor, the safest first move is not to argue about whether the vendor is good or bad. The safer move is to inspect what happened after the leads arrived.
For each lead source, the owner needs a small response-proof table:
| Lead source | Cost or plan | Fit label | Owner | First response | Second touch | Last meaningful note | Next action |
|---|---|---|---|---|---|---|---|
| Lead vendor | Monthly / per-lead / pay-per-call | Good fit / wrong service / duplicate / out of area / unclear | Person or queue | Time and channel | Time and channel | What actually happened | Renew / reduce / pause / clean follow-up |
That table does not prove the vendor is good. It also does not prove the vendor is bad. It gives the contractor enough ground to decide whether the next dollar should go to more leads, cleaner follow-up, a smaller test, or a pause.
Why Renewal Decisions Get Messy
Lead vendors are easy to blame because the bill is visible. Follow-up leakage is harder to see because it hides in call logs, inboxes, spreadsheets, text threads, CRM statuses, voicemail, dispatch notes, and "I thought someone else called them" moments.
That is why a renewal meeting often starts with the wrong question:
"Are these leads worth it?"
A better first question is:
"Can we prove what happened after each lead arrived?"
If the answer is no, the business may be making a budget decision from a partial record. That is a weak place to renew, cancel, dispute, or increase spend.
Google's own Local Services Ads documentation separates lead charging, budgets, and credits into platform-specific rules. A contractor should not assume every paid lead is bad just because some calls did not become jobs. At the same time, a contractor should not keep paying for another month without checking whether the internal response path was strong enough to judge the source fairly.
AI Cleanup Doctor sits in that middle layer: not vendor blame, not lead-generation promises, and not a guarantee of refunds or booked jobs. The work is to make the response path visible enough for a practical decision.
The Renewal Cleanup Question
Before renewal, inspect one sample period. It can be a week, two weeks, or a recent month. The window should be small enough that a real person can check it without dumping private customer records into email.
For each lead, ask:
- Which source sent it?
- Was the lead a possible fit?
- Who owned it?
- When was the first response?
- Was there a second touch?
- What did the final note actually say?
- Is the next action renew, reduce, pause, dispute, clean process, or review manually?
This is not fancy attribution. It is basic operational truth.
| Decision | Record pattern to see first | Safer next step |
|---|---|---|
| Renew smaller | Good-fit leads have visible owner and first response, but second touch is inconsistent | Keep the source small while cleaning the second-touch habit |
| Pause | Many rows have no owner, no first response, or no fit label | Pause expansion and clean the internal handoff before judging the source |
| Review vendor settings | Wrong-area, wrong-service, duplicate, or bad-fit labels are documented | Review targeting, service area, job type, and lead filters without claiming vendor fault |
| Clean follow-up first | Source looks mixed, but response proof is too thin to compare | Build a small response-proof board before changing spend |
| Escalate manually | High-value leads show unclear last notes or estimate/deposit gaps | Review the redacted sample before deciding whether the lead is truly dead |
What To Check Before Blaming The Vendor
1. Source Label
If every lead is just "internet lead," the business cannot compare sources. Use plain labels:
- Google Local Services Ads
- Google Ads lead form
- website form
- phone call from landing page
- Facebook lead
- paid lead vendor
- referral
- repeat customer
- unknown
The label does not need to be perfect. It needs to be consistent enough to prevent a good source and a bad process from being mixed together.
2. Fit Label
A lead can be real but not useful. Label the fit before blaming the vendor:
- good fit
- wrong service
- out of area
- duplicate
- price-only shopper
- emergency but no capacity
- spam or suspicious
- unclear
Do not invent certainty. If the team does not know, mark it unclear.
3. Owner
The most expensive lead can still disappear if nobody owns it. "Sales" is not an owner. "Office" is not an owner. A useful owner field names a person, a queue, or a role that can be checked.
Bad owner field:
- handled
- called
- office
- sales
Better owner field:
- Maria - first call
- dispatch queue
- estimator callback list
- owner review
- hold - wrong service
4. First Response
For paid leads, first response matters because the buyer may have contacted more than one business. A first response record should include the channel and timing:
- called 3:12 pm
- texted 3:18 pm
- voicemail left 3:19 pm
- email reply 3:40 pm
- no first response found
This is not a promise that faster replies will create jobs. It is a record of what happened.
5. Second Touch
Many teams call once, get no answer, and then mentally mark the lead as bad. That can be true. It can also be incomplete.
A second touch record gives the contractor more clarity:
- second call next morning
- text follow-up
- estimate reminder
- quote clarification
- no second touch
- do not contact
- wrong number
6. Last Meaningful Note
The last note should tell a future reviewer what happened. "Done" is not enough.
Useful examples:
- "Left voicemail; no second touch yet."
- "Customer wanted service outside our area."
- "Duplicate of lead #1482."
- "Requested estimate; waiting on photos."
- "Price-only inquiry; no appointment requested."
- "No owner assigned after form submission."
This one field often changes the renewal conversation. It turns vague frustration into a next step.
The Lead Vendor Renewal Table
Use a table like this before deciding whether to buy another month:
| Source | Sample count | Likely fit | Response proof | Main leak | Renewal decision |
|---|---|---|---|---|---|
| Paid lead vendor | 20 | mixed | first response visible on 12, second touch visible on 5 | weak second touch | renew smaller or clean follow-up first |
| Google Ads lead form | 14 | unclear | owner missing on 8 | routing gap | fix form-to-owner handoff |
| Website form | 9 | good | first response visible on 9 | estimate follow-up gap | keep source, clean estimate follow-up |
| Referral | 5 | strong | owner visible on 5 | no tracking issue | keep |
The renewal decision should be boring and practical. If the source is weak and response proof is strong, the vendor may need to be paused or reduced. If the source is mixed and response proof is weak, the next step may be cleanup before renewal judgment. If the source is strong but follow-up is inconsistent, canceling the vendor may hide the real leak.
What Not To Count As Proof
These do not prove a vendor is bad:
- "The team said the leads were bad."
- "Nobody remembers booking jobs from it."
- "The bill felt high."
- "A few callers were not a fit."
- "The CRM says closed-lost with no note."
- "The owner was frustrated."
These also do not prove a vendor is good:
- "The dashboard shows lots of leads."
- "The cost per lead looks normal."
- "The vendor says the campaign is performing."
- "One large job came in last month."
- "The ad platform marked the lead valid."
Good renewal evidence is more specific: source, fit, owner, first response, second touch, last meaningful note.
What To Send For A Safe First Scan
For an AI Cleanup Doctor first scan, do not send passwords, admin access, full call recordings, private exports, payment information, or sensitive records.
Send a small redacted sample instead:
- business website
- lead source or vendor name
- sample date range
- approximate lead count
- public landing page or form URL
- redacted rows with source, owner, first response, second touch, and status
- one sentence describing the renewal decision you are trying to make
If the team uses several sources, start with one vendor and one sample period. The goal is not to audit the entire business in the first pass. The goal is to find whether there is enough response proof to make the next spend decision cleaner.
The v130 Order page now includes a first evidence path section for exactly this kind of decision:
https://cleanup.stoga.com/order
When To Renew, Reduce, Pause, Or Clean Up First
Renew
Renewing may make sense when the source fit is clear, response proof is strong, and the team can explain why another month is worth testing.
Reduce
Reducing may make sense when the source has some fit but the business needs a smaller sample while it cleans ownership, second touch, or routing.
Pause
Pausing may make sense when the sample shows repeated wrong-service, out-of-area, duplicate, or suspicious leads and the internal response proof is already clean enough to support that conclusion.
Clean Up First
Cleanup should come first when the business cannot prove who owned the leads, when first response is missing, when second touch is inconsistent, or when the last notes do not explain what happened.
That cleanup may be cheaper and safer than buying another month blindly.
A Practical Owner Checklist
Before the renewal call, answer these:
- Do we know how many leads came from this source?
- Do we know the cost or plan for the sample period?
- Did we label good fit, wrong service, duplicate, out of area, and unclear?
- Did every lead have an owner?
- Can we see first response timing?
- Can we see second touch?
- Can we explain the last meaningful note?
- Do we know which leads should be suppressed, disputed, reviewed, or followed up?
- Do we know whether the next action is vendor renewal, budget reduction, internal cleanup, or pause?
If the answer is mostly no, the renewal decision is not ready.
How AI Cleanup Doctor Helps
AI Cleanup Doctor can prepare a focused first scan around a lead vendor renewal decision. The scan does not guarantee refunds, lower lead costs, better source quality, rankings, traffic, leads, booked jobs, revenue, indexing, backlinks, or AI citations. Do not guarantee local rankings, lead volume, vendor credits, customer responses, or revenue from a cleanup scan.
It can help organize the decision:
- what source sent the leads
- what looked like a fit
- where ownership became unclear
- whether first response and second touch were visible
- what the last notes said
- what should be cleaned before buying more
That is enough to make the next conversation less emotional and more useful.
Safe CTA
If you are deciding whether to renew another month of contractor leads, start with one sample source and one proof path.
Use the Order page to choose the smallest safe evidence path:
https://cleanup.stoga.com/order
Or review the first-scan readiness page before sending materials:
https://cleanup.stoga.com/first-scan-readiness
Sources Reviewed
- https://www.ftc.gov/business-guidance/advertising-marketing
- https://www.ftc.gov/legal-library/browse/ftc-policy-statement-regarding-advertising-substantiation
- https://support.google.com/localservices/answer/7195435
- https://support.google.com/localservices/answer/7434558
- https://support.google.com/localservices/answer/15100654
Next step
Start with the public URL and the follow-up issue you want inspected: https://cleanup.stoga.com/order