Is the organisation ready, or is the ERP being asked to fix something else?
ERP is the most important and most misunderstood category in enterprise technology. Important, because the operating model lives inside it. Misunderstood, because most projects are run as software projects with software success criteria — go-live dates, modules activated, training hours delivered.
The question a strategy answers is narrower and harder: what is this organisation actually trying to change, is it ready to change it, and what is the smallest scope that delivers a measurable operating outcome first. Answering it before selection is far cheaper than discovering it during implementation.
How ERP decisions go wrong before they start.
Selection by demonstration
The platform is chosen on how well a sales team demonstrated it, against requirements nobody wrote down first.
Scope set by department politics
Phase one includes every department because none would accept being second, so nothing reaches depth.
A business case built for approval
Benefits are quantified generously to secure budget and never tracked afterwards.
Readiness never tested
Master data quality, process ownership and decision rights are assumed adequate. All three surface as problems in month four.
No total cost view
Licence and implementation are costed; data migration, integration, change management and year-three support are not.
A metric nobody committed to
The programme has no named operating number, so success becomes a matter of opinion at the end.
What the engagement actually includes.
Readiness assessment
One week on site examining close speed, control gaps, reporting load, master data quality and process ownership. The output answers one question: ready, or not yet, and why.
Requirements definition
Written before any vendor is seen, expressed as operating outcomes and process needs rather than a feature checklist.
Platform selection
Scored against the written requirements, the internal team that will own it, data residency, cost over five years and upgrade path. Documented so the decision can be defended later.
Scope & phasing
The smallest first phase that produces a measurable operating change, and an explicit statement of what waits and why.
Business case
Total cost over five years against benefit expressed in operating metrics, built to be tracked after approval rather than only to obtain it.
Programme shape
Governance, sponsor accountability, gate structure and the internal roles the client must fill for the programme to be ownable afterwards.
Six weeks to a defensible decision.
Selection is scored against written requirements. These are the platforms and considerations that usually appear in a regional evaluation.
Ranges observed on Al Jawad engagements. Your targets are agreed in assessment, before the work starts.
Will you recommend Odoo?
Sometimes. We are an Odoo Gold Partner and that stays visible. Where the requirements point elsewhere, the evaluation says so — we would rather lose an implementation than run one that should not exist.
Can we run selection ourselves and hire you to implement?
Yes, and many clients do. We will tell you honestly if we think the selected platform is wrong for the operation before we sign an implementation contract.
What if the verdict is not ready?
Then we say which organisational work must be sequenced first. An ERP asked to fix a non-technology problem will fail and the failure will be blamed on the software.
How much does the assessment cost relative to the project?
A fraction of a percent of a typical programme, and it routinely changes the scope enough to pay for itself several times over.
Start a conversation.
Choose the one that fits where you are. None of them is a sales call. Each is an advisory conversation calibrated to a specific question.