Klaviyo Reclaiming the Customer Graph
Klaviyo: the $665M/year HubSpot for ecommerce
Launching an in house CDP is really a fight over who owns the customer graph, not just who sends the next email. Once Segment became the system collecting events and deciding which tools received them, Klaviyo and peers became easier to swap out. Building their own CDPs lets them pull event collection, profile building, segmentation, and campaign execution back into one stack, which improves retention and creates new products to sell.
-
Segment’s core advantage was that one Javascript snippet could route the same customer event stream to many downstream apps. That turned messaging tools into replaceable destinations, because the historical profile and event pipeline no longer lived inside the email platform itself.
-
Klaviyo’s original edge came from storing rich ecommerce behavior in its own profile model, so marketers could build segments and flows without exporting CSVs. A standalone CDP weakened that edge by moving the source of truth outside Klaviyo and into a neutral router.
-
There are two versions of CDP emerging. Segment style CDPs are open routers that send data anywhere. Klaviyo style CDPs are more tightly tied to the app suite, which makes them strong for all in one workflows and enterprise expansion, even if they are less neutral than pure play CDPs.
The market is heading toward bundled systems of record where messaging, analytics, support, and AI all sit on top of the same profile store. The winners will be the platforms that make that profile both easy to use inside their own products and useful enough that customers stop paying a separate vendor to hold the center of the stack.