How to build a credible CDP business case

Do not start with the category promise

Claims about a 360-degree customer view, personalisation or artificial intelligence are too broad to fund responsibly. Start with a decision that already happens and show how better customer identity, fresher data or consistent activation would change it.

The first business case can be narrow. It should not be vague.

Choose a use case with an observable value path

• Customer suppression: acquisition spend no longer directed at known customers or ineligible records.
• Win-back: lapsed customers reached in a relevant window using maintained lifecycle data.
• Lead-stage control: media treatment changes when a lead qualifies, progresses, converts or becomes ineligible.
• High-value acquisition seeds: prospecting informed by customers with observable value, retention or conversion quality.
• Clean-room activation: approved customer cohorts prepared for governed collaboration or measurement.

Build a baseline before forecasting improvement

For suppression, identify the acquisition campaigns, current audience overlap and destination match rate. For win-back, record the eligible population, current reactivation rate and customer value. For acquisition seeds, record qualified conversion and downstream value rather than only platform conversion volume.

If the baseline cannot be measured, treat the initial implementation as a measurement phase. Do not turn missing evidence into an optimistic benefit assumption.

Use conservative benefit ranges

Estimate the value directly affected by the audience decision, then apply measured match rates, realistic adoption and a range of possible outcomes. Separate value already captured by current processes from the incremental value the CDP may add.

Show a downside, expected and upside case. The expected case should still justify the work after implementation risk and internal effort are included.

Include the full cost to operate

• Initial data discovery, identity design and implementation.
• Platform licence or managed-service fee.
• Cloud storage, processing and monitoring.
• CRM, analytics, warehouse, destination and clean-room integration.
• Privacy, security, procurement and legal review.
• Internal or partner time for audience changes, quality assurance and measurement.
• Future custom work that is necessary for the agreed roadmap, not merely desirable.

Company-size labels do not determine value

A New Zealand enterprise may be described as mid-sized in Australia or the United States. Revenue and employee bands therefore make weak qualification rules for customer-data technology.

The stronger test is whether the organisation has meaningful first-party data, ongoing media investment, maintained customer states and a repeatable audience decision whose value exceeds the cost and operating burden.

Set evidence gates for each phase

• Data gate: the source fields are available, maintained and usable.
• Identity gate: the agreed records can be reconciled with an acceptable error rate.
• Activation gate: audience entry, exit and destination delivery work as designed.
• Measurement gate: the use case has a baseline, test or holdout.
• Commercial gate: conservative annual value exceeds the full annual cost.
• Expansion gate: the next use case can reuse the customer layer and has a named owner.

Compare operating models, not only licences

A lower software fee can still create a higher total cost when identity design, data engineering, destination support and day-to-day operation sit elsewhere. A managed model can be stronger when the business needs the capability but does not need a permanent specialist martech team.

Fractyl can be managed by the Fractyl team, licensed to an agency or client team, or operated through a shared model. The proposal should state exactly who owns each responsibility.

Use Fractyl pricing as a starting benchmark

Indicative Fractyl onboarding starts from NZ$5,000 excluding GST. A typical managed implementation is NZ$2,500 per month, per brand, excluding GST.

Final pricing depends on the CRM, data volume, cleanliness and structure, required destinations, security needs and custom integration work. Australian proposals make currency, tax and scope explicit.

The board-level case in four sentences

Name the customer decision that is currently weak or manual. Quantify the conservative annual value affected. State the first implementation, full annual cost and accountable operating team. Define the evidence required before any expansion.

If the case needs a long list of future features to work, the first scope is not strong enough yet.