Anti-Fragile take
No single enrichment provider covers everything. Waterfall enrichment tries provider A, then B, then C, stopping when a field is filled and validated. It is slower and more expensive per record than a single call, but the output is dramatically more complete.
We waterfall with cost caps: cheap providers first, expensive ones only on high-value accounts or after cheap ones fail.
Why it matters
Single-provider enrichment creates confident gaps. Waterfalls surface what you actually know versus what you are guessing.
How we build it
Ordered provider chains per field type, validation after each step, coverage dashboards, and cost-per-record tracking.