Customer.io's Neutral CDP Strategy
Colin Nederkoorn, founder & CEO at Customer.io, on the CDP layer in messaging
This is a wedge strategy, not just a product feature. By making its CDP send data into Braze, Iterable, and other enterprise messaging stacks, Customer.io can get inside large accounts before ripping out the incumbent. The team that owns event plumbing can adopt Data Pipelines first, route product and warehouse data to every downstream tool, and then judge Customer.io on speed, usability, and cost before considering Journeys.
-
Customer.io defines CDP in the broad enterprise sense, ingest data from apps, APIs, databases, and warehouses, filter or reshape it, then fan it out to downstream tools. That makes interoperability with competing engagement platforms a core part of the product, not a side integration.
-
This open approach lowers adoption risk for enterprises. Earlier, Customer.io often told prospects to implement Segment first so their data stayed portable if they switched messaging vendors. Data Pipelines internalizes that same benefit while removing an extra hop between customer data and time sensitive messages.
-
The upmarket logic is tangible in the business. Customer.io said in 2023 it was doubling $100K plus enterprise deals each year, and by September 2025 it had reached $100M ARR after growing from $50M ARR in 2023 and $78M ARR at the end of 2024. The CDP layer is part of how it turns enterprise evaluation into expansion.
Going forward, the company is trying to become the neutral data and workflow layer for product led companies. If Data Pipelines keeps winning the initial integration decision, Customer.io can expand from being one messaging tool into the system that sits between product data, warehouses, analytics, and outbound engagement across the stack.