Packaged vs composable CDP: one brief, four architectures

0:00 Monday, nine a.m.

Monday, nine a.m., you send one brief to four teams.

Win back lapsed buyers by Friday.

0:11 One brief, four lanes

Same customers, same brief, four CDP architectures, in the order the market built them: packaged, composable, Dual Zone and agentic.

0:22 Who builds the segment

In the packaged lane, marketing builds the segment itself within the hour.

No engineer, no ticket.

In composable, marketing can build segments without code, in the reverse ETL tool.

But only from the fields the data team has already set up, and 'lapsed' isn't one of them yet.

So marketing files a ticket, and waits.

In Dual Zone, the lapsed score lives in Zone 1, so the data team adds it to the next warehouse run.

In agentic, nobody builds a segment.

The brief gets rewritten as a goal: an outcome, a measure, a deadline and a limit.

The limit is still empty.

1:04 Who sends, and when

On Tuesday, packaged sends.

The composable segment is ready by the afternoon, and syncs to the email tool every hour or so.

Dual Zone sends in the moment, on the score Zone 1 handed across last night.

The agent sends, reads the clicks and tries again, all day.

1:24 Where each one breaks

Then each lane finds its weak spot.

In packaged, the warehouse says some of those buyers are worth twenty percent less than the CDP thinks, because it nets off returns.

Nobody has said which number counts.

At two in the morning, the composable sync fails, and nothing flags it.

The next send goes out on yesterday's segment.

One customer buys at eight. At ten, Zone 2 still offers her the win-back discount, because her score won't refresh until tonight.

The agent finds the cheapest route to its target, and stops spending on the people who were always harder to win back.

Clicks go up, and margin doesn't.

2:06 What each one costs

So what did each lane cost?

Packaged was quickest to build, and its rules and segments live in the vendor's store, which makes it the hardest to leave.

In composable, every refresh is warehouse compute and a sync billed by the row.

You can refresh every fifteen minutes instead of every hour, but you pay for each run.

In Dual Zone, the cost is the seam: how old a score Zone 2 may act on.

Fresher scores mean more runs in Zone 1, and a bigger bill.

In agentic, it's oversight.

Someone checks the work, and writes the limit the brief left out.

2:46 Who does the work

By Friday, all four have sent the campaign.

As you can see, none of them won.

Each one moved the same work to someone else: the vendor, the data team, the seam between the zones, or you, the person who checks the agent.

So the useful question isn't which lane is fastest.

It's which of those four jobs your team can take on.

See each architecture step by step at Martech Stack Builder, or build your own.