Waterfall enrichment is a method where multiple B2B data providers are tried in sequence for each record: if the first provider can't produce a verified email or phone number, the next one is attempted, until there's a hit or the chain ends. The name comes from the shape — a request cascading down provider after provider until something catches it.
It exists because of one uncomfortable fact about B2B data: no single provider covers everyone. Every database has gaps by geography, seniority, industry and recency. A single-provider setup means every gap is a lead you found but can't contact. A waterfall turns several partial databases into one good one.
We're not summarizing other people's blog posts here — every contact reveal on Leaderra runs through a waterfall we built and re-tune on our own money. This is the mechanics, honestly explained.
How does waterfall enrichment work, step by step?
- A record enters the chain — usually a name plus a company or domain, from prospecting, a form fill, or a CSV.
- Provider one is queried. If it returns the contact data you need, the chain stops.
- On a miss, the next provider is tried — each with different coverage strengths, so the second catches some of what the first dropped.
- The result is verified — the email is bounce-checked, the phone line-type checked — before it counts as a hit. This step separates good waterfalls from expensive ones.
- Only the verified hit is kept (and paid for). In a well-built chain, a miss costs nothing.
The compounding is the point: if provider A finds 60% of your records and provider B finds 60% of A's misses, the pair covers 84%. Add a third and a fallback aggregator and match rates that no single vendor can sell you become routine.
Why not just use one big database?
Three reasons, in the order they cost you money:
- Coverage gaps become silent losses. Every un-enrichable lead was paid for upstream — in ad spend, list building, or scoring — and dies for want of an email.
- Bounce rates kill campaigns. A single stale database means sending to old addresses; past a few percent bounces, your deliverability (and domain reputation) degrades. Verification inside the waterfall is what keeps sends safe.
- You inherit one vendor's pricing model. With a waterfall, providers become interchangeable parts — when one degrades or reprices (it happens to all of them), records route around it.
Static vs smart waterfalls — the part most explanations skip
A static waterfall runs the same provider order for every record. It's better than one provider, but it leaks: it calls expensive providers on records a cheap one would have caught, and wastes calls on providers that rarely hit a given segment.
A smart waterfall treats the order as a decision, per record:
- Segment-aware routing — a US SaaS VP and a German manufacturing owner have different best-first providers.
- Skip logic — providers with near-zero historical hit rates on a segment aren't called at all.
- Hit-rate memory — every attempt updates per-segment stats, so this month's ordering beats last month's.
Two teams can run the same providers and land hit rates 20 points apart. The ordering logic, not the provider list, is the difference — which is why we treat ours as the product and the providers as parts. The full breakdown of which providers do what is in our provider-by-provider comparison.
Should you build one, rent one, or buy the output?
| Path | Right when | The catch |
|---|---|---|
| Build your own | You want per-segment routing, your own provider contracts, and hit-rate data you keep | Real engineering + ongoing maintenance; provider APIs change |
| Rent a waterfall (FullEnrich-style aggregators, Clay tables) | Engineering time is scarcer than margin | Static ordering, same for everyone; per-attempt costs |
| Buy the output (packaged data layer) | You want verified, scored records without owning any plumbing | Less composable — you adopt the vendor's pipeline |
We did all three at different stages. Today we run our own chain, keep a rented aggregator as the final fallback, and sell the output as the packaged path — one credit wallet, app, API and MCP, never charged on a miss. Teams that build anyway use our waterfall endpoint as a step inside their own chain.
FAQ
What is waterfall enrichment in simple terms?
Trying several B2B data providers one after another for each contact you need, keeping the first verified result. Like calling three suppliers for a part: you stop at the first one who actually has it, and you only pay the one who delivers.
What's the difference between waterfall enrichment and data enrichment?
Data enrichment is the general practice of adding information (emails, phones, firmographics) to a record. Waterfall enrichment is a specific technique for doing it: sequencing multiple providers to maximize match rate, instead of relying on one source.
How many providers should a waterfall have?
Three to five covers most of the curve: a cheap high-hit first hop, a broad database second, a specialist third, and one aggregator as the final net. Beyond that, added providers mostly add latency — better returns come from smarter ordering than from a longer chain.
Does waterfall enrichment guarantee valid emails?
No — which is why verification must sit inside the chain, not after it. A provider returning an address is not the same as the address being deliverable. In our chain nothing counts as a hit (or gets charged) until it passes verification.
Is waterfall enrichment expensive?
Run naively, it can be — every provider call costs something. Run well, it's the cheapest per delivered record: our production chain lands a verified email + mobile at roughly $0.08 per completed record, precisely because cheap providers go first and misses cost nothing.