Colin Nederkoorn, CEO and founder of Customer.io, a customer engagement platform offering marketing automation and data & analytics solutions, discusses the company’s CDP platform and potential new additions, the benefits and tradeoffs between the all-in-one and platform approaches to building marketing automation tools, the existing and potential customer base and how their preferences change over time, and Customer.io's positioning in the market amidst players such as Segment, mParticle, Klaviyo, and Intercom. He highlights the company's vision for the road ahead in five years.
The following interview was conducted by Sacra—June 2023
Background
Colin Nederkoorn is the founder & CEO at Customer.io. We talked to Colin to better understand the trade-offs and upsides of the platform vs. all-in-one approaches to building marketing automation tools, Customer.io's newly launched customer data platform (CDP), and Customer.io's new positioning amid a market of many customer data products, including Segment, mParticle, Rudderstack, Klaviyo, Intercom, Amplitude, and more.
Questions
Tell us about the decision to build a CDP and take a platform approach to building out Customer.io. What's the problem statement from the customer perspective?
Can you talk a little about taking a platform approach vs. all-in-one? How do you think about this specific approach that you've chosen?
How do you think about interoperability with other SaaS tools? What does it mean to "own" the CDP layer, especially if Data Pipelines works seamlessly with any SaaS? Is it more important that Customer.io "owns" the CDP, or that Segment doesn't and that the CDP is commoditized? I would love to hear, because Customer.io predated the modern CDP and Segment. Right?
What are the benefits of vertical integration that customers get from bringing everything onto the Customer.io platform?
How does go-to-market (GTM) change with a platform approach? What's it look like now vs. what it will need to become an as-you-go multi-product? How do you see the customer journey in terms of adopting the Customer.io stack as it grows?
Right now, the Customer.io platform consists of Journeys (marketing automation) and Data Pipelines (CDP). How do you think about what products you want to add and in what order? How do more products drive more customer value and lock-in?
Do you see Journeys as the primary revenue driver with Data Pipelines as more of a loss leader? Are you imagining any new products as revenue drivers? How are you thinking about revenue mix and pricing for individual products and bundles?
In our last conversation, you mentioned Customer.io's customer base is mainly SMB and customers churn as they go enterprise. How has that moment of churn changed over time? How do you expect the platform approach to affect churn at the high end?
CDP has got a little confusing as a term. It might include ETL, reverse ETL, data enrichment etc. How are you defining CDP at Customer.io? Where do you see the opportunities to build a feature-rich experience at the CDP layer?
Customer.io Journeys needs a low latency CDP to make sure messages are sent to users in real-time based on actions they take in the app. Is speed a differentiator among CDPs? If so, does Customer.io intend to compete on that dimension?
Is data warehouse sync part of CDP or a separate product? How do you see the relationship between CDP and "modern data stack" in terms of data infrastructure to power things like Journeys? Is the data warehouse sync a differentiator for Customer.io versus competitors like Braze and Iterable?
How do you position Customer.io's CDP against standalone products like Segment, mParticle and Rudderstack and the CDPs of other products like Klaviyo, Intercom and Amplitude. Do you intend to win based on vertical integration with Customer.io Journeys? How about price, feature differentiation, and number of integrations?
Klaviyo launched its CDP as part of its enterprise platform. Are you primarily thinking about Data Pipelines as driving enterprise lock-in and all-in-one? Do you have a downmarket strategy for Data Pipelines? How do you think about what Klaviyo and Intercom are doing?
There’s a common pitfall of going multi-product by selling into multiple buyers. As you launch more products, what do you see as the boundary conditions that define what Customer.io should and wants to be doing vs. what it won't do?
Intercom used to have a platform approach, with marketing automation and support built on top of a CRM. It's now decided to focus 100% on customer service. Why is now the right time to try this platform approach and how will Customer.io succeed where Intercom decided to pull back?
Where do you imagine that Customer.io can get the most leverage out of AI? How are you thinking about AI at Customer.io re automating writing messages, creating segments, enriching data etc.?
To the extent that Customer.io helps enable a specific PLG sales motion for its customers, how concerned are you that the way that customers buy software in general will change with AI? What risk is there that, e.g., marketing automation becomes a lot less effective as a result of a dramatic rise in spam and that tools like Customer.io lose their alpha?
If everything goes right for Customer.io in five years, what does it become? How do you see the world change as a result?
Contact us
Gain access to all industry hubs, market maps, research tools, and more
Get a demo
By using this site, you agree to allow SPEEDA Edge and our partners to use cookies for analytics and personalization. Visit our privacy policy for more information about our data collection practices.