Databricks is selling a lakehouse-native customer data product. Salesforce and HubSpot are selling customer data inside the CRM the enterprise already owns. The standalone CDP is being squeezed from both sides, and the renewal cycle is where that squeeze becomes a budget line.
The Ecommerce Times called the trend earlier this year. The category that spent a decade selling itself as the neutral hub for customer data is being absorbed into the platforms on either side of it. From below, the warehouse and lakehouse vendors argue the data already lives with them, so the activation layer should too. From above, the CRM and marketing suites argue the workflows already live with them, so the profile store should too. Both are right in different rooms of the same building.
That leaves the standalone CDP defending a middle that used to be the whole point. When the warehouse can resolve identity and the CRM can trigger a journey, the specialist tool in between has to justify itself on something other than "we sit in the middle."
The renewal question has changed
For three years the enterprise CDP conversation was a product bake-off. Which vendor had the better identity graph. Whose connectors were richer. Whose consent management was more mature. Procurement wrote scorecards. Analysts ranked quadrants. Marketing signed the contract and IT inherited the integration.
That question is now the wrong question. The vendors on the shortlist are converging on similar capability, and the capability itself is being commoditised by the platforms on either flank. Asking which CDP wins at renewal is like asking which fax machine to buy in 2005. The answer might be correct and still miss the point.
The better question is who owns the customer-data outcome across the warehouse, the CRM, the contact centre and the campaign. That is not a product question. Product questions have product answers. Ownership questions have partner answers.
Why the two-sided squeeze matters for accountability
The reason the squeeze matters is not architectural. It is accountable. When customer data moves through a warehouse, into a CDP, out to a CRM, into a contact centre platform, and back into a marketing suite, every handoff is a place where the outcome can be dropped and no single vendor is on the hook. The enterprise ends up with five invoices and no owner.
Vendors know this. That is why Optimove has been pushing agentic marketing in recent days, why Zeotap keeps expanding into adjacent customer data territory, and why Databricks is positioning CustomerLake as the place all of it should collapse into. Every one of them is making the same pitch in different words. Buy more from us and you will have fewer seams to manage.
That pitch is half right. Fewer seams is the correct goal. Buying more from a single product vendor is not the only way to get there, and often not the best way, because the seams that hurt most are not inside one product category. They are between marketing and the contact centre. Between the campaign and the fulfilment. Between the data platform and the agent taking the call.
What enterprises should actually do at renewal
Stop running the CDP evaluation as a standalone procurement. Run it as one input into a broader question about who is accountable for the customer-data outcome across every channel the enterprise touches.
If the answer is "our warehouse vendor," accept the consequences. The warehouse becomes the system of record and the CRM becomes a workflow layer on top of it. If the answer is "our CRM suite," accept those consequences too. The suite eats the CDP and the warehouse becomes a downstream reporting target. Both are defensible. Neither is free.
The third answer, and the one most enterprises actually need, is a partner who owns the outcome across all of it. Warehouse, CRM, contact centre, campaign, fulfilment, and the data flowing between them. One accountable programme rather than five product renewals negotiated in separate rooms by separate teams.
That is the renewal conversation worth having this quarter. Not which CDP wins. Who owns the customer.