How much does a customer data platform cost?
If you’re one of those shoppers (like me) who looks at the price first, deciphering customer data platform (CDP) pricing will frustrate you.
CDP pricing is complicated for two reasons.
A CDP that started as an email service provider might base its price on events, like emails sent, page views, clicks, etc. A CDP that originated as an analytics platform might base its price on total web traffic, while a CDP that used to be a data warehouse might set its price by how many profiles are under management.
There are many other price models, including by:
You will have to get a custom quote from each vendor you’re considering, but the quote won’t tell the whole story.
MarTech defines a CDP as “a marketer-managed system designed to collect customer data from all sources, normalize it and build unique, unified profiles of each individual customer. The result is a persistent, unified customer database that shares data with other marketing technology systems.”
Most CDPs started off as something else and added or acquired functionality to become full-fledged CDPs. Knowing a CDP’s origin story gives you insight into:
If there’s a conflict, it can become a hidden cost in added development time and workarounds. A good fit can be better than a good price. Vendors that specialize in a CDP tailored for your business and industry may be ideal in the long run.
If you’re in the market for a CDP, you probably have solutions for someof what CDPs offer. For example, you might already have a service to manage a paywall, which most CDPs can also do.
Early on, you’ll have to make the best-of-breed vs. Swiss Army knife choice.
Some CDPs stick to a narrow focus. They provide a consistent, single view of the customer (which is a myth — but never mind that for now). These best-of-breed CDPs rely on other applications to send emails, cleanse data, create interactions on the website, build forms, provide content recommendations, and so on. They position themselves as “best-of-breed” in their narrow focus and expect you to use other solutions for other tasks.
Swiss Army knife CDPs incorporate some or all of the functions mentioned above into their solutions. The drawback? You may use functionality provided by your CDP vendor when a solution offered by another vendor dedicated exclusively to providing that function or service would be a better choice. Let’s face it, the can opener on a Swiss Army knife isn’t best-of-breed, but it will get the job done when it’s the one you have in your pocket!
There’s no simple solution to this choice. It’s tempting to think it’s wise to use best-of-breed solutions for every function. But, aside from the fact that “good enough” is often good enough, that can be impractical.
All of this is relevant to pricing because the cost of the CDP isn’t only what you’re quoted. You also have to consider what you can save by eliminating duplicative services (provided you can get out of the contract) or what you might have to add to get all the functionality you’re searching for.
Here are two examples. CDPs that send email might save you the money you’re currently spending on an ESP. But a CDP that doesn’t have a clean integration with an essential service might result in development or middleware costs.
These and many other factors add complexity to CDP pricing. It depends on your size and the services you’re looking for, so you have to start the process by developing use cases. What will you do with a CDP and what return on investment are you hoping to get? Documenting these cases will help you list all the functions you require.
With use cases in hand, you can add and subtract costs from a CDP bid based on what current services you can discard and what additional services you’ll need.
The minimum investment for a CDP is about $5,000 per month. It will go up from there based on volume and so on. It’s quite easy to get into multiples of six figures annually or more, so you should only invest in a CDP if your use cases are likely to result in substantial savings or additional revenue.
If the price tag scares you, don’t let that stop you from investigating. You might not need a full CDP. By working on your use cases and considering what functions are required to make them happen, you might discover things you can build yourself — or some “not quite CDP” solutions that solve your requirements.
The best thing about considering a CDP is that it requires you to think about what you’re doing, why and what benefit those current or potential activities would bring to your company and your customer. That exercise can sharpen your focus, and you might discover revenue opportunities that make the price sting a little less.
Opinions expressed in this article are those of the guest author and not necessarily MarTech. Staff authors are listed here.
