Live in days, not quarters — and what that actually requires
Enterprise implementations take quarters largely because of scope discovery and data migration, in that order. Neither is a law of nature. Both can be compressed, but only by deciding in advance what you will not do.
1 min readOadbox
Go live on one process, not on the product
The fastest rollouts we run start with a single process that has a clear owner and a visible outcome: fee collection for a school, OPD registration for a hospital, trip sheets for a fleet.
It works because success is unambiguous within two weeks, and because the people who will use everything else get to learn the system on something that matters to them rather than in a training room.
Import is the critical path
Every rollout is gated by data. Master data — students, patients, items, vehicles, employees — has to arrive from spreadsheets that are inconsistent in ways nobody has documented.
- Provide templates, but accept the customer's own file and map it.
- Validate and report every rejected row with a readable reason.
- Make import repeatable — the first attempt is never the last.
- Import opening balances as transactions, so the ledger reconciles from day one.
Configure less than you think you need to
The temptation at kick-off is to configure everything the customer might eventually want. It extends the timeline and produces settings chosen before anyone has used the system.
We configure the minimum required for the first process to work correctly, then revisit at week four, when the customer's questions have changed from hypothetical to specific.
Run parallel, but put a date on it
Running the old process alongside the new one is a sensible safety net and a slow death if it has no end date. Two weeks is usually enough to build confidence; two months guarantees that neither system is trusted.
Set the cut-over date at kick-off, make it a decision rather than a discovery, and hold it unless something real is wrong.
Written by the Oadbox team. Something here not match how it works in your business? We would genuinely like to hear it — connect@oadbox.com.