An ERP project that goes wrong rarely fails on go-live day. It fails earlier, in a phase somebody hurried through because it produced nothing to look at. A written plan guards against that. It tells the owner what should exist at the end of each phase, which makes a skipped one easy to spot.
Who needs to be in the project
Three kinds of people on the client side make the plan work. An owner or director who can settle arguments between departments. A project lead, usually the person who knows the daily work best, who answers the vendor's questions and chases colleagues for theirs. And one key user in each department who tries every release. Without a named lead, each decision waits for the owner, and the owner is busy.
The phases of an ERP implementation plan
Discovery
The vendor sits with the people who do the work and follows real orders, purchases and payments. The result is a short written description of each process, with a list of modules, roles and reports. Read it and correct it; everything later is built on it.
Design
Every screen is drawn and shown before it is built. Click through them with the key users and ask for changes now, while a change means redrawing a box and not rewriting software.
Build in releases
Development arrives in small working pieces, loaded with your own items and customers. Key users try each one and report what is wrong or missing while it is fresh.
Prepare the data
While the build runs, clean the item, customer and supplier lists and agree the date for opening stock and balances. This is the client's work more than the vendor's.
Train by role
Each person learns the screens for their own job, on the live system, in the language they work in. A storekeeper does not need the accountant's session.
Go live
Pick one module and one location, load the opening figures and switch on a quiet day. Keep the old record running beside it for a short, agreed period, then close it.
Support the first month
Fix what real use uncovers, check the first closing against the old books, and only then schedule the next module.
This is how Operix runs its own projects: discovery, design with every screen shown first, weekly releases on your own data, training on the live system in Urdu or English, and support on one WhatsApp number. Payments follow milestones set out in the written quote, so each phase has a visible finish. The modules themselves are listed on the ERP software page.
What each phase should hand you
| Phase | What you should receive | Warning sign |
|---|---|---|
| Discovery | A written process note and module list | Building starts after a single meeting |
| Design | Screens you can click through | You are told you will see it when it is ready |
| Build | A working release at regular intervals | A long silence, then one large delivery |
| Data | Cleaned lists and matched opening totals | Data is left until just before go-live |
| Training | Each role trained on its own screens | One group session for the whole office |
| Go-live | One module live, and a date for closing the old record | Everything switched on in one day |
| First month | A list of fixes, closed one by one | The vendor is hard to reach after handover |
A go-live checklist
- Opening stock counted and entered, godown by godown.
- Customer and supplier opening balances agreed with accounts.
- Every user has a login and has used it in training.
- Printers tested for invoices and challans.
- A decision on what staff do if the internet or power fails during the day.
- A named person on each side to call when something is wrong.
- A date on which the old register or sheet stops.
The first month after go-live
The first days bring a stream of small complaints: a missing field on the challan, a report sorted the wrong way, a user who cannot find yesterday's invoice. This is normal, and it is the most useful feedback the project will get. Keep one list, agree which items are faults and which are new requests, and fix the faults fast. In these weeks staff decide whether the system is on their side.
Watch three things. Whether anyone has quietly gone back to the old sheet. Whether stock in the system still matches a spot count. Whether the first month-end closes from the system's figures alone. If all three hold, the module has landed and the next one can begin.
How long it takes
That depends on the modules, the branches, and how quickly data and decisions come from the client side. We agree the timeline module by module in the written quote, and the first module usually goes live while the others are still being built. Be wary of any plan that moves the whole business in a single switch.
Projects that skip a phase tend to meet the problems described in why ERP implementations fail. The data phase has its own guide, moving from Excel to an ERP, and the order of modules is covered in ERP modules explained. The Sea Keepers ERP shows where such a plan ends: one system running the company's work from the first enquiry email to the final delivery documents. For a plan drawn up around your own business, book a demo.
Questions people ask
What are the phases of an ERP implementation?
Discovery, design, build, data preparation, training, go-live and support after launch. Each should end with something the client approves before the next one starts.
How long does an ERP implementation take?
It depends on the modules, the branches and how fast data and decisions arrive. Operix agrees the timeline module by module in the written quote, and the first module usually goes live before the rest are finished.
Should we go live with all modules at once?
No. Start with one module at one location, let it settle, then add the next. A single switch for the whole business leaves no room to find and fix problems.
Who should lead the ERP project on our side?
One named person who knows the daily work and has the owner's backing to decide. A project with no lead on the client side stalls every time a question needs an answer.
What should be ready before go-live?
Counted opening stock, agreed customer and supplier balances, trained users with their own logins, tested printers and a date for closing the old record.
