A customer data platform promises to collect behavioural and transactional data from every channel, resolve it to individual people, and make those profiles available to marketing and support tools. When it works, it is genuinely useful. It also costs a great deal and depends entirely on data you may not have in usable shape.
The prerequisite nobody mentions is identity resolution. Merging a web session, an app install, a support ticket and an order into one person requires a reliable key. If your systems identify customers by email in one place, phone number in another and a generated ID in a third, the platform will produce a merged profile that is confidently wrong.
Fix the keys first. Agreeing an internal customer identifier and propagating it through the systems you already own is unglamorous work that makes every subsequent option cheaper — including the option of not buying anything.
Many organisations discover that what they actually needed was a warehouse and a scheduled job. If the goal is analysis and segmentation rather than real-time personalisation, loading the same data into a warehouse and modelling it there costs a fraction of a platform licence and leaves the data somewhere you control.
The case for a real platform strengthens when you need decisions in milliseconds — showing a returning visitor something different, suppressing an ad for someone who just bought. Batch pipelines cannot do that, and building a low-latency profile store is not a small project.
Whichever route, insist on export. A platform holding your customer profiles in a proprietary format with no clean export path is a dependency you will regret at renewal, and renewal is when the pricing conversation stops being friendly.
