Hightouch and Databricks now stand at the center of the debate over where customer data platforms are headed, according to a new CMSWire analysis examining the two companies' intertwined trajectories.

The core question the analysis raises is one every martech practitioner should be asking: do brands still need a standalone CDP, or does the warehouse — or lakehouse — now do that job?

What is Hightouch's actual position in this story?

Hightouch built its business on a simple premise: enterprises already hold their customer data in a warehouse, so why copy it into a separate CDP datastore? The company's "composable CDP" model leaves data in place — in Snowflake, BigQuery or Databricks — and layers modeling, audience segmentation and activation on top.

Databricks, for its part, has pushed the same argument from the infrastructure side. Its lakehouse platform positions itself as the single home for structured and unstructured data, with lakehouse Federation, Delta Sharing and its Unity Catalog governance layer doing work that once required dedicated middleware.

The CMSWire piece frames the relationship between the two as a signal: when the biggest names in data infrastructure and the loudest voice in composable CDP land converge on the same thesis, the traditional packaged CDP category loses its default status.

What changes for practitioners?

For marketing operations and data teams, the implications cut in several directions:

• Procurement shifts. Teams evaluating CDPs increasingly compare them against a warehouse-native build, not just against each other.
• The talent question gets sharper. Composable approaches demand data engineering skills that many marketing teams still lack.
• Governance moves upstream. Identity resolution and consent logic increasingly live in the warehouse layer, not in a marketing tool.
• Integration depth matters more than feature checklists. The quality of a vendor's connectors to activation channels — ads platforms, email, personalization — decides real-world value.

Why does the Databricks connection matter specifically?

Databricks has spent years courting marketing and customer-data workloads that traditionally sat in CDPs and marketing clouds. Its acquisition activity and product investments in real-time serving, streaming and AI/ML tooling have made the lakehouse a credible staging ground for customer 360 initiatives.

Hightouch's alignment with that ecosystem signals where its bets lie: the vendor wins when the warehouse wins. That contrasts with packaged CDP vendors, whose business depends on pulling data out of the warehouse and into their own storage.

Readers should note a limitation of this summary: the source item is a headline-level syndication feed entry, and CMSWire's full analysis — linked from the feed — contains the specific figures, product versions and executive commentary behind the argument. This rewrite confines itself to what the source headline and attribution establish: that CMSWire identifies Hightouch and Databricks together as the directional signal for the CDP category.

What should buyers watch next?

The direction of travel suggests a few checkpoints for anyone planning a customer data stack over the coming budget cycles:

• Whether Databricks deepens first-party support for activation workflows, or keeps partnering with composable vendors.
• Whether packaged CDPs respond by offering warehouse-native deployment modes — several already have.
• Whether Hightouch expands beyond activation into deeper identity and measurement capabilities.

The category is not disappearing. But the CMSWire analysis, as signaled by its framing, treats Hightouch and Databricks as evidence that the center of gravity in customer data has moved from the marketing stack into the data stack — and that marketers who ignore that shift risk buying into an architecture the market is leaving behind.