Month one: understand the operating model
The first stage maps how work moves through finance, sales, purchasing, inventory, field service, or manufacturing. The output should be a prioritised scope and a record of decisions, assumptions, dependencies, and exclusions.
Month two: configure and test the core flow
Configuration should follow the agreed process rather than reproduce every workaround. Teams review realistic scenarios, identify gaps, and decide which exceptions need a control, an integration, or a documented manual step.
Month three: prepare the people and data
Data cleansing, import templates, permissions, training, reporting, and cutover planning become the centre of gravity. A system can be configured correctly and still fail if the information and operating habits are not ready.
After go-live: stabilise before expanding
The first weeks are for resolving real usage issues, clarifying ownership, and measuring whether the new process is working. Additional modules and customisations should follow evidence, not the original wish list.
Have a similar problem in your business?
Bring us the current process and we will help you work out whether it is worth solving.
Talk through the problem