Company
How we run phased ERP rollouts
Module by module, unit by unit, with each stage live before the next begins.
ERP programmes fail in predictable ways. The most common is the big-bang cutover: eighteen months of building, one weekend of migration, and a business that cannot invoice on Monday.
We do not run projects that way.
Modules go live one at a time
Every ERP engagement is broken into modules with a deliberate sequence. Procurement and inventory usually go first, because material data is what makes every downstream figure trustworthy.
Each module goes to production before the next begins. The client gets working software early, and we get real usage feedback while the rest is still being designed.
One unit before all units
Within a module, we deploy to a single site or department first. Problems surface at a scale where they can be fixed quickly rather than across an entire organisation at once.
On the Ravi Mills engagement this meant procurement went live in one unit for three weeks before the other two followed. Two data model corrections came out of that period, both cheap to make at that point and expensive later.
Shared master data from day one
The one thing we do not phase is the data model. Every module writes to shared master data from the first release. This is what separates an ERP from several applications wearing the same logo.
The sequencing is negotiable. The shared model is not.