If you’re managing outbound at scale, you’re likely using a waterfall. And it’s the right default.
Instead of relying on one provider to have every mobile number and email on earth, you stack them. If Provider A doesn’t have the data, the system automatically asks Provider B, then Provider C.
On paper, it’s the perfect hedge. You maximize your coverage and only pay for what you find.
But every tool has structural limits. When you move from finding any data to building a predictable revenue engine, the waterfall starts to show its cracks. The tradeoff for that extra 5% of coverage is often a lack of transparency, rising costs, and compliance risks that scale as fast as your list.
To build a pipeline you can actually trust, you need to know what the waterfall is hiding.
The hidden tradeoff: Knowing the “Who” but not the “How”
Platforms like Clay are excellent at orchestration. They show you exactly which provider returned a result. But that’s where the transparency ends.
When a secondary or tertiary provider in your waterfall hits a match, you still don’t know:
- The source: Was this scraped from a public header three years ago, or is it sourced from a private, verified database?
- The freshness: When was this specific record last dialed or delivered?
- The verification: Is “verified” a technical status (like an SMTP check) or a functional one (the person actually picked up)?
Providers like Lusha operate differently because they own the infrastructure. This means they can tell you exactly when a record was updated and how it was collected.
If you only care about raw match rates, or the total hits at the end of a sheet, aggregators will often find more matches. They’re pulling from dozens of corners of the web. But a match isn’t a connection.
The cost of a marginal match
Waterfalls get expensive fast. Most teams set up their logic to keep hunting until they find a result.
The problem is that each extra provider adds marginal coverage at full credit cost. You might pay Provider A for 60% of your list, then pay a premium to Provider D to find the remaining 3%. Often, that 3% is the lowest quality data—records that have been scraped and resold across the web because they aren’t held in a primary, high-integrity database.
You end up overpaying for the scraps of the internet, filling your CRM with records that have no compliance guarantees and low deliverability.
Three scenarios where the waterfall breaks
1. Compliance-auditable outreach
“Where did you get this number?”
If a prospect, or a regulator, asks that question, “a waterfall provider found it” isn’t a legal defense. To stay safe, you need a clear line of sight to the data’s origin.
When you use data from a proprietary database, there’s typically a higher level of compliance. In a waterfall, you’re often only as compliant as the weakest link in your chain.
2. The European gap
Most waterfall providers share the same secondary sources for EMEA. If one doesn’t have it, the others likely won’t either—or they’ll provide the same unverified office ghost-line.
According to Clay’s own data test of 9,806 mobile numbers, only 23% qualified as verified and high-propensity across all regions. While Clay states their waterfall delivers “2–3x more mobile phone coverage than leading solo providers,” more numbers don’t always mean more conversations.
Meanwhile, Lusha focuses on the quality of the match, maintaining 85% phone accuracy and 98% email deliverability.
If you’re targeting the UK, DACH, or France, you need a primary source, not an echo chamber of aggregators.
3. Direct dials that actually pick up
A waterfall returns a number to fill a field. Providers with proprietary databases return the kind of number that converts.
There is a massive difference between a switchboard number that redirects to a voicemail and a verified direct dial. If your BDRs are spending 40% of their day navigating phone trees, your “high coverage” waterfall is actually costing you money in lost labor.
When the waterfall actually wins
Let’s be honest: if your only goal is to find the maximum number of emails possible and compliance isn’t a constraint for your industry, the waterfall wins. No contest.
If you are doing high-volume, low-stakes email blasts, stacking 15 providers will always yield a longer list than using a proprietary database alone.
But if you are picking up the phone, or if you sit in a regulated industry where “trust me” isn’t a data privacy policy, volume is a trap.
Strategy over stacking
The waterfall is a tool, not a strategy. What you put in the waterfall matters more than how many providers you stack.
So, start with what you have. Use cheap, broad sources for initial research if you must, but verify them against a primary database.
If compliance and connect rates matter to your revenue goals, don’t trade legal safety for a few extra rows in a CSV.
Keep reading:
