The problem
A retail bank launches a loyalty programme. The CRM team builds the email journey. The product team designs the points mechanics. Tech builds the platform. Three teams, three roadmaps, three definitions of "a loyal customer."
Six months later: the email team can't trigger on points events. The points system has no data on who actually churns. The platform goes live with a login wall that kills activation before it starts.
Nobody failed at their job. The system failed because there was no system.
The concept
Loyalty is an outcome of integration. It breaks at the seams between teams — where CRM meets product, where data meets comms, where customer expectation meets backend reality.
Knowing who you're talking to is the foundation. Not a segment. Not a persona. A shared, operational definition of your customer: who they are right now, what they did last week, what they're likely to do next.
That definition has to live somewhere everyone can see it. And it has to update.
Most programmes skip this. They build the rewards mechanic first and assume the customer data will follow.
How to
1. Map who owns what. List every team touching the programme. For each: what data they hold, what decisions they make, what they need from others. One table. Do it in a room together.
2. Define "loyal customer" once. Not for a campaign — for the programme. What behaviour, what frequency, what value threshold makes someone worth treating differently. Write it down. Get sign-off from every team that touches it.
3. Find your single source of customer truth. Usually your CRM or CDP. If it doesn't exist: identify the closest thing and name the gaps explicitly.
4. Build one shared customer view before you build anything else. Before the points mechanic. Before the comms calendar. One place where all teams see the same customer.
5. Run a pre-launch integration check. List every data dependency in the programme. For each: does it exist today? Where does it live? Who owns it? What breaks if it's late?
Common mistakes
Defining the customer differently in every team. CRM calls them "active users." Product calls them "power users." Finance calls them "high CLV." Three names, three criteria, no shared reality. The programme optimises for the wrong person.
Assuming the data will be there. The comms plan requires real-time points balance in the email. The points system updates nightly. Nobody checked. The email goes out with yesterday's number. The customer calls support.
Treating the integration problem as a tech problem. Tech can build the connections. They can't decide what connects to what, or why. That's a business decision. Programmes that wait for IT to "sort the data" don't launch well.