What does a customer data platform cost in Australia and New Zealand?

Why CDP pricing is difficult to compare

Customer data platforms package cost in different ways. Some charge by profiles, events, destinations or modules. Others require a separate implementation partner, cloud environment or internal operations team.

A low software line can still create a high total cost if identity, data engineering and audience operation sit outside it. A larger licence can be justified when the organisation genuinely uses the broader capability.

The six costs to include

• Platform licence or managed-service fee.
• Initial data, identity and audience design.
• CRM, analytics, warehouse and destination integration.
• Cloud storage, processing and monitoring.
• Privacy, security, procurement and legal review.
• Ongoing people time for audience changes, quality assurance, incident response and measurement.

Fractyl provides a transparent starting point

Indicative Fractyl onboarding starts from NZ$5,000 excluding GST for the initial implementation. The typical managed monthly cost is NZ$2,500 per month, per brand, excluding GST.

These are starting benchmarks rather than a binding quote. The final scope can move up or down depending on the systems, data and operating model. Australian organisations receive an agreed commercial proposal that makes currency, tax and scope explicit.

What changes the Fractyl price

• CRM system and how its data can be accessed.
• Record volume, processing load and required refresh frequency.
• Duplicate, incomplete, inconsistent or outdated data.
• Availability of stable customer IDs and useful lifecycle fields.
• Number of audiences, brands, regions and live destinations.
• Custom connectors, clean-room workflows and security requirements.
• Whether Fractyl, an agency or the client team operates the platform.

Price the first use case against conservative value

Start with the annual acquisition budget or customer value the first audience can affect. For suppression, estimate the spend reaching known customers, then apply measured destination match rates and check that exclusions do not remove valid prospects.

Keep waste removed separate from any predicted improvement in conversion quality. If the conservative value is not clearly larger than the annual fee and internal effort, reduce the scope or do not proceed.

Questions to ask every CDP vendor

• What is included in implementation and what requires a partner?
• Which source and destination connectors are live for our exact systems?
• Who maintains identity rules and audience logic after launch?
• Which cloud, profile, event or usage charges can grow over time?
• What security and procurement evidence is available?
• How is the first use case measured?
• What is the three-year licence, implementation, cloud and operating cost?

A commercially credible starting scope

A useful first proposal should name the source systems, first audiences, destinations, refresh schedule, governance responsibilities, measurement plan and exclusions. It should also show which later ideas are not included.

That clarity matters more than buying the longest feature list. The first scope should be small enough to prove, but built on foundations the next audience can reuse.