The Highest-Leverage Data Project Most Organisations Haven't Started

A sports and entertainment organisation asked us to map its customer-facing systems. We found six different versions of "the customer," and one root cause quietly holding back both personalisation and partner revenue.

Ask most organisations how many systems hold customer data and they'll name three or four: a CRM, an e-commerce platform, a marketing tool. Ask whether "the customer" in one is the same person in another, and confidence drops fast.

We saw this during a tech landscape assessment for a sports and entertainment organisation with no shortage of customer-facing technology

but no way of knowing whether the person who bought a ticket last month was the same person who'd downloaded the app, answered a survey, or made a donation.

The organisation's systems mapped out to six, each running in its own lane:

• A ticketing/CRM platform recording who bought what, when
• An e-commerce platform with its own accounts and purchase history
• A branded app with its own user base and engagement data
• Marketing tools messaging whoever they'd been given data on
• Survey tools capturing feedback and preferences
• A donations platform with its own donor records

Each system did its job well. The problem was that nothing connected them: no unified ID, no shared data layer, no way to say with confidence, "this is one person, and here is their full relationship with us."

One root cause, four symptoms

The consequences travelled past a marketing dashboard.

Fragmented data meant each system held only a partial record of "the customer," with no way to merge them. That made personalisation structurally impossible: if you can't recognise the ticket-buyer, the app user, and the survey respondent as the same person, every touchpoint starts from zero.

It also reached past the customer relationship: the organisation's sponsorship deals are bets on exposure turning into business outcomes, and because ticketing and retail data weren't linked to sponsorship analytics, there was no way to show partners how their exposure performed.

The result was revenue lost twice over - once in missed offers and retention, again in sponsors who, lacking clear evidence of value, are harder to retain, upsell, or charge more.

Four symptoms. One cause. Each likely to land on a different team's desk as its own problem.

The fix - and the trap to avoid

The usual response, once someone notices the pain, is to shop for a new platform: a CDP, a CRM module, a "customer 360" add-on. That's risky - unless it's scoped specifically as the unifying layer, with a mandate to reconcile across systems already in place, it becomes a seventh system with its own definition of "the customer." The fragmentation doesn't disappear. It gets a new member.

Our recommendation wasn't to replace the organisation's systems. It was to build a unified customer ID and shared data layer connecting what was already there:

• Define "a customer" as one concept across the organisation, not one per system
• Build the process that matches and merges ticketing, e-commerce, app, marketing, survey, and donation records into that single ID
• Put the unified view in front of marketing, commercial teams, and leadership - for personalisation, partner reporting, and a real picture of the customer

None of it requires ripping out existing systems - it's the connective layer that was missing, and it's lower-risk and faster to show value than a platform replacement.

Conclusion

Chasing "better personalisation" and "better partner reporting" as separate projects misses the point. Both trace back to the same cause: no single, shared definition of who the customer is.

A unified customer ID won't show up on a slide as a flashy capability, but it's the foundation personalisation, lifecycle journeys, and partner reporting depend on - the project most roadmaps are quietly missing precisely because it doesn't look like a new feature.

Key takeaways

• Not recognising the same person across two systems is a structural gap, not a data hygiene issue.
• Fragmented customer data is one cause behind two visible symptoms: weak personalisation and unprovable partner ROI.
• A new platform without a mandate to unify existing systems just adds a silo. It doesn't remove one.
• The highest-leverage fix is usually a unified ID connecting systems you already have, not a platform replacement.

If your organisation can't say how many "versions" of a customer exist across your systems, that's the highest-leverage data project you're not yet running. We're always happy to help you take a look.