Go-lives that actually go live.
Our five-phase implementation, borrowed from projects that shipped. The numbering is earned: each phase gates the next.
LAST UPDATED · 11 JULY 2026
ERP projects rarely fail at the software. They fail at the seams: verbal scope, data migrated "later", training squeezed into cutover week. Each phase below is a gate built to close one of those seams.
Configure does not start until Discover has produced a fixed, written scope.
Migration does not finish until the numbers match your old system, line by line.
Go-live waits until every user has been trained in the place they'll work.
The same sequence applies to a full Odoo implementation, an inventory rollout, or an MRA e-invoicing connector riding on an existing system.
- PHASE-01
Discover
Stock-flow map, module shortlist, fixed-scope quote. We walk the floor, follow a product from goods-in to invoice, and write down where it leaks.
- PHASE-02
Configure
A working system loaded with your products, pricelists and workflows. Weekly demos on your data, never sample data.
- PHASE-03
Migrate
Field-mapped migration of sales, invoices, payments, deliveries and stock levels. Trial runs until the numbers reconcile.
- PHASE-04
Train
Role-by-role training at the counter, in the stockroom, in the office. Cheat sheets that survive staff turnover.
- PHASE-05
Go-live & support
On-site cutover, first stocktake together, then support tiers with defined response times. WhatsApp, same timezone.
Your history comes with you.
Field-mapped migration of sales, invoices, payments and deliveries. You keep your past (customers, balances, stock movements) and you keep it queryable. No "fresh start" that quietly means "lost records".
We don't disappear at cutover.
Support tiers with defined response times, proactive monitoring on hosted systems, and compliance updates tracked for you. Mauritius-based, same timezone, reachable on WhatsApp.
How ERP projects usually die.
Requirements drift because nobody wrote down what "done" means. Our fix: Discover ends with a fixed-scope quote, and changes after that are new decisions, not silent additions.
Everything looks fine with ten imaginary products; reality arrives at migration. Our fix: from Configure onwards, every demo runs on your real SKUs, pricelists and customers.
The system works; the people at the counter were shown it once, a month ago. Our fix: Train is its own gated phase, role by role, at the counter, and go-live waits for it.
Your side of the project.
An implementation is not something done to a business; it's done with one. Discover needs the owner and the key staff in the room: the cashier who knows which workaround everyone actually uses, not just the org chart. Configure needs a champion on your side: one person empowered to answer "how should this work?" without convening a committee. Migrate needs your old data in whatever state it truly is. Messy exports are normal, hidden ones are the problem. And Train needs the counter, the stockroom and an hour of each person's shift, in their own workplace rather than a meeting room.
None of it is heavy: a few hours a week from the right people. But projects where the client is a spectator are the ones that stall, so we're upfront: if nobody on your side can own it, the honest advice is to wait until someone can.