Apps Building CDPs to Own Customers
Salesforce, Amplitude, and the fat data layer in B2B SaaS
Launching a CDP is really a move to own the customer record before a neutral data router does. When Amplitude or Klaviyo gets the event stream, identity graph, and profile into its own stack, the customer no longer just buys analytics or email. They buy the plumbing that feeds those products, which lowers onboarding work, makes adjacent upsells easier, and raises the cost of swapping vendors later.
-
Segment changed the balance of power by turning customer data into portable infrastructure. One snippet could feed many tools, which made downstream apps more interchangeable. That is why destination apps started adding CDP features, and why Twilio layered Engage on top of Segment to capture more workflow revenue itself.
-
Klaviyo’s version is especially about collapsing ecommerce marketing into one system. A merchant can collect shopper events, unify profiles, build segments, and trigger email or SMS without standing up a separate CDP first. That creates faster time to value and gives Klaviyo more products to sell into the same account.
-
These CDPs are not all equally open. The evidence points to a split between broader routing products and more vertically integrated systems. Amplitude is closer to a true cross tool data layer, while Klaviyo’s CDP is designed mainly to make Klaviyo’s own marketing apps work better and stickier for enterprise buyers.
The direction of travel is toward suites that combine system of record, activation, and warehouse connectivity. As Snowflake and other warehouses become the long term home for customer data, the winners will be the apps that can both plug into that warehouse cleanly and still offer enough native data plumbing that customers do not need a separate CDP for everyday work.