Waterfall Enrichment: Why Verification Is the Other Half

What is waterfall enrichment?

Enrichment means filling in the fields you are missing on a contact or account: work email, phone, job title, company size, tech used. No single data provider has every field for every person. Each one is strong in some regions, industries or company sizes and thin in others.

A waterfall solves that by asking providers in order. You send the contact to provider A. If A returns an email, you stop. If not, you ask provider B, then C. You only pay for the lookups you run, and you end up with more filled fields than any one source would give you.

The idea is simple. The decisions inside it are where teams get it right or wrong: which fields to enrich, which provider goes first, what counts as a match, and what you do with the answer once you have it.

Found is not the same as deliverable

Here is the part most enrichment guides skip. A provider returning an email address does not mean a mailbox exists behind it. Some addresses are guessed from a pattern, such as first.last at the company domain. Some were right a year ago and the person has since left. Some sit on catch-all domains that accept every address at the door and bounce or discard later.

So a waterfall that stops at the first answer is optimised for coverage, not for sending. If you load those results straight into a sequence, you send to addresses nobody checked. Hard bounces follow. Mailbox providers read a high bounce rate as a sign that a sender does not maintain its list, and that hurts inbox placement for every email you send afterwards, including the ones to good addresses.

That is why verification is the other half of the job. Enrichment answers "can we find this person?" Verification answers "will this address accept mail today?" You need both answers before a contact goes anywhere near a send.

How should a waterfall actually run?

A workable waterfall for a small team has six steps. None of them needs a data engineer, but each one needs a decision written down so the process runs the same way every time.

• Pick the fields that change a decision. Work email and job title usually matter. Ten extra firmographic fields you never filter on only cost money.
• Order providers by fit, then by cost. Put the provider that is strongest for your market first, and the cheapest broad source after it.
• Set a match rule. Match on full name plus company domain, not name alone, so you do not enrich the wrong person with the same name.
• Record where each field came from. When a provider's answers start bouncing, you can see it and move it down the order.
• Send every found email to verification before it is saved as usable.
• Keep the unverified and risky results in a separate list. Do not delete them, but do not send to them either.

Verify after enrichment, then again before every send

Verification is not a one-time filter. Addresses decay. People change jobs, companies change domains, and a list that was clean when you built it drifts over the weeks it takes to work through a sequence. We check at three points, and each one catches something different.

What the bounce numbers show

In our own campaigns, list verification and suppression cut the hard bounce rate from 11.17% to 0.43%. Nothing about the copy or the offer changed. The difference was which addresses we were willing to send to.

For a B2B SaaS client in fleet safety, hard bounces fell from 1,637 on the first send to 75 on the third send of the same campaign wave, with bounce suppression between sends. Unsubscribes fell from 76 to 8 over the same sends, and the unique click rate rose from 0.55% to 1.45%. We cannot say suppression alone caused every one of those changes. We can say the list got cleaner each round because addresses that failed once were never sent to again.

Across client programs and our own marketing, we verified 30,000+ contacts before sending in 2026. The habit matters more than any single tool: nothing is sent to an address that has not passed a check.

Suppression is the step between sends

A suppression list is the set of addresses you must never email again in a given program. It grows with every send. If it lives in one person's spreadsheet, it will be missed the day that person is out. It should be checked before every send, by the system, every time.

At minimum, suppress these:

• Hard bounces from any previous send.
• Anyone who unsubscribed or asked not to be contacted.
• Replies that said no, so they do not get the next follow-up.
• Current customers and open deals, unless the campaign is meant for them.
• Competitors and partners you do not want in a cold sequence.

How to choose data enrichment tools

Clay is the tool most people link with waterfalls. According to Bloomberry's analysis of 1,000 GTM engineering job postings, Clay appears in 57% of them and Apollo in 29%. That tells you what employers use. It does not tell you what your list needs.

Judge enrichment tools on one number you can compute yourself: cost per deliverable contact. Take your total enrichment and verification spend for a batch and divide it by the number of contacts that passed verification. A cheap provider with many invalid results can cost more per usable contact than a pricier one. Run the same sample of your real target accounts through two or three providers and compare that number, not the coverage claim on the sales page.

Also ask where verification sits. Some tools include it, some leave it to a separate service. Either is fine. What is not fine is a flow where nobody can point to the step that checks the address before it is sent.