Customer data platform costs: a whole-life budget template with a worked £82,500 example

A customer data platform needs a defined buyer-owned journey before it has a cost. A public category price cannot show what a configured service will cost. Ask each supplier for a comparable written quotation and build the budget from those answers, using the budget template as the record.

What to take away

Set the boundary before asking for cost

Write down which jobs the budget covers. A CRM, warehouse storage, identity resolution, consent management, tag storage, analytics, activation and managed integration are different functions. One contract may bundle several, but a bundle does not remove the need to price each dependency.

Describe the current process as the baseline: its systems, hand-offs, error correction, staff effort and existing contracts. Do not invent a wage or an efficiency rate. If the baseline is not written down, any saving claimed later has nothing to be measured against.

For the build-or-buy decision, the comparison of CDP vs data warehouse shows which functions you may already own.

Make every supplier figure identifiable

Do not copy a monthly figure into the budget until the quotation record is complete. The table lists the fields to request. A quotation that omits one of them stays on hold.

Profiles, events, storage, destinations, seats, environments and service hours cannot be averaged as if they were equivalent. Define whether a profile is unique, active, known, merged or billable more than once. For an event price, record which event states count and how retries and duplicates are treated. The page on pricing models compared shows why the units differ.

Compose the whole-life cost

Supplier cash is one line. The real cost includes subscription, usage and support; discovery and contract review; migration and data-quality correction; privacy and legal analysis; security testing; training and change control; and renewal, export and deletion.

The article on hidden costs lists items that a headline fee tends to leave out.

The worked example uses invented inputs for a fictional membership service with 10,000 authorised profiles, 250,000 billable events a month, one hosted edition and a 12-month term.

Supplier cash is therefore about 52 per cent of the total in this example. Rebuild the split from your own quotations.

Use blank, traceable formulas

For each line item, keep currency, VAT basis, unit, quantity, period, scenario, evidence reference, owner and confidence beside the value. Three formulas carry the model, and each stays blank until the inputs are approved.

Do not enter a figure just to make a formula run. A loaded labour rate needs your own approved accounting method, so do not substitute a salary or a market-average guess. Treat low, base and high cases as scenarios with stated inputs, not as a forecast.

Check VAT as a reviewed field

Record whether each supplier figure includes VAT, excludes it or says nothing, and do not assume you can recover it. In HMRC's VAT guide, input tax is the VAT you are charged on business purchases and expenses.

A registered person can reclaim VAT on purchases as it relates to taxable supplies made, but in principle cannot reclaim VAT that relates to non-business activity or exempt supplies. Keep cash timing separate from economic cost: if VAT is payable before recovery, the cash-flow model needs both periods as fields. A qualified UK accountant should confirm your treatment.

Budget privacy, security and contract work

Privacy work is a cost at the start of the project, not a final check. The Information Commissioner's Office states in its data protection by design guidance that organisations must put in place appropriate technical and organisational measures.

Early privacy work can reduce longer-term costs by preventing large-scale redesigns, so budget it before configuration starts.

Where a supplier acts as a processor, the contract needs minimum terms. These include processing only on documented instructions, a duty of confidence, security measures, rules on sub-processors, help with data subjects' rights, end-of-contract provisions, and audits and inspections. That guidance is under review after the Data (Use and Access) Act 2025, so check it before signing.

Security is an operating cost, not a one-off questionnaire. A lightweight approach to cloud security identifies four areas where you rely on the provider: data encryption, authentication and access control, security logging and incident management, and governance. The wider data protection duties sit alongside them.

Control sensitivity, renewal and exit

Vary one declared input at a time: billable profiles, ingested events, storage, destinations, support scope, internal effort, data-cleaning work, renewal terms and exit work. Set reforecast triggers before approval, such as a changed identity definition, an added source or a supplier unit change.

The exit budget should include the export specification, preservation of suppression records and provenance, an isolated restore test, transition support, access removal and deletion evidence. A nominal export feature does not prove a usable departure. Plan for migration without data loss from the first quotation.

Tie contingency to a named uncertainty, such as an unresolved profile definition or an untested restore, rather than adding an unexplained percentage to every row.

Before you act

Common questions

What should a buyer do when only a public category price is available?

Treat it as a prompt to request written quotations. Ask each shortlisted supplier to cover the exact edition, unit, quantity, billing period, term, additions, overages, renewal, VAT basis and exit charge on the same date. Compare only quotations that answer every field.

How should VAT be treated in a customer data platform budget?

As a reviewed field on every supplier figure. Registered businesses can reclaim input tax only as it relates to taxable supplies, so recovery depends on your circumstances. Ask an accountant to confirm it.

Why not turn profile or event counts into money?

Counts are system outputs, not financial results. Use accounting evidence for realised transactions, refunds, delivery costs and direct variable costs, and claim a benefit only where a credible comparison supports it.