Chili Piper's enrichment today only supports a fixed list of named third-party providers. Every time a customer wants to use a provider that isn't already integrated, or their own custom-built data source, the only path is a one-off request for Chili Piper to build and maintain a dedicated integration for that specific vendor. This is a recurring pattern, not a one-off. Separate requests already on the board ask for Cognism, Amplemarket, Demandbase, Lead Magic, and HubSpot Breeze as enrichment sources, alongside this instance of a customer wanting to use their own custom-built scraping repository. Each is being treated as its own vendor-specific integration ask, but the underlying job to be done is the same: let admins point enrichment at whatever data source they're already using, named or custom, without waiting on Chili Piper to ship a bespoke connector for each one. There's a related, generic enrichment webhook that already calls out to "the connected provider," which suggests some form of bring-your-own-endpoint enrichment may exist in part today. If so, the gap may be less about building new capability and more about hardening and exposing that mechanism generally (documentation, payload flexibility, support for authentication schemes beyond a single fixed field), so any provider or custom system can be plugged in without a dedicated build each time. Why it matters: GTM teams increasingly mix named vendors with in-house data assets. Locking enrichment to a fixed, Chili Piper-maintained vendor list means every new provider or custom source is a queue item instead of a self-serve configuration, and it multiplies the maintenance burden as the vendor landscape keeps shifting.
