
Foundations
Part of Customer data platforms foundations for buyers
Turning four customer-data problems into reversible commercial tests
Turn four customer-data problems into reversible commercial tests for England, with evidence, ownership, acceptance and stop rules instead of forecasts.
Commercial opportunities in customer data platforms should begin as buyer-problem hypotheses. The sources reviewed on 6 September 2026 do not establish an England opportunity size, adoption rate or forecast. Each route below therefore needs a real buyer, authorised evidence and a small reversible test before anyone claims demand.
What to take away
- Start each customer-data opportunity as a buyer-problem hypothesis, not a claimed market size.
- Run a small reversible test with synthetic or fixture records before connecting live activation.
- Name an owner and a stop rule for every test, and record acceptance evidence.
- A paid brief, permissioned trial or explicit rejection beats a favourable interview comment.
- Do not fold the four opportunities into a market forecast.
Data-lineage and identity review
Problem: a buyer cannot show which source supplied a profile field or why records were joined.
Source-to-output map
- Synthetic records with false match
- Split identity and stale attribute
- Missing identifier
- Source-to-output map
- Exception log
Smallest test: use synthetic records containing a false match, a split identity, a stale attribute and a missing identifier. Produce a source-to-output map and an exception log without connecting a live activation destination.
Acceptance evidence: another authorised reviewer can reproduce every join and locate the originating field. Thresholds remain blank until the buyer defines the decision risk.
Owner and stop rule: the buyer's data owner decides. Stop if source authority is unclear, uncertainty is hidden or correction cannot return to the source. The ICO's data-protection principles guidance supports scrutiny of minimisation and accuracy, but does not endorse an identity method.
Rights and suppression propagation test
Problem: correction, objection, suppression or deletion evidence ends at one application.
Rights propagation trace
- Authorised fixture requests
- CRM state change
- Analytical store state change
- CDP function state change
- Output queue state change
- Conflicting update test
Smallest test: issue authorised fixture requests through a copy of the proposed journey. Trace state changes across the CRM, analytical store, CDP function and output queue. Include a conflicting update to see whether a suppressed record is recreated.
Acceptance evidence: a timestamped record shows every recipient, outcome, exception and accountable decision. The ICO's individual-rights guidance provides a UK regulator boundary; qualified review is still needed for the actual facts and exemptions.
Owner and stop rule: the privacy owner accepts the evidence. Stop if one destination cannot receive or prove the required state.
Tag and collection inventory service
Problem: an organisation cannot connect pixels, tags, scripts or software development kits to purposes, providers and user controls.
Smallest test: inspect a bounded non-production journey and create a versioned inventory containing technology, trigger, data, provider, purpose, storage or access action and proposed control. Do not expand collection during discovery.
Acceptance evidence: the technical inventory reconciles with the declared journey and exposes unresolved items. The ICO's guidance on storage and access technologies covers more than cookies and makes purpose important. A technical label is not a legal conclusion.
Owner and stop rule: the product owner and qualified PECR reviewer decide separately. Stop if a technology's operation, provider or purpose cannot be verified.
Exit-readiness and recovery evidence
Problem: the buyer cannot show what it would recover if a hosted or managed service ended.
Smallest test: export synthetic profiles, consent or preference states, mappings, transformation rules, logs and configuration where the proposed scope requires them. Attempt a documented restore outside the service.
Acceptance evidence: files are usable, provenance survives, access is controlled and supplier deletion evidence is specified. The NCSC's supplier assurance questions includes prompts on return, secure deletion and termination. It does not prove that any supplier can meet a buyer's requirement.
Owner and stop rule: procurement and the operational data owner both sign the result. Stop if essential meaning or audit history is trapped in an undocumented format.
How to test commercial interest
For each hypothesis, recruit eligible England organisations through a declared frame. Record the organisation rule, respondent authority, recent workflow event, current route, evidence offered and decision date. Keep research permission separate from later promotion. A useful outcome is a paid bounded brief, permissioned trial or explicit rejection with reasons, not a favourable interview comment.
Do not add the four opportunities into a market forecast. One buyer may face all four, and one service may address several. Expire the hypothesis if no eligible organisation supplies the required evidence, if the manual route passes at lower risk, or if non-compensating privacy, PECR, security, accessibility, contract or exit gates fail.
Before you act
- Recruit eligible England organisations through a declared frame.
- Define the buyer, authorised evidence and a small reversible test.
- Keep research permission separate from later promotion.
- Record respondent authority and the recent workflow event.
- Stop if source authority or purpose cannot be verified.
- Expire the hypothesis if no eligible organisation supplies evidence.
Common questions
What counts as acceptance evidence for the data-lineage test?
Another authorised reviewer must reproduce every join and locate the originating field. Thresholds stay blank until the buyer defines the decision risk. The buyer's data owner decides, and the test stops if source authority is unclear, uncertainty is hidden or correction cannot return to the source.
Why should collection not expand during the tag inventory test?
The smallest test inspects a bounded non-production journey and builds a versioned inventory of technology, trigger, data, provider, purpose, storage or access action and proposed control. The text says do not expand collection during discovery. A technical label is not a legal conclusion, so a qualified PECR reviewer decides separately.
When should a hypothesis be expired?
Expire it if no eligible organisation supplies the required evidence, or if the manual route passes at lower risk. Also expire it if privacy, PECR, security, accessibility, contract or exit gates fail without compensation. A useful outcome is a paid brief, a permissioned trial or an explicit rejection with reasons.



