Scope — discovery & module selection
A focused first week that ends with a signed module set, a wiring plan for your existing tools, and a rollout schedule everyone has seen.
What we actually do in this stage
We sit on a call with your ops lead and walk the operation end-to-end. Orders coming in, picking, packing, dispatch, returns, the spreadsheets and side-systems that hold everything together. Goal is to see the actual process — not the org-chart version of it.
Out of that, we propose a starting module set from the 21 OpsUI modules. Most operators land on 2-9 modules depending on size. We tell you what you do not need yet, not just what you do need.
Finally, we agree the deployment shape: standalone (OpsUI is your system of record) or extend your existing NetSuite. That call is driven by where finance lives today, not by what we want to sell.
What you see at the end of week 1
A short scope document covering:
- Recommended module set with monthly + annual pricing visible upfront
- Standalone vs NetSuite-extension recommendation with the reasoning
- Data-migration plan: what we pull from where
- Carrier + accounting integration list (NZ Couriers live today; Xero / MYOB / NetSuite per-rollout build)
- Schedule for the remaining three stages — typically 5-6 weeks total
What we need from you
About 4-6 hours of your ops lead's time across the week — most of it is the walk-through call and a follow-up review of the scope document. We do not need you to assemble a steering committee or run a kick-off workshop.
What operators actually ask about this stage
Can we add or remove modules after the scope is signed?
+
What if we are not sure between standalone and NetSuite extension?
+
Does the scope document commit us to anything?
+
Ready to start your rollout?
The scoping call is the first stage. Bring one of your own orders — in 30 minutes we walk through claim → pick → pack → ship on live OpsUI.