Client-side ERP implementation assurance
ERP Implementation Consultancy We do not implement. We make sure it lands.
An ERP implementation is the largest discretionary spend most mid-market boards will approve in a decade, and the organisation buying it does the work once while the integrator does it every year. That asymmetry is the problem. Intology sits on your side of the table for the duration and holds the delivery to the plan, the budget and the benefits that were promised in the business case.
We do not implement ERP. We hold no reseller agreements, no partner accreditations and no delivery revenue with any vendor or systems integrator, and we do not bid for the build. That is what allows us to tell you, in week nine, that the plan is not going to work.
What we mean by ERP implementation consultancy
The phrase describes two different trades, and buyers routinely commission one when they need the other.
An implementation partner builds the system. They configure it, integrate it, migrate the data and take it live, and they are paid on the delivery. Most firms selling ERP implementation consultancy in the UK are partners of SAP, Oracle, Microsoft, NetSuite, Infor or IFS, and their advice is shaped by that accreditation whether or not anyone intends it to be.
Intology does the other job. We are the client-side capability that specifies the outcome, governs the programme, manages the integrator relationship, tests the assumptions and tells the board the truth about status. If you need someone to build the system, we are not that firm, and we will say so in the first conversation. If you need someone whose only interest is that it works, that is exactly what we do.
Why ERP implementations fail
The failure modes are consistent, and almost none of them are the software:
- The requirement was never agreed, so scope is renegotiated in every sprint
- Data quality was assumed rather than assessed, and migration becomes the critical path
- The integrator's plan was accepted without a client-side view of whether it is achievable
- Business ownership sat with IT, so the people who have to use it were never engaged
- Testing was compressed to protect the go-live date, moving risk into production
- The business case stopped being tracked the moment the programme started
Every one of those is visible months before it becomes a crisis, to anyone whose job it is to look. That is the job.
The phases of an ERP implementation
Methodologies differ by vendor and partner, but every ERP implementation moves through the same six phases. Knowing which one you are in, and what should already be true before you leave it, is most of the governance job.
Phase 1
Requirements and design
Business processes are defined and mapped to the system. The decisions made here determine the cost of everything that follows, and the most expensive words in an ERP programme are "we will configure that later".
Phase 2
Build and configuration
The system is configured, extensions are developed and integrations to surrounding applications are built. Scope discipline is the control that matters, because every accepted change here compounds through testing and training.
Phase 3
Data migration
Extract, cleanse, map, load, reconcile, repeat. Data is the single most underestimated phase in ERP delivery and the most common reason a go-live date moves. It should start in month one, not month nine.
Phase 4
Testing
System, integration, performance and user acceptance testing. Compressing testing to protect a date does not remove the defects, it moves them into production where they cost more and are seen by customers.
Phase 5
Cutover and go-live
The rehearsed sequence that takes the business from the old system to the new one, including the fallback plan. A cutover that has not been rehearsed end to end is a plan, not a capability.
Phase 6
Hypercare and benefits realisation
Stabilisation, defect burn-down and the return to business as usual, then tracking the benefits the business case promised. Most programmes declare victory at go-live, which is the point at which the value has not yet been earned.
What Intology does on an ERP programme
We take the client-side roles that decide whether the investment pays back:
- Implementation assurance: independent review of plan credibility, readiness and reported status
- Client-side programme leadership, including interim programme director where the role is vacant
- Systems integrator management: statement of work, milestones, change control and the difficult conversations
- Requirements and design governance, so scope is decided rather than drifted
- Data migration governance, with reconciliation evidence rather than assurances
- Test strategy oversight and go-live readiness assessment against agreed criteria
- Business readiness, training and adoption planning through the Embedded Change Model
- Benefits tracking from business case through to realisation
On most engagements Intology is a small senior team alongside your people, not a parallel delivery organisation. The integrator still builds the system. We make sure what they build is what you agreed to buy.
How Intology engages
Before the build starts is where we add the most value and cost the least. A four to six week readiness and governance engagement before contract signature sets the requirements baseline, tests the integrator's plan, fixes the statement of work and establishes the reporting the board will rely on for the next two years.
During delivery we run continuous assurance alongside your programme, with a defined cadence of gate reviews and a standing seat at the steering committee. The output is a board-ready view of whether the programme will hit its dates, its budget and its benefits, and what needs to change if it will not.
When a programme is already in difficulty we run a recovery: rapid diagnosis, stabilisation and a re-baselined plan the board can stand behind. That work is described on our programme recovery page and typically stabilises a distressed programme inside 30 days.
Selection, implementation, recovery: which one you need
These are three different engagements and buying the wrong one wastes a quarter.
If you have not chosen a platform, you need a selection. Requirements, market analysis, weighted scoring, demonstrations and a board-ready recommendation. Where the scope is enterprise-wide that is an independent ERP selection; where it is confined to the general ledger, consolidation and reporting it is a finance system selection; and where you are testing the market for a service or partner rather than a product, it is an RFP or RFI process.
If you have chosen and are about to build, or are already building, you need what this page describes: client-side assurance and governance holding the integrator to the plan.
If the programme has already slipped twice and the board has stopped believing the reporting, you need programme recovery before you need anything else.
What you receive
Every engagement produces evidence a board can act on, not a commentary.
- An independent assessment of plan credibility against scope, resource and dependency reality
- A requirements baseline with a change control process the integrator has signed up to
- A reviewed statement of work with milestones, acceptance criteria and remedies that mean something
- Gate review reports at each phase boundary, with a clear recommendation to proceed or hold
- Data migration reconciliation evidence rather than assurances
- A go-live readiness assessment against criteria agreed before the date was set
- Board-ready reporting on schedule, cost, risk and benefits confidence
- A benefits tracker maintained from business case through to realisation
- A documented lessons and handover pack at closure
Who we work with
Intology works with FTSE-listed companies, PE-backed businesses, mid-market organisations and UK public sector bodies, typically £25m to £2bn revenue or equivalent public sector budget. Over fifteen years we have delivered more than one hundred programmes for over fifty clients.
Engagements are staffed with senior practitioners only. The people reviewing your integrator's plan have run programmes of that size themselves, on the client side, and have signed off go-live decisions with their own name against them.
Frequently asked questions
The questions UK boards and CFOs most often ask before commissioning client-side ERP support.
Do you implement ERP systems?+
What is ERP implementation?+
Why do ERP implementations fail?+
When should we bring in independent assurance?+
Which ERP platforms do you cover?+
Can you manage our systems integrator for us?+
Our ERP programme is already in trouble. What happens first?+
How is this different from your ERP selection service?+
How is the work priced?+
About to sign, or already slipping?
Tell us where the programme is and who is delivering it. We will tell you honestly whether you need assurance, client-side leadership, or a recovery, and if the programme is in good shape we will tell you that too. The initial conversation is free and carries no obligation.