05
ERP implementation and business systems — client-side consulting
ERP and cloud projects rarely fail on technology. They fail because the client has nobody of their own to decide, so the supplier decides — in its own favour.
Client-side ERP implementation consulting
Client-side leadership of ERP and other business-system implementations, including SAP S/4HANA, and of cloud migrations (AWS, Azure). We are vendor-neutral: our interest is your go-live date, not the number of licences sold.
What you have at the end
- Requirements specification and tender pack with evaluation criteria
- Bid comparison and proposed acceptance terms
- Cutover plan: data migration, test cycles, go/no-go criteria
- A list of deviations from standard, each with a written decision
How we work
How a client-side ERP implementation starts
Standard first, customisation by exception.
Requirements and tender first, then selection, then control of customisation: every deviation from standard needs a written decision. Cutover follows go/no-go criteria agreed in advance. On SAP projects we work to the SAP Activate methodology and the Fit-to-Standard approach; cloud migrations are planned in waves, with lift-and-shift options assessed for each virtual machine.
The first step is normally a delivery assessment: two to three weeks, fixed scope and fixed price, with written findings. Only then do we agree further work, if any is needed. See Engagement models.
Frequently asked questions about ERP implementation
Who leads an ERP implementation on the client's side?
It should be someone who works for you, not for the supplier. That role owns the scope, decides what follows the standard and what gets adapted, and makes sure acceptance is measured against real criteria. Without it, customisations grow and the date moves.
Do you implement SAP or another ERP?
We neither implement nor resell any system. We run the project on your side, whichever system and supplier you have chosen — precisely because we have no stake in that choice.
Do you help select a supplier?
Yes — requirements, tender preparation, comparing bids and negotiating scope and acceptance terms. That is often the part of the work that pays for itself, because that is where the cost of the project is decided.
How long is an ERP implementation engagement?
It depends on where we come in. Before the tender: requirements, the tender pack and supplier selection, agreed as a scope of their own. After signature: a two-to-three-week delivery assessment, then client-side leadership for the length of the rollout — through cutover and acceptance of the solution.
Does your programme look like this? Get in touch or call +381 63 275 615.
Related services
ERP decisions cost least before the contract is signed.
Before the tender: requirements, evaluation criteria and acceptance terms. After signature: a two-to-three-week delivery assessment at a fixed price, with written findings on where the project really stands.