Proposal · Example deck
A 30-day proof for Example Co.
Prepared for Example Co. · 5 October 2026
Example Co. is fictional
02
02 / The first 30 days
One decision, tested in 30 days.
01 / What the data says Illustrative
50%
of 160 one and two star reviews got a reply in the 12 months to [date].
The other 80 did not. That is where to start.
n=160 reviews · fictional Example Co. · illustrative figure
03 / Why ownership matters
Your next supplier decision should include the exit.
Ask for the deliverables, access rights, ongoing costs and handover responsibilities in writing.
04 / What we build
The use case determines the build.
These are the parts we may need, with the deliverables and dependencies agreed in the scope.
Records and signals
Decisions and workflows
Measurement and handover
05 / Replies by rating Example data
Half of the 160 complaints got no reply.
Five-star
Four-star
Three-star
One and two star
Reply rate by rating · n=2,000 Google reviews, 12 months to [date] · fictional Example Co. · example data
06 / What your business owns
When the logic is yours, so is the record.
What you own
- Decision logicThe rules or model behind each decision, tested and versioned, with each decision recorded.
- Data recordThe customer or site data each decision uses, with its sources and definitions written down.
- WorkflowThe steps that carry each decision into the tools your team already uses.
- DocumentationRunbooks and training, so your team can run the system and change it as the business changes.
Runs inYour environment · Your cloud · Hosted by NTWRK if needed
Rights and dependencies documented
Renting the part that decides
- Platforms that keep your decision logic
- AI seats that leave nothing behind
- Pilots that stop before production
- Consultants who leave decks
07 / After day 30 Example plan
The next commitment is a separate decision.
Day 30
Recommendation
Evidence for the next decision: build, buy, change the process or stop.
Month 2
Production build, if agreed
Agreed separately, based on what the proof shows.
Month 4
Your team makes a change
The owner inside the business approves and ships it.
Month 6
Review against the baseline
Outcome measures show whether the work is useful.
08 / The 30-day proof
One decision, tested in 30 days.
Before
A 30-minute call
The decision, where the data sits and who will run it.
Days 1 to 5
The decision
Agree the decision and check the data, with an early data checkpoint on day 5.
Days 6 to 25
The proof
A working proof on your data, with its results and known limits.
Days 26 to 30
The record and recommendation
Build, buy, change the process or stop, with the work documented.
The 30-day proof tests one decision on agreed cases, with each decision recorded. It does not establish production readiness or guarantee a return.
09 / At renewal
“We could leave, but it would be too hard.”
What someone says when renewal arrives
Build to Keep · Field Note 04
10 / About NTWRK
A Melbourne consultancy that builds intelligence into the systems your business runs.
With a defined handover for your team.
pending
Wes Fischer
Founder and CEO, NTWRK
+61 3 4427 7768
ABN 59 619 107 336
11 / The offer
One decision, tested in 30 days.
01
The decision
Defined with a baseline and a test, agreed before the proof starts.
02
The proof
A working proof on your data, with its results and known limits.
03
The record
The documented work behind the proof, from decision logic to workflow, handed over.
04
The recommendation
Build, buy, change the process or stop, with what it would take to run.
Pricing is set in the proposal after scoping.
Runs in your environment or an agreed, controlled NTWRK workspace. Any production build is agreed separately.
Start with the decision
Bring the decision worth testing.
Book a callFirst engagement: a 30-day proof on one decision.