Cold outreach lands or it does not, and the list decides a lot of it
A sequence is loaded, the sending domains are warmed, and nobody has checked whether the 12,000 prospects scraped last month are real people. Cold sending has no safety net: there's no engagement history telling the receiving provider you're wanted.
Cold lists are also the worst in the business. Scraped data, guessed patterns, and job titles from a directory updated whenever someone remembered. A guessed address at a real company is exactly the shape of a bounce.
The order the work happens in
Verify before the sequence, never during
A sequence discovers bad addresses by sending to them, which is the expensive way to find out. Check the file first, and your first step goes out to addresses that at least exist.
Split by what came back
Valid addresses go into the main sequence. Catch-all and unresolved results go into a separate one at a lower daily volume, so a bad guess in that group cannot damage the sequence that is working.
Cap the daily volume per mailbox
Cold sending fails on volume as often as it fails on data. A new mailbox sending two hundred a day looks like a new mailbox sending two hundred a day, whatever the list quality.
Watch the first fifty replies for the wrong signal
Out-of-office replies from people who've left mean your data source is stale in a way verification can't see. That address exists, and it's dead as a prospect.
Re-check before any second campaign to the same file
B2B data decays at roughly a quarter of the file a year through job changes, so a list verified six months ago is meaningfully different now.
What each result means here
The same four results and their flags, read against this job. A catch-all worth keeping in one situation is one to exclude in another.
| Result | What to do with it |
|---|---|
| Valid | Main sequence. This is the group the campaign is built on. |
| Invalid | Remove. On cold data these are usually pattern guesses that were wrong. |
| Catch-all | A separate low-volume sequence. Common at larger companies, and a guessed name at a catch-all domain accepts and then bounces later. |
| Unknown | Hold, or send at low volume from a mailbox you are willing to risk. Never mix into the main sequence. |
| Role flag | Drop for most cold outreach. A message to info@ rarely reaches the person and frequently produces the complaint. |
| Disposable flag | Remove. A throwaway address on a prospect list means the data source is worse than you thought. |
How you know it is finished
The main sequence runs under 2% bounces across a full cycle and the awkward segment is running separately, so a bad guess in the second group cannot take down the first.
What this does not fix
Cold lists are where the billing rule matters most, because the hard segment is large: a scraped B2B file can run 40% catch-all and unknown. A catch-all row costs a credit, because learning that a domain accepts everything is a result, and it's the one that decides which sequence a prospect goes into. An unknown row costs nothing. At $25 for 10,000 credits, you are charged for answers rather than for the file size.
Questions people ask
Should I send to catch-all addresses in cold outreach?
In a separate sequence at low volume, from a mailbox whose reputation you can afford to spend. Mix them into your main sequence and one unresolvable group sets the bounce rate for everything you send.
Does verification remove spam traps from a scraped list?
No, and this is the claim to be most suspicious of in this market. A pristine trap is indistinguishable from a real mailbox at the protocol level. Recycled traps can sometimes be flagged by heuristic, which is a guess wearing a label.
How often should a cold list be re-verified?
Before each campaign if the gap is more than three months. Job changes are what kills B2B data, and they happen continuously rather than on your schedule.
Try it on the file in front of you
100 free checks a month, no card. Addresses we could not get an answer on come back labeled as unknown, and those are not billed.