customer_data.layer
The data
Customer records, source mappings, pipelines, transformations, and rules inside your environment.
OWNERSHIP / GOVERNANCE
Ownership is not a feeling. It is a list.
What we build with you sits in your environment, in your name, with the documentation and operating rhythm your team needs to keep running it.
01 / WHAT YOU HOLD
The ownership checklist.
Seven things your team holds after the build. Each one is a real artefact in your environment, not a setting in someone else's account.
customer_signals.set
The signals
The behavioural, commercial, lifecycle, and service signals used to understand customers.
model_logic.spec
The model
Documented and versioned logic for scoring, segmentation, prediction, prioritisation, or recommendation.
decision_rules.map
The decisions
Rules, triggers, next-best actions, and decision histories traceable to the data behind them.
workflows.ops
The workflows
Lifecycle, CRM, sales, service, campaign, and personalisation workflows your people can run.
measurement.board
The measurement
Dashboards, alerts, outcome reporting, and improvement backlog.
capability.runbook
The capability
Runbooks, documentation, training, and the operating cadence.
02 / OWNED, NOT RENTED
Same data. Opposite outcome.
The same customer data can be owned or rented. The difference is whether your team can see it, run it, and keep it.
OWNED RENTED
The record is in your environment.
The record sits in a vendor account.
Logic is documented.
Logic is hidden in settings.
Model changes are versioned.
Model changes are not fully visible.
Workflow rules can be inspected.
Workflow rules depend on supplier access.
Reporting ties decisions to outcomes.
Reporting is limited to what the platform exposes.
Your team can run it.
Your team pays to keep querying it.
The supplier can leave.
The capability leaves with the contract.
Removability is the test. Remove NTWRK at a phase boundary and the completed work keeps running. We build to that line.
03 / GOVERNANCE
Built for explanation, not dependence.
An operating principle, not legal advice. When the records, rules, model logic, and decisions sit in your environment, the explanation of what happened and why is already written, in your name. From December 2026, Australian businesses must be able to explain how their automated decisions are made. Owning that record is the difference between showing your working and asking a supplier for it.
Data lineage note
Decision-rule summary
Model-change history
Workflow map
Access and responsibility map
Handover runbook
QUIET INTELLIGENCE BEATS LOUD PLATFORMS
See whether building it to keep is right for you.
One conversation about the customer record, the decisions you need to make, and what your team should still hold after the work is done.