Information security for software delivery

ISO/IEC 27001
ISO/IEC 27001 certified
Where ERPs fail
Why the ERP that won the demo stalled at go-live
We do not have an office in Saudi Arabia
We serve organisations there from our Riyadh office and our engineering hubs in Lahore and Karachi, travelling for the parts of an engagement that need to happen in person.
ERP selection is decided in a room where a vendor shows clean screens against clean data, and the feature list is the currency. But an ERP does not fail on features; almost none do. It fails when it meets the messy reality it has to run inside: the finance system it must reconcile with, the warehouse process that does not match the module's assumptions, and the hundred people who did their jobs one way on Friday and are asked to do them another way on Monday. The demo tests none of that, which is why it predicts so little.
So we move the project's centre of gravity to where the risk actually is. Before feature choices, we map the integrations the ERP must make and the processes it will change, and we plan the go-live as a sequence of small, reversible steps with the old way still available. The feature list matters, but it is the cheapest part to get right. Integration and adoption are the expensive, decisive parts, and a project that treats them as the main work is one that lands.
The rollout
Bringing in a system the whole operation depends on
Not a single go-live date, but a sequence: integrate first, move one module, bring the people, then repeat — with the old process available until each module has earned trust.
A rollout flow: map the real process, integrate before migrating, move one module live, bring the people — with the old process kept in parallel until each module has earned trust.
- 01
Map the process as it truly runs
Document how the work is really done, including the workarounds staff never mention, before deciding what the ERP will change.
- 02
Integrate before you migrate
Build and test the connections to finance, inventory and the other systems first, because an ERP that cannot exchange data is a silo with a big price.
- 03
Move one module live
Bring a single area — procurement, say — into the ERP while the rest of the operation continues as it was.
- 04
Bring the people, not just the data
Train and support the staff who now work differently, and adjust the module to how they actually operate, because an unused ERP is a failed one.
Keep the old process in parallel
Each module keeps the previous way available until the new one has carried real work long enough to trust. An ERP go-live with no fallback is a bet on being right the first time across the whole operation at once.
What decides it
The four things that determine whether an ERP lands
None of these appear on a feature comparison. All of them decide whether the system the operation runs on is trusted or resented.
Integration into what you already run
The ERP has to exchange correct data with finance, inventory and every system it does not replace. This is the largest hidden cost and the most common reason a go-live slips.
Data migration you can trust
Years of records, with their errors and gaps, have to move into the new system cleanly. Migrating bad data faithfully just relocates the problem into an expensive new home.
Change management as the real work
The people whose jobs the ERP changes decide whether it is adopted. Training, support and adjusting the system to how they work are the project, not a phase bolted on at the end.
A phased go-live, not a switchover
Bringing modules in one at a time, with the old way in parallel, keeps any failure contained to one area rather than stopping the whole operation on a single date.
Our role
What we integrate and what your operation has to decide
- 01
Integration mapped first
We map and build the connections into your existing systems before module work, because the integration surface is what most often decides whether an ERP go-live holds its date.
- 02
A go-live your people can absorb
We phase the rollout module by module with the old process kept in parallel, and support the staff whose work changes, so adoption is built in rather than hoped for.
- 03
The process decisions stay yours
How the operation should work is yours to decide; we tell you honestly where the ERP should fit your process and where your process is better changed to meet a proven pattern.
How your operation should run is a decision only you can make; we build the integrations, phase the go-live and support the change, so the system the whole business depends on is trusted rather than worked around.
Common questions
What buyers ask
Should we build a custom ERP or configure an established ERP product?+
For most organisations, configure an established product and build custom only at the edges. A mature ERP product carries decades of solved problems in finance, procurement and inventory that you do not want to rebuild, plus a compliance and update path you would otherwise own. Fully custom is justified only where your operation is genuinely unlike what the products assume, and that is rare — most businesses that think their process is unique have a standard process with a few real exceptions. The decisive work in either case is the same: integration and adoption, which is where the money and the risk actually sit.
How long does an ERP take, and what makes it slip?+
It varies with the number of modules, the state of your data and how many systems it must integrate with — which is why an honest estimate is scoped from those, not quoted as a flat number. What makes an ERP slip is almost never the software; it is integrations that turn out to be harder than assumed, data that is dirtier than anyone admitted, and adoption that stalls when staff are asked to change too much at once. Phasing the rollout and running the old process in parallel does not make the total work smaller, but it stops a single slipping module from holding the whole operation hostage to one date.
How do you keep the business running while the ERP goes live?+
By never switching the whole operation at once. We bring modules in one at a time and keep the previous way of working available in parallel until the new module has carried real work long enough to be trusted. If a module misbehaves, the affected area falls back rather than the whole business stopping. The trade is that two ways of working run side by side for a period, and reconciling them takes effort, but that is a manageable cost next to the alternative of a single go-live night on which the entire operation has to be right at once.
In this cluster
Next step
Plan the rollout
A programme plan that names the integrations, the go-live order and the change effort per module before feature selection, so the project is scoped on what actually decides it.
Plan the rollout
What happens next
- 1We reply within one business day.
- 2A 30-minute scoping call with a senior consultant.
- 3A written proposal with scope, team, and timeline.
Or reach us directly
