The hidden cost of scattered systems
For a retailer running five separate tools, the real bill is not the license fee — it is teams starting from scratch with the same customer every morning.
Asking how many tools a brand runs is really asking how many pieces its customer has been cut into. The pattern we see in the field is always the same: campaigns are built in one tool, sales tracked in another, loyalty points held in a third, and the contact centre talks to people from a fourth screen. All four work correctly — and none of them knows the other three are describing the same person.
The bill is not in licences, it is in repeated work
Add up the licence lines and the number usually looks bearable. The invisible line is the weekly reconciliation spreadsheet, the meetings spent between two reports that disagree, and the hours given to the question "which number is right?". With one retail team we measured it: producing the result report for a single campaign took two full days across three departments. Once the same data lived in one place, that work collapsed into a screen where the report simply exists.
Unifying systems looks like an IT project. It is really about letting every team speak the same sentence.
That is why we built the 1page ecosystem around a single customer profile. CDP, CRM, marketing, commerce, loyalty and analytics all read the same record, so information updated in one channel is immediately true in the next. The goal was never to sell more modules — it is that everyone in the morning meeting can look at the same screen.
Where to start: identity, ownership, measurement
We start unification by describing the customer, not by picking a product: what makes one customer unique in this brand? Phone, email, loyalty number? If three teams give three answers, whichever software you buy, the data will split in two again.
The second step is ownership. If it is not written down which team updates which field, unified data falls apart again within six months: the contact centre corrects an address, e-commerce writes the old one back, and nobody knows which is right. We draw up the ownership table in the first week, before any technical setup.
The third is measurement: pick a single number that shows whether the unification worked. Our favourite indicator is how many screens an answer has to travel through. If a question that needed four screens at the start of the project needs one at the end, you did the work right.
