Problem
ERP projects go wrong in familiar ways. The organisation tries to recreate its old processes in a new system, customisation grows, and the go-live date slips. Data migration is planned late, and testing focuses on screens instead of whole processes.
Outcomes
- An ERP that supports how finance and operations work, with customisation kept to what is needed.
- Clean, reconciled data migrated from the old system.
- Key processes tested end to end before go-live.
- Staff trained and confident on day one.
- A system that can be updated without a major project each time.
Scope
In scope
- Requirements and process design with finance and operations teams.
- Platform selection support, where a choice is still open.
- Configuration and, where needed, extension.
- Data migration and reconciliation.
- Integration with CRM, payroll, banking and other core systems.
- Testing, training and go-live support.
Not included
- Accounting or tax advice. We work alongside your finance team and advisers.
Approach
Discovery
We agree how finance and operations should work, before configuring anything. We also profile the data early, because data quality problems are the most common cause of delay.
Delivery Planning
We plan the build in short cycles, the data migration rehearsals and the cutover. We agree a named finance owner to sign off the reconciliations.
Build and Test
We configure in stages, migrate and reconcile the data with rehearsals, and test whole processes, such as order to cash, with the people who run them. Before go-live, you get the test results and the final cutover plan. A named person then decides whether to go ahead.
Operational Readiness, Hypercare and Closure
We support go-live and the first period-end, and provide extra hypercare for the first few weeks. We then hand over to your team, or stay on, and close the work with your sign-off.
Deliverables
Technologies
Controls
Frequently Asked Questions
Should we customise the ERP to match our processes?
Only where a process gives you a real advantage. For everything else, adopting the standard process usually costs less to run and to update.
When does data migration start?
Early. We profile the data at the start, because data quality problems are the most common cause of delays.
Can you rescue an ERP project that is already in trouble?
Yes. We start with a review of the design, data and testing, then agree a plan to get it back on track.
Do you support the system after go-live?
Yes, through platform support and optimisation, or we hand over to your team with documentation and training.
Planning or rescuing an ERP project?
A Discovery Sprint takes 5 to 10 working days. It ends with a decision brief, a prioritised roadmap, an indicative architecture and a risk register, which you keep whatever you decide next.