How to fire your lead-gen agency without losing pipeline
A clean transition plan from a generic lead-gen agency to a real outbound motion. Asset checklist, switch sequence, and the 30-day overlap.
The reason most teams that fire a lead-gen agency see pipeline drop is that the agency owned the assets. Domains, lists, sequences, deliverability infra: all gone the moment the contract ends. Here is how to make the switch without losing a quarter.
The mistake: cancelling before signing
Never send a termination notice before the next vendor is signed and scoped. Outbound takes 4 to 6 weeks to ramp. If you cancel first, you create a 60-day pipeline hole that will hit your numbers next quarter.
The asset checklist
Before sending notice, demand and verify:
- All sending domains transferred to a registrar you control
- Mailbox credentials handed over (Google Workspace admin access)
- DNS records exported and documented
- Full sequence content as text or in your sequencer
- Complete lead lists with all enrichment data
- CRM data fully synced and de-duplicated
- Deliverability reports from the last 90 days
- Any custom Clay tables or enrichment workflows
If any of these is missing or refused, escalate before notice. Once notice is sent, your leverage drops to zero.
The 30-day overlap
Run both vendors for 30 days. The new vendor uses the overlap to: take over domains, warm any new mailboxes they add, ingest the lists, re-deploy sequences in the new infra, and validate deliverability. The old vendor keeps producing meetings in the meantime so your pipeline does not stall.
30 days is the sweet spot. Shorter and the new vendor cannot ramp. Longer and you are paying for the same motion twice.
The conversation with your existing vendor
Most agencies will not love this. A clean script:
"We are restructuring our outbound program. Per our agreement, please prepare a full asset transfer package by [date]. We will continue current campaign volume through [end date]. Final invoice will reflect services through that date."
Stay polite and stay specific. Vendors that try to hold assets hostage are vendors that will fight harder than the contract entitles them to.
What if they refuse to transfer
Check your contract first. In almost every case, assets built on your behalf are yours, not theirs. If they refuse, escalate to their leadership and reference the agreement. Most resolve within a week. If not, your legal counsel sends a letter referencing the relevant clauses. Domains can be transferred under ICANN rules regardless of vendor cooperation.
What to do in week 1 with the new vendor
- Inventory all assets received
- Audit deliverability on inherited domains (some may need cooldown)
- Re-validate lists (data older than 90 days needs re-enrichment)
- Set baseline KPIs from the last vendor's reporting
- Document the gaps the new vendor will close in months 1 to 3
What to do in week 4
Cut the old vendor. By now the new vendor should have warmed any new mailboxes, validated the play, and started booking meetings on their own infrastructure. Paying both for more than 30 days is waste.
The signs you should have fired them sooner
- Reports show "emails sent" instead of meetings or pipeline
- You have never seen the actual sequences or lists
- Domains and mailboxes are in their accounts, not yours
- Meetings booked are consistently bad-fit or no-shows
- Cost per booked meeting is over 1 percent of your ACV
The right successor
Pick a vendor that contractually transfers every asset at any time, prices on meetings or pipeline (not activity), and shows you their actual sequences and signals on day one. See our comparison piece on managed outbound vs lead-gen agencies for the specific structural differences.