Enrichment waterfalls

The enrichment waterfall is the foundational technique of GTM engineering. The premise: never trust a single data provider. Chain several in a fixed order, and take the first verified answer.

Why one provider is never enough

Every vendor has blind spots. Apollo is strong in some segments, ZoomInfo in others, Cognism on compliant European mobile numbers. Depend on one and you inherit its gaps. A waterfall turns that into strength: ask provider A first; if it returns a verified hit, stop and pay only for that; if it misses, fall through to B, then C.

Sequencing

Order providers by two factors: match rate for your segment, and cost per hit. Cheapest reliable source first, expensive specialist last. Build a separate waterfall per field type, because the best provider for emails is rarely the best for phone numbers.

Coverage and spend

Because most vendors bill on successful matches, a well-built waterfall pushes coverage toward complete without paying three times for one record. Track match rate and cost per enriched record as your two health metrics.

A waterfall is not about finding the best vendor. It is about never depending on one.

Cross-discipline note

A waterfall only enriches records you have decided are worth enriching. That decision, who counts as in-ICP, is an Operations question. Get the ICP definition right first, then let the waterfall do its work.