Key Takeaways
- Seven phases: discovery, data model and prototype, build or configure, migrate and integrate, test with real work, go live, then run and evolve.
- Published UK timelines are commonly three to six months for a small business and six to twelve for mid-market before customisation; a phased build can have one module in real use in six to ten weeks.
- Cost is driven by data quality, integration count and decision speed — not by the number of features you licence.
- Four failure modes account for most disasters: dirty data, scope drift, non-adoption, and integrations discovered late.
ERP implementation is the work of getting a system from a signed contract into genuine daily use: mapping how the business actually runs, modelling the data, building or configuring, migrating history, integrating the tools you keep, training people by role, and cutting over without stopping the business. The software is rarely the hard part. The hard part is that implementation is an organisational change wearing a technical costume.
The Seven Phases, and What Each One Produces
| Phase | What happens | What you should hold at the end |
|---|---|---|
| 1. Discovery | Real data, exports and daily routines walked through with the people doing the work | A written map of the current process, in their words, with every workaround named |
| 2. Model & prototype | Data model and clickable screens before any production code | Something you clicked and approved, not a specification you skimmed |
| 3. Build or configure | Two-week increments on a staging system | A working module you can open, on your own data |
| 4. Migrate & integrate | History imported and reconciled; live syncs switched on | Reconciliation reports proving the numbers match |
| 5. Test with real work | Your team runs genuine transactions, not scripted demos | A defect list that is shrinking, and named owners |
| 6. Go live | Cut-over plan, role-based training, parallel run where risk justifies it | A rollback plan you hope not to use |
| 7. Run & evolve | Monthly improvements from the team that built it | A written record of what shipped and what is next |
Phase one is the one most often shortened and the one that decides everything after it. A questionnaire is not discovery. Watching an order move through the business is.
Realistic Timelines
Published UK figures for subscription ERP are commonly three to six months for a small business and six to twelve months for mid-market, before customisation. Larger multi-site programmes run longer.
Those numbers describe the whole system going live at once. A phased approach changes the shape rather than the total: one useful module in real use inside six to ten weeks, then the rest over roughly four to nine months, with each piece earning its keep before the next starts. The total effort is similar; the risk profile is completely different, because you learn whether the thing fits while it is still cheap to change.
What Actually Drives the Cost
- Data quality. Duplicate part numbers, wrong costs, stock that never matched. Cleaning is unglamorous, unavoidable, and the single biggest swing factor in an implementation quote.
- Integration count. Every system that must exchange data — accounting, e-commerce, payments, payroll, couriers, EDI — is a small project with its own failure modes.
- Decision speed. Projects are billed in elapsed time as well as effort. The businesses that finish quickly are the ones that can decide.
- Process change appetite. Every insistence that the software match an existing habit exactly is a customisation. Some are worth it; many are habit.
- Testing discipline. Skipping real-work testing does not save money, it moves the cost to the week after go-live at a worse exchange rate.
On the accounting question: whether implementation costs can be capitalised depends on the nature of the spend and the standard you report under, and it is genuinely a question for your accountant rather than your software supplier. Configuration and training are commonly treated differently from development that creates an asset — get it confirmed in writing before the invoices start.
Choosing an Implementation Partner
The product shortlist gets all the attention and the partner decides the outcome. Six questions that separate them:
- Who is actually doing the work? Names and roles, not a capability statement. Are the people in the pitch the people in the project?
- Show me a discovery output. A redacted process map from a real client tells you more than any case study.
- What happens in month nine? Whoever answers this with a support-queue diagram is telling you the build team leaves.
- What is a change request? Ask for the day rate and the approval process in writing, before signing.
- Whose cloud account, whose code? If the answer is theirs, leaving later is a rebuild rather than a handover.
- What have you told a client not to buy? A partner who has never talked someone out of a module is selling, not advising.
The Four Failure Modes
- Dirty data. Migrate rubbish and you have a faster way to be wrong. Reconcile during migration and run old and new side by side before cut-over, not after.
- Scope drift. Phase one becomes everything. The defence is a defined outcome per phase, live on real data, before the next one opens.
- Nobody adopts it. A system built for the org chart rather than the job. The defence is your team testing every increment on their own data, so by go-live they are using something they shaped.
- Integrations discovered late. The surprise that blows timelines. Every integration should be proven against the live API during discovery, not assumed from a feature list.
If you want the phased version of this run for you, our UK ERP build works exactly this way, and the audit that comes out of phase one is yours whether or not you continue.
Frequently Asked Questions
How long does ERP implementation take?
Published UK timelines are commonly three to six months for a small business and six to twelve for mid-market, before customisation. A phased build puts one useful module into real use within six to ten weeks and rolls out the rest over roughly four to nine months, which lowers risk without changing the total effort much.
How much does ERP implementation cost?
It varies more with your data and integrations than with the software. The swing factors are data cleaning, the number of systems that must exchange data, how quickly you can make decisions, and how much process change you will accept. Ask for year-one total including implementation and the day rate for changes after go-live.
Can ERP implementation costs be capitalised?
It depends on the nature of the spend and the accounting standard you report under, and it is a question for your accountant rather than your supplier. Development that creates an asset is commonly treated differently from configuration and training. Get the treatment confirmed in writing before invoices start.
What is an ERP implementation partner?
The firm that does the discovery, configuration or build, migration, integration, training and cut-over. With subscription ERP the vendor sells the licence and a partner delivers the project, which is why partner selection matters as much as product selection.
Should we go big-bang or phased?
Phased, unless something forces a single cut-over. Phasing lets you discover misfit while it is still cheap to fix, gets value earlier, and gives the team capacity to absorb change. Big-bang concentrates all the risk on one weekend.
Weighing up ERP for your own business?
Book a free strategy call. We walk one real order through your business with you and tell you honestly whether custom, cloud or off-the-shelf fits — including when the answer is “not yet”.
Book a Free Strategy Call