How LEGO rebuilt its marketing stack on composable architecture

August 27, 2026 · 5 min · Free, with full transcript

LEGO's migration away from a monolithic digital platform toward a composable, API-first architecture offers one of the clearest real-world tests of what this approach actually costs and delivers. The lessons cut both ways: real gains in speed and personalization, and real friction that most vendors quietly omit from their pitch decks.

Listen to the podcast

4 min

Read the full transcript

Welcome to the Leaders Insights podcast.

Today's episode, how Lego rebuilt its marketing stack on composable architecture.

Lego rebuilt its entire marketing stack on composable architecture, and everyone's calling

it a triumph.

You're about to tell me they're wrong, aren't you?

Not wrong, just selectively honest.

Lego did something genuinely hard and mostly got it right.

But the way vendors are using Lego as a poster child is dishonest, and most companies copying

them will set money on fire.

Start with the basics.

Composable architecture.

What does that actually mean for someone who doesn't live in this world?

It means you stop buying one giant all-in-one platform and instead assemble your stack from

specialized pieces that talk to each other through APIs, application programming interfaces,

the connectors that let two systems pass data back and forth.

Print management here, personalization there, commerce over there.

And the old way?

A monolith, one vendor, one system, everything bolted together.

Think Adobe Experience Manager doing content, commerce, and analytics under one roof.

Convenient until you want to change one thing and discover you can't without touching everything.

So why is Lego the wrong role model?

Because Lego has something you don't.

A platform engineering team of serious size and a brand that prints money.

When they moved to Composable, they weren't saving on licenses.

They were buying speed.

They rebuilt a campaign landing page in days that used to take six weeks.

Days versus six weeks.

That's a real number.

Where's the catch?

The catch is that speed came after roughly two years of plumbing.

Composable doesn't remove complexity.

It relocates it.

In a monolith, the vendor owns the integration.

In Composable, you own it.

That's called the integration tax, and nobody puts it on the slide.

Define the integration tax, because that sounds like consultant speak.

Every one of those separate pieces needs someone maintaining the connections between them.

When your personalization tool updates its API, your content system might break.

Lego reportedly runs a dedicated internal team just keeping the seams stitched.

That's a permanent salary line, not a one-time setup.

Vendors sell Composable is cheaper.

You're saying it's more expensive?

For most mid-market companies, yes.

And notice the numbers always come from the vendors.

When Contentful or Commerce Tools publishes a 40% faster time to market figure, that's

their own customer survey.

Self-selected, best case.

The companies that ripped it out mid-migration don't answer the survey.

So who should actually do this?

Companies where speed of change is worth more than the cost of maintenance.

If you ship three campaigns a year, a monolith is fine.

Wain choi.

Stop buying architecture you'll never stress.

If you're launching localized content across 40 markets weekly, like Lego, Composable

pays for itself.

Let me push.

Lego cited better personalization.

Isn't that the real prize?

It's the prize everyone wants, and few earn.

Personalization, showing different customers different content based on behavior, only works

if your data is clean and unified.

Lego spent enormous effort on a customer data platform, the single database that stitches

one shopper's behavior across web, app, and store, before the personalization delivered

anything.

Skip that step, and you've got a fast system serving the wrong Duplo set to a teenager.

That's the funny part.

A very expensive machine confidently getting it wrong.

It's the most sophisticated way ever invented to recommend a product someone bought last

Tuesday.

The tech isn't the problem.

The data discipline underneath it is where projects quietly die.

So what did Lego get genuinely right that people should copy?

Sequencing.

They didn't rip out the monolith overnight.

They peeled off one capability at a time.

Content first, then commerce, then personalization, with the old system running alongside.

They call it the Strangler pattern.

You grow the new system around the old one until the old one's dead.

Boring.

Unglamorous.

Correct.

Give me the one thing a listener does Monday morning.

Before you call a single vendor, count how often you actually change your marketing content.

If the honest answer is a few times a quarter, composable is a solution to a problem you

don't have.

Tú ludid.

Spend that money on cleaning your customer data instead.

That's where Lego's real advantage lives.

And it's the one part nobody's trying to sell you.

That's it.

The CMO Decision Tools are live at MBA-training.com.

Read and go deeper