Customer.io's Neutral CDP Playbook
Colin Nederkoorn, founder & CEO at Customer.io, on the CDP layer in messaging
The real divide here is open routing versus bundled customer records. Customer.io is trying to sell a CDP as neutral plumbing that can take event data from an app or warehouse, reshape it, and send it to many downstream tools, including competing messaging products. The point is not just storing profiles inside one app, but acting as the pipe between systems so teams can swap destinations without rebuilding their tracking setup.
-
In this framing, a true CDP does three concrete jobs. It collects event data from apps and databases, lets teams filter or transform fields like removing PII, and forwards that data to other destinations such as warehouses, analytics tools, and messaging products. That is the Segment, mParticle, RudderStack model Colin is comparing against.
-
Klaviyo and Intercom are built first as application suites. Klaviyo grew as a vertically integrated ecommerce marketing stack with its own tracking snippet, CRM, email, SMS, and later CDP positioning. Intercom has increasingly centered its product around customer service. In both cases, the data layer primarily strengthens the home product bundle rather than serving as neutral infrastructure across rival tools.
-
That distinction matters because control of the data pipe changes switching costs. Segment became strategically powerful by sitting in application code and routing customer data to any destination, which made downstream apps easier to replace. Customer.io is copying that playbook at a smaller scale, using Data Pipelines to reduce dependence on outside CDPs and make Journeys easier to adopt later.
Going forward, more messaging and support platforms will keep adopting CDP language because the customer data layer is where retention and expansion economics concentrate. The winners will be split between open routers that become default infrastructure, and bundled suites that use data ownership to sell more adjacent products. Customer.io is clearly aiming for the open, interoperable side of that line.