Customer record
Customer data, source mappings and definitions brought into a record your team can use.
NTWRK / AI-NATIVE INTELLIGENCE YOU OWN
Quiet intelligence
beats loud platforms.
Your people know which customers need attention and where a process gets stuck. NTWRK builds that knowledge into the systems your business already runs. Your business owns what’s built, and your people can see why each decision was made.
Book a call
A 30-day proof on one decision.
See the work
30-MINUTE CALL · THE DECISION · WHERE THE DATA SITS · WHO WILL RUN IT
What you own
Some platforms can now leave your data in your warehouse, which is good. The question is where your identity rules, segments and agents live.
- Decision logic The rules or model behind each decision, tested and versioned, with every decision recorded.
- Data record The customer or site data each decision uses, with its sources and definitions written down.
- Workflow The steps that carry each decision into the tools your team already uses.
- Documentation Runbooks and training, so your team can run the system and change it as the business changes.
SELECTED CLIENTS
Build to Keep · Field notes
A useful next read.
Wes Fischer writes about the decisions behind the build: what to keep, what to question and what to test before committing.
You’re subscribed to Build to Keep. The next issue will arrive by email. Every issue includes an unsubscribe link.
Check your inbox for a link to confirm your subscription. Click it to receive Build to Keep.
Your subscription didn’t go through. Please try again in a moment.
Email delivery is stopped for this address.
No confirmation email has been sent. To check the delivery status, email hello@ntwrk.com.au from this address.
01 / WHAT WE BUILD
What a working build can include.
The use case determines the build. These are the parts we may need, with the deliverables and dependencies agreed in the scope.
Your environmentEight possible parts
Records & signals
01
02
Signals
The behaviours and events that matter to the decision being tested.
Decisions & workflows
03
04
05
06
Model
Scoring or prediction logic, with the tests and documentation needed to review it.
Decisions
Rules that turn the evidence into a recommended next action.
Workflows
The steps that carry the decision into the tools your team uses.
Agents
AI assigned to a defined task, with agreed permissions, checks and escalation points.
Measurement & handover
07
08
Measurement
A baseline and outcome measures that show whether the work is useful.
Handover
Documentation, runbooks and training for the people responsible for the completed work.
One build · Yours to keep
02 / HOW WE START
One decision, tested in 30 days.
Pick the decision that costs the most when it’s slow or wrong. For a retailer, that might be which loyalty members get a call after a second complaint about the same store. The proof tests that one decision on your data, against a baseline agreed before the work starts. At day 30 you have the evidence for the next step: build, buy, change the process or stop.
-
The decision
Defined with a baseline and a test, agreed before the proof starts.
-
The proof
A working proof on your data, with its results and known limits.
-
The record
The documented work behind the proof, from data record to workflow.
-
The recommendation
Build, buy, change the process or stop, with what it would take to run.
From 10 December 2026, organisations covered by the new duty must add information to their privacy policies about certain automated decisions that use personal information and could significantly affect a person’s rights or interests. Source: Privacy and Other Legislation Amendment Act 2024, new Australian Privacy Principle 1.7. Read the field note
Stop at day 30 and the four outputs are handed over, documented.
The POC tests an idea on agreed cases. It does not establish production readiness or guarantee a return. It runs in your environment or an agreed, controlled NTWRK workspace. The scope sets out access, deliverables and handover. Any production build is agreed separately.
Book a call
A 30-day proof on one decision.
See what you own
03 / BUYING COMMITTEE
One build. Five reasons to say yes.
A build like this is rarely one person’s decision. The same system has to answer different questions for the CEO, marketing, data, finance and risk.
One build, read five ways. Each seat asks a different question of the same system.
AI in the work, not beside it.
The agents and workflows sit inside the operation, and your team runs them.
An audience that compounds.
Each campaign adds signal to the customer record your team already holds.
ONE BUILDin your environment
No new silo to run.
Records, pipelines, rules and model logic documented enough to inspect and change.
An asset, not a subscription dependency.
The spend turns into records, workflows, logic, documentation and a trained team.
Each decision, traced to its record.
Every decision is recorded where your team can inspect it, with the logic behind it.
04 / FAQ
Questions worth answering first.
What does the 30-day POC give us?
One decision that costs your business when it’s slow or wrong, tested on your own data. Before the proof starts, the decision is defined with a baseline and a test. At day 30 you have a working proof, its results and limits, what it would take to run, the decision logic, data record, workflow and documentation, and a recommendation to build, buy, change the process or stop. For a dealer network, the decision might be which new enquiries get a same-day call back. A production build is a separate decision, scoped after the proof.
Do we need perfect data before we start?
No. The proof needs enough access to test one decision and to show the limits of the data behind it. An early data checkpoint shows whether the data can support the test, before most of the work is done. Bring the decision you want to improve and the names of the systems involved.
What happens if we stop after the POC?
You keep the documented work: the results and limits, the decision logic, data record, workflow and documentation behind the proof, and the recommendation. Stopping at day 30 is a planned option in every scope. A recommendation not to build saves the cost of a build that wouldn’t have paid its way, and that’s a useful result too.
Can our internal team run the finished work?
Yes. That’s what a production build is for. Before it starts, the scope names who in your team will operate it and what the handover includes. Every decision the system makes is recorded, so your people can see why each decision was made and run the system as part of their daily work. Support after handover is a separate agreement, if you want one. A completed POC may still need further work before production.
Where does the finished work run?
In your own environment or your own cloud account, or NTWRK can host it if you need that. The scope records which. Either way, your business keeps the decision logic, the data record, the workflow and the documentation, and authorised people in your organisation can query the data. Cloud and model costs continue after handover wherever it runs, and the scope lists each one.
Do you earn anything from the tools you recommend?
No. NTWRK is technology agnostic, with no reseller or referral deals. If buying a product or changing a process answers the question better than a build, that’s the recommendation you get.
How is the work priced?
Pricing is set in the proposal after scoping. Each proposal quotes a fixed fee for a defined scope, and a production build is priced separately from the proof.
START WITH THE DECISION
Bring the decision worth testing.
In a 30-minute call, you’ll find out whether the decision can be tested on the data you have, and who in your team would run the finished work. Pricing is set in the proposal after scoping.
Book a call
First engagement: a 30-day proof on one decision.