An enrichment waterfall is a sequence of data providers tried in order until the first verified field is found. Email and mobile are the usual stop conditions. Later providers in the chain do not need to run for that field once it is filled.
It is a pattern. SurroundR uses it on LinkedIn capture. Clay uses designed waterfalls in an ops workspace. HubSpot is where SurroundR writes the result. The integrations hub is the destination-plus-waterfall page for the product. This glossary owns the term. It will not restate that hub.
The pattern, in one pass
- You have a person (in SurroundR: the LinkedIn profile you are viewing).
- Provider 1 is asked for a verified email or mobile.
- If verified, stop that field. If not, try provider 2.
- Repeat until you have a hit or the list is exhausted.
- Write the fields into the CRM. Dedup so you update the human you already had.
Stop conditions are per field, not "the person is done." Email can hit on provider 2 while mobile keeps walking. Public SurroundR copy talks about first verified email and mobile on the same capture save. Billing behavior (what a credit is, what a miss costs) lives on the enrichment waterfall product page. Do not treat this post as the credit contract.
SurroundR's public description: 20+ premium data vendors, first verified hit, write to HubSpot, about two seconds with the capture click. Managed round robin or bring-your-own keys. Free is 100 credits per month with no card. Read the product page for how those modes differ. This glossary will not reprint the settings UI.
What this page will not copy from /integrations
Provider grids, BYO versus managed tone, and HubSpot as the one destination are already on integrations. At the overlap: SurroundR's waterfall is how enrichment is executed inside capture. The hub is how the stack is explained to buyers. Link, do not duplicate.
Named enrichment suppliers do not belong in this prose. Partner pages exist for keys. Public waterfall copy stays "20+ premium data vendors."
If you need OAuth, objects, and every HubSpot tier, that is the HubSpot integration page. A waterfall that cannot write to HubSpot is a demo, not a CRM motion.
Clay and orchestration (different job)
Clay is built for ops-led data orchestration: you design waterfalls and pipelines in a workspace, then push to many destinations. SurroundR is built for the rep already on LinkedIn: one click, HubSpot is the centre of gravity.
Honest stack: Clay for list-scale ops waterfalls, SurroundR for in-feed capture and HubSpot writeback. Overlap is smaller than the category names suggest. The Clay vs SurroundR page is the compare. Use it instead of turning this glossary into a vs page.
A waterfall in Clay and a waterfall in SurroundR share the sequencing idea. They do not share the surface (sheet versus feed) or the default CRM depth.
If the buying question is "we already paid for a data contract," BYO keys on the enrichment product page is the SurroundR answer. If the buying question is "we want to design 14-step tables," that is Clay. Both can be true in one company. They are still different jobs.
Why teams want a waterfall
One vendor misses titles, regions, or mobiles. A chain raises hit rate without five browser profiles. It still misses. Quote your own HubSpot fill rates in a review, not a number from this page.
A waterfall is not a guarantee. It is a way to fail over without the rep becoming the router. If every provider misses, HubSpot still gets the capture (name, title, company, LinkedIn URL). Reachability is incomplete. That is honest. Recapture later if the person is still in play. Nightly rewrite of the whole portal is not what SurroundR claims.
Hygiene still matters: results must land on standard properties, and capture must match email, phone, or LinkedIn URL. See what is data enrichment for the job versus the pattern, and CRM data hygiene for RevOps for the operating checklist.
Inbound uses the same waterfall. There is not a second inbound chain. The difference is when you click: inbound lead enrichment in HubSpot.
What a miss looks like (and what to do)
A miss is not a product incident. It is a person HubSpot now has, without a verified email or mobile from this run. The capture still wrote name, title, company, and LinkedIn URL. The seller can still DM. They cannot sequence an empty email field.
Next actions that stay honest:
- Work them on LinkedIn and recapture later
- Use a channel you already have (if a form email exists, the match should have kept it)
- Do not open five finder tabs "just this once" as the new process. That is the problem the waterfall was meant to remove.
Order of providers matters in the abstract: a cheaper or faster source first, a specialist later. SurroundR's managed round robin is one opinionated order. BYO keys let you pin the order to contracts you already pay. Neither mode belongs as a second integrations article here. Open the product page and the hub.
Short version
An enrichment waterfall tries providers in order and stops at the first verified email or mobile. SurroundR runs that on LinkedIn capture into HubSpot. Mechanics, credits, and keys: enrichment product page and integrations hub. Ops-designed waterfalls in a workspace: Clay compare. Install SurroundR if the waterfall you want is the one that fires on the profile you are already viewing.
