## Why composable CDPs benefit CRM teams

### Author

Dylan Flye  
SVP, Sales

### Table of contents

- [So, what exactly is Hightouch’s stance?](https://www.simon.ai/blog-posts/why-composable-cdps-benefit-crm-teams#so-what-exactly-is-hightouchs-stance)
- [1. Auto-optimizing experiences](https://www.simon.ai/blog-posts/why-composable-cdps-benefit-crm-teams#1-auto-optimizing-experiences)
- [2. Data availability](https://www.simon.ai/blog-posts/why-composable-cdps-benefit-crm-teams#2-data-availability)
- [3. Identity management](https://www.simon.ai/blog-posts/why-composable-cdps-benefit-crm-teams#3-identity-management)
- [Why composability matters](https://www.simon.ai/blog-posts/why-composable-cdps-benefit-crm-teams#why-composability-matters)

As I wrote in [an earlier article](/content/resources/cdp-schism-salesforce-vs-snowflake/index.html), the benefits of composability have often been expressed in terms of the architectural principles of data management and how this benefits data teams.

While these benefits are important, I’d argue they’re not the primary benefits of composability.

Businesses ultimately invest in CDPs to drive marketing and customer experience performance metrics – improving customer acquisition efficiency, increasing customer lifetime value, driving up purchase frequency, etc.

Expressing the benefits of composability purely in architectural terms has limited conversation around how it benefits the above business outcomes expected of a CDP and the customer marketing teams that invest in the process.

Martin Kihn at Salesforce, the way less cool version of Don Cheadle, recently published [Salesforce’s future vision for their Data Cloud](https://www.linkedin.com/feed/update/urn:li:activity:7150975877315485696/), a term they now apparently use interchangeably with CDP.

The Customer Data Platform is 10 years old -- almost 11. About 1/3 of Taylor Swift's lifetime. What comes next?

Here are five Swift-free predictions for the near future of the CDP:

1. **CDPs become something you can talk to**  
   GenAI and enterprise software have two directions: GenAI goes into the tools (making them work better) and the tools come to GenAI (giving the large language models special features). That first category is already upon us, as every class of software suddenly gets easier to use: we've gone from SQL power user to SQL dilettante to drag-and-dropper to simply chatting to the machine in a drawl. In other words, the CDP is learning our language, literally.

2. **CDPs turn into a tool that helps the CIO**  
   We know that CDPs began life as the metier for marketers, primarily in retail; facing pressured margins and a very data-organized, analytical, cloud-based (ahem) competitor named you-know-who. Some years ago, other parts of teams touching CX discovered it: service, commerce, sales, etc. After all, the "C" in CDP is the same as the "C" in CX, right? Next step is a strategic elevation into a different "C," the C-suite, as the unified profile becomes an asset for long-range planning.

3. **CDPs gear up for the unstructured data deluge**  
   CDPs like [Salesforce](https://www.linkedin.com/company/salesforce?trk=public_post_embed-text) Data Cloud ingest data in any form and land it in a lake, or connect to cloud warehouses like Snowflake minus ETL. What follows is a harmonization step that makes a unified profile possible (mapping like fields to like). AI and GenAI now make it much easier to get value from unstructured data like text (especially), images, and other media. Expect CDPs to support vector DBs, embeddings, semantic retrieval, etc.

4. **Standalone CDPs scale down in scope and number**  
   Don't call it a shake-out: we'll say that CDPs not part of a larger platform or ecosystem environment will have to make a sharper case for themselves in the mid- and large-enterprise. Some go down-market to the SMBs and some verticalize, hyper-targeting a specific industry (like health care), geographic region (like France), or use case (like fan club management -- just making this up; not really; already patented).

5. **The "C" in CDP becomes less literal**  
   Customer data is difficult to manage -- which gave CDPs their initial focus. We already see Data Cloud customers building profiles of things that are not people: products, brands, store locations, connected devices. As the users for CDPs expand beyond the original hard-working digital marketers, so the data objects handled extend as far as CX relevance can dream, from bods to bots.

## So, what exactly is Hightouch’s stance?

Hightouch was founded by a group of former Segment engineers who attached Hightouch’s vision to data warehouse centricity and the #moderndatastack. It’s also worth mentioning that Segment seemed to miss this data-warehouse-centric trend and now Twilio’s business is feeling the pressure.

I agree with just about everything Hightouch has to say about traditional CDPs. Traditional CDPs predominately come from an era of SaaS where the application wants to become the source of truth for whatever data it controls.

Salesforce pioneered this approach by creating a cloud for everything that stores an authoritative copy of your sales, marketing, advertising, support, and [insert data for any use case here] data. **Data Cloud is now their response to the problems this approach creates.**

This approach means that the data marketing teams are working with is often siloed from investments being made on the data side for other use cases.

A great example of this is that enterprises will often have analytics and data science teams interpreting data to gather insights and that same work is rarely being used or seems to seldom be available to support marketing use cases.

At Simon, we’ve always embraced data warehouse centricity and the myriad benefits centralizing data within a data warehouse creates for a business, beyond CDP use cases.

Hightouch is a product built by engineers for engineers (like Segment) and so the vision and product marketing around it have always focused on the benefits for engineers. My goal here is to translate some of these benefits into the things that matter most for the teams that use data to power the customer experience.

If the Cloud Data Warehouse is the center of your data strategy, and the CDP is fully connected to your CDW, there are many benefits for customer marketing teams beyond the benefits for data teams that Hightouch and others have expressed.

### 1. Auto-optimizing experiences

If the CDP is fully connected to all customer data — think ML models trained on historical data, engagement data, real-time data from web/app, etc., — the CDP can auto-optimize the customer experience.

Why is this different in a composable approach? The answer is simple: the optimization is driven by the highest quality dataset (i.e., the complete customer profile).

When real-time and historical data come from different sources and the CDP is organizing this (a classic traditional CDP use case), ML models may take into account something like the customer’s historical lifetime value, but it cannot fully incorporate real-time data in training the models that predict what experience to serve the customer.

### 2. Data availability

One of the things I hear most often from CRM teams is that they spend a significant amount of time wrangling and structuring data to support their various marketing use cases.

This is primarily driven by the rigid data structures of marketing automation platforms (I said I wouldn’t continue to talk about Salesforce in this article, but SFMC data extensions or PET tables in Oracle Marketing Cloud are probably the best examples of this).

With a composable approach and well-structured data in the data warehouse, the CDP can function as the "brain" of marketing automation, with the downstream platform simply executing the messaging.

### 3. Identity management

Customer identity is the biggest blocker to achieving fast time to value with a CDP. For enterprises with complex data structures (e.g., accounts, households, multiple brands, etc.), this is especially true.

While engineering-focused rETL tools talk about this benefit, and composability provides significant benefits in enabling teams to leverage complex identity structures, these benefits should also be extended to CRM teams.

Getting identity right means not only being able to structure data to reflect the customer context but also being able to personalize the customer experience against it (and leverage relational data tied to the customer context).

For example, we have many clients who have multiple brands, and being able to personalize the experience based on the context of a given brand, while also being able to understand the customer holistically across brands, is an important use case that comes to mind.

With a traditional CDP, and Salesforce Data Cloud may now be the most prominent example of this, the quality of your identity resolution, data science model outputs, and the blocking and tackling of your CRM program — segmentation, personalization, orchestration, and the like are dependent on the data quality within your traditional CDP.

## Why composability matters

With a composable approach, there is no divide between investments designed to solve these problems at an enterprise data level and the business outcomes that CRM teams are driving toward.

Further, composability means that achieving these goals can be accomplished through credentialization of the CDP into the data warehouse vs. a months- or years-long implementation of the CDP and ongoing maintenance and integration work as data changes.

With GenAI advancements, GPTs and the like can interpret a dataset to, for example, generate the right email content for 1-1 personalization. GenAI could do this regardless of where the data lives, but the quality of the output is going to be determined almost entirely by the quality of the dataset and not the quality of the model itself — something that is certainly improved with a composable approach because the GPT can interpret the entire corpus of customer data.

I predict that the more vendors, data, and CRM teams adopt composable approaches and the more they can express the business value or use cases that composable approaches enable, this trend will move from the collective industry navel-gazing that composability seems to have so far represented and will eventually become a requirement of CDP vendors.