How an engagement runs, and what your business keeps.
Start with one decision. Each stage ends with a handover and a choice to stop. By the end, your team runs the decision logic and the workflow itself, from a record your business keeps.
Six stages, from a call to a handover.
In the order you will meet them.
A 30-minute call
The decision, where the data sits and who will run the finished work.
The decision, defined
A baseline and a test, with an early data checkpoint, written into the scope.
A 30-day proof
On your data, with results, limits, run requirements and a recommendation.
A production build
Separately scoped and agreed, only if the evidence supports it.
Your team runs it
In the tools it already uses, with every decision recorded.
Yours to keep
Documentation and training, in your business’s name.
Each stage has a defined scope and a clear choice to continue or stop. You can stop after the proof and keep the documented work. Support after handover is optional and agreed separately.
Monday’s questions, with the reasons attached.
Every Monday the trade team reviews last week’s numbers and lists questions. The answers arrive by Wednesday, leaving two days to act before the weekend.
Illustrative example · Retail
Example Co.’s Monday trade meeting
Sales against plan, by store week 41 · 15 stores · % of plan
Weeks of stock cover fastest two lines · by store
Website orders for store pickup week 41 · by store
Customer service calls, by store tagged to a store · week 41
Bars: 15 stores. Dark = the four stores flagged.
Top up the two fastest lines in four stores and roster extra Saturday staff at two of them.
The flags arrive in the Monday trade pack and in each store manager’s task list, tools the team already opens.
- Record
- TR-0412 · Mon 12 Oct 2026, 08:05 AEDT
- Logic
- trade-flags v0.6 · approved by Trading Manager
- Records used
- Sales by store, stock on hand, website orders, customer service calls, week 41.
- Decision
- Top up two lines in four stores before Saturday.
- Why
-
Sales ahead of planUnder 1 week of coverCalls about stock rising
- Human check
- Trading Manager accepted; could override with reason.
- Limits
- Website returns aren’t in the record yet. Supplier delivery dates may lag a week.
- Follow-up logged
- Against next Monday’s sales and stock for the four stores.
- Access
- Trade, Retail Operations and Finance; authorised roles only.
The logic, the record, the workflow and the documentation.
Some platforms can now leave your data in your warehouse, which is good. The question is where your identity rules, segments and agents live.
What crosses over at each stage, then a page from each document your team keeps.
Four documents your business keeps, in its own name.
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.
Readable rules your team can change, tested against recorded decisions first.
Trade flags: logic versions
| Ver. | Date | Change | Approved by |
|---|---|---|---|
| v0.4 | 17 Aug 2026 | First release: sales against plan and stock cover. | Trading Manager |
| v0.5 | 14 Sep 2026 | Added customer service calls as a third factor. | Trading Manager |
| v0.6 | 5 Oct 2026 | Cover threshold raised before the Christmas range. | Retail Operations Manager |
Your people question it directly, without asking a supplier for access.
Data dictionary: trade record
| Field | Definition | Source |
|---|---|---|
| store_sales_week | Sales for the trading week, by store, including GST. | Point-of-sale system |
| weeks_of_cover | Stock on hand divided by average weekly units sold. | Stock system |
| web_pickup_orders | Website orders collected in store, counted on the pickup day. | E-commerce platform |
| service_calls_store | Customer service calls tagged to a store by the agent. | Contact centre system |
Runs each day in the tools your team already opens.
Monday trade flags: workflow
Written so a new starter or another provider can take over.
Runbook: Monday trade flags
If a flag looks wrong
- Open the decision record and read the Why field.
- Check the Limits field for gaps in that week’s data.
- Override the flag in the task list, giving a reason.
- Raise a logic change request if the same error repeats.
Where it runs is your call.
- Your environmentBuilt inside the systems you already run, under your access controls.
- Your cloudDeployed to your cloud account. You hold the account and the bill.
- Hosted by NTWRKIf you need it. Documented so it can move to you or another provider.
No reseller or referral deal sits behind any tool in the scope, and there’s no preferred platform. The recommendation follows the decision, and it can be a tool you already have. Cloud and model costs continue after handover, and the scope lists each service.
Your team runs it after handover.
Before the build starts, the scope names who in your team will operate the work and what the handover includes. Your people can see why each decision was made and run the system as part of their daily work.
After handover, NTWRK is optional. Support sits under a separate agreement with a defined purpose, or there’s none at all. If you later want a different provider, the documentation is written so you can appoint one.
Start with a 30-day proof of concept.
A 30-minute call
The decision, where the data sits and who will run it.
The decision
Agree the decision and check the data, with an early data checkpoint on day 5.
The proof
A working proof on your data, with its results and known limits.
The record and recommendation
Build, buy, change the process or stop, with the work documented.
The proof is a complete purchase in itself. You can stop at day 30 and keep the documented work. A production build is scoped separately. Pricing is set in the proposal after scoping. The proof does not establish production readiness or guarantee a return.
START WITH THE DECISION
Bring the decision worth testing.
A 30-minute call: the decision, where the data sits and who will run the finished work.