TL;DR: The waterfall is the right default for outbound at scale. Stack providers, pay only for what you find, maximize coverage. But every tool has a ceiling. The waterfall is excellent at telling you who returned a match and terrible at telling you how that data was sourced, how fresh it is, or whether the number actually connects. The tradeoff for the last few points of coverage is lower transparency, rising cost, and compliance risk that scales with your list. If you are dialing phones or operating in a regulated market, volume becomes a trap. What you put in the waterfall matters more than how many providers you stack.
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 is where the transparency ends.
When a secondary or tertiary provider in your waterfall hits a match, you still do not know:
The source. Was this scraped from a public header three years ago, or 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, where the person actually picked up?
Providers that own their infrastructure operate differently, because they can tell you exactly when a record was updated and how it was collected. If you only care about raw match rates, aggregators will often find more matches, because they are pulling from dozens of corners of the web. But a match is not a connection.
The cost of a marginal match
Waterfalls get expensive fast. Most teams set 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 available, records that have been scraped and resold across the web precisely because they are not 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.
For the full breakdown of how first-pass coverage controls that cost curve, see why a verified first layer changes the economics.
Three scenarios where the waterfall breaks
Compliance-auditable outreach
“Where did you get this number?” If a prospect, or a regulator, asks that question, “a waterfall provider found it” is not a legal defense. To stay safe, you need a clear line of sight to the data’s origin. Data from a proprietary database typically carries a higher level of compliance. In a waterfall, you are only as compliant as the weakest link in your chain.
The European gap
Most waterfall providers share the same secondary sources for EMEA. If one does not have a record, the others likely will not either, or they will return 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 to 3 times more mobile phone coverage than leading solo providers, more numbers do not always mean more conversations.
Meanwhile, Lusha focuses on the quality of the match, maintaining 86% phone accuracy and 98% email deliverability. If you are targeting the UK, DACH, or France, you need a primary source, not an echo chamber of aggregators.
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 large difference between a switchboard number that redirects to voicemail and a verified direct dial. If your BDRs spend 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 us be honest. If your only goal is to find the maximum number of emails possible and compliance is not a constraint for your industry, the waterfall wins. No contest. For 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 you sit in a regulated industry where “trust me” is not 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, do not trade legal safety for a few extra rows in a CSV.
Keep reading:
