The backdrop: efficiency gains meet slowing growth

The business context was familiar.

Sales performance across several markets was flat to slightly declining. At the same time, internal teams were managing complex content workflows, fragmented data, and slow production cycles.

A CMS transition promised relief: a) Fewer operational silos, b) Faster content updates, c) Better integration with modern tools. All helpful. But largely internal.

The analysis made one thing clear early on: technology change alone was unlikely to materially affect revenue. Growth would require something else.

Why personalisation kept coming up

Industry benchmarks pointed in the same direction.

• Advertising costs were increasing year over year
• Cost per lead was rising faster than conversion rates
• Customers showed stronger engagement when content felt relevant

At the same time, many organisations struggled to act on this insight. Real-time data was available, but rarely activated across channels in a coordinated way.

The gap wasn’t ambition. It was execution. This is where the CMS shift became interesting, not as a destination, but as a foundation.

The approach: test before scaling

Rather than rolling out a full transformation, the team modelled several scenarios.

They ranged from baseline performance (no meaningful personalisation) to higher-efficiency cases where data was actively used to shape experiences.

The most conservative scenario assumed: a) Limited behavioural targeting, b) No major media efficiency gains, c) Incremental improvements in lead quality.

Even here, the numbers were worth attention.

At scale, small percentage uplifts translated into tens of millions in additional revenue annually, driven primarily by better conversion of existing demand.

To validate assumptions, a short proof-of-concept was proposed:

• Limited to two mature markets
• Time-boxed to six months
• Focused on a small set of high-impact use cases

The aim wasn’t optimisation theatre. It was learning.

What the PoC was designed to test

The pilot focused on four practical steps:

1. Data strategy definition: Identifying which signals were actually useful for personalisation, not just available
2. Data connection, not replacement: Linking existing systems without disrupting ongoing operations
3. Market-specific use cases: Selecting scenarios where relevance could realistically influence intent
4. Continuous optimisation: Measuring, adjusting, and learning rather than locking in assumptions

Importantly, the investment was modest relative to the size of the business. The expectation wasn’t certainty. It was directional evidence.

What this means for decision-makers

A few broader lessons stand out.

First, CMS upgrades are often oversold as growth drivers. Their real value lies in enabling speed, consistency, and integration.

Second, personalisation only pays off when it’s treated as a system, not a feature. That means data, governance, and operating models, not just tools.

Third, in high-volume businesses, small improvements matter. A fraction of a percent can justify experimentation when the downside is capped.

Finally, testing beats debating. Especially in uncertain markets.

Closing thought

Growth doesn’t always come from bold bets. Sometimes it comes from disciplined ones.

This case shows how organisations can explore new growth levers without committing to full-scale transformation upfront. Not by chasing certainty but by creating the conditions to learn faster than competitors.

If you’re navigating similar constraints, the question isn’t whether personalisation works in theory.

It’s whether you’re set up to test it properly.

Curious what a low-risk pilot could look like in your context? Start small. Measure honestly. Let the data earn the next step.