The TL;DR
Most brands evaluating a CDP already have the data infrastructure to do what a CDP does.
The data is unified. The profiles exist. The warehouse is running.
What’s actually missing is an activation layer — a way for marketers to use that data in campaigns without filing a ticket to the data team every time.
That’s not a CDP problem. That’s a tooling and workflow problem. And buying a standalone CDP doesn’t fix it.
Here’s what makes this more than an opinion: the market already validated it. In the last 18 months, the CDP category went through a wave of consolidation — acquisitions, rebrands, vendors pivoting away from CDP features toward AI decisioning and activation.
Every major engagement platform and data warehouse rebuilt around the same unified profile capability that CDPs pioneered. The value didn’t disappear. It got absorbed into the tools brands are already running.
Which means for most brands, the standalone CDP is a solution to a problem their existing stack already solves.
What a CDP Actually Does
A CDP’s core functions are:
- Ingest data from multiple sources
- Unify and resolve customer identities
- Create a single customer view
- Make that view available for segmentation and activation
Here’s what we see all the time: brands already have the first three covered.
All data lands in the data warehouse. It handles transformation and enrichment. ETL pipelines are running. Identity is being managed. What they don’t have is a marketer-accessible interface on top of that infrastructure — a place where the CRM team can build segments, launch journeys, and run experiments without going back to data engineering for 70–80% of their work.
That missing piece is an engagement platform. Not another data layer.
A Standalone CDP Adds Complexity, Not Capability
When brands insert a CDP between their warehouse and their engagement platform, the architecture gets longer:
Data warehouse → CDP → Engagement platform
Each handoff introduces latency. Data inconsistency. A new platform to maintain, integrate, and pay for. A new vendor relationship to manage.
What we consistently see is that brands end up with three platforms doing overlapping jobs — and a data team fielding integration issues instead of building better models.
The simpler architecture is:
Data lakehouse → Engagement platform
And increasingly, the activation and decisioning layer lives natively inside the lakehouse itself — not as a bolt-on, but as a core capability. That’s a fundamentally different model than inserting a third-party CDP between your warehouse and your campaigns.
It’s also where the broader market is heading. As AI agents take on more of the work of campaign execution, segmentation, and optimization, the profile layer those agents operate on becomes the critical variable. The brands investing in AI-native CRM operations are building on warehouse-native profiles connected directly to their engagement platform — not routing data through a third system.
The Real Problem Is Activation, Not Unification
A pattern we see across brands is this:
The data team has built something genuinely impressive. There’s a clean customer model in the warehouse. Computed attributes — lifetime value, engagement scores, churn risk, purchase recency — have been modeled and are available.
But marketers can’t get to any of it.
To use a segment, they need to describe it to a data analyst, who writes SQL, runs it, exports a list, and uploads it into the campaign tool. That process takes days. Sometimes weeks. It runs on request queues and sprint cycles. The result is a marketing program held back not by a lack of data — but by a broken workflow between data and marketing.
Standalone CDPs marketed themselves as the solution to this problem. And they can be, in the right context. But what we find in practice is that brands evaluating CDPs often don’t need a separate data layer — they need better tooling that brings marketers closer to the data they already have.
Braze does this natively. Marketers build segments in a no-code visual builder using any combination of profile attributes, behavioral events, and time-based logic. No SQL. No tickets. No waiting.
When CDPs Still Make Sense
It’s worth being direct about where a standalone CDP does make sense — because the answer isn’t never.
When identity resolution is especially complex. Brands with large anonymous user populations, heavy cross-device journeys, or significant probabilistic matching requirements may find that a CDP’s native identity graph offers something a warehouse plus deterministic matching can’t easily replicate.
For omnichannel campaigns across owned and paid. The Braze/Meta integration works well when you already know who you’re targeting — lookalikes, retargeting, suppression. CDPs like TradeDesk and LiveRamp go further, making it easier to push first-party audience data into paid media at scale. For a true cross-channel play that spans CRM and media buying, a CDP can be the right connective layer.
Neither of these is a reason to default to a CDP. They’re reasons to reach for one when the specific architecture calls for it — not because the evaluation checklist says “do you have customer data.”
On Identity Resolution
The most common concern we hear: “But what about identity resolution? Doesn’t the CDP handle that?”
In most B2C environments, deterministic identity resolution — matching anonymous behavior to a known profile at the point of identification — covers the vast majority of use cases.
Braze handles this natively. The SDK creates anonymous profiles. When a user identifies (login, purchase, form submission), Braze merges the anonymous record into the known profile and backstitches prior behavior. Multiple identifiers are supported natively: email, device ID, external ID, in-app identifiers.
For more complex cross-system deduplication, that work happens upstream in the warehouse — before data reaches Braze. This is actually the better approach. The matching rules are visible, auditable, and owned by the brand’s own team. Not locked inside a vendor’s black-box identity graph.
The Cost Reality
CDP licenses are not cheap. And they compound.
You pay for the CDP license. You pay for the integration work to connect it to your warehouse and your engagement platform. You pay for the ongoing maintenance when schemas change or pipelines break. You pay for someone to manage a third platform that your team also has to learn.
When we look at the total cost of ownership across a typical 3-year contract, the cost of a CDP is rarely just the license fee. It’s the integration overhead, the ongoing ops burden, and the organizational complexity of managing one more system in the middle of your stack.
Redirecting that budget toward lakehouse infrastructure and a best-in-class engagement platform delivers more activation capability at lower total cost. The trend is clear: CDP functionality is increasingly valuable inside the data layer — not bolted on top of it as a separate system.
This Isn’t Anti-CDP
Stitch started as a CDP implementation partner. We still implement Braze alongside CDPs regularly. When a brand’s architecture genuinely calls for one, we build it.
What we’re pushing back on is the assumption that a CDP is always part of the answer. In a lot of cases, the problem brands are trying to solve with a CDP is a workflow and tooling problem — one that a warehouse-native engagement platform already solves.
The standalone CDP category consolidated not because the category failed, but because its core value became table stakes everywhere else. The unified customer profile is now an assumed foundation — inside your warehouse, inside your engagement platform, increasingly inside the AI agents running on top of both.
The question worth asking before buying a third-party CDP is:
Do we need a separate data layer — or do we need marketers to be able to actually use the data we already have?
For most brands, the answer is the latter. And the architecture to get there is already inside their stack.
