Booking vendor demos before assessing your own data and process gaps spends money on the wrong step first.

This is where every serious ERP engagement should begin, upstream of vendor selection. Choosing between SAP, Oracle, Dynamics and Odoo before you know the state of your chart of accounts, master data and finance team capacity is how implementations end up badly late and over budget.

What the assessment examines

The assessment covers four areas, in roughly this order. Data: how reliable your customer, supplier, item and general ledger records are today, and how much cleansing an implementation would require. Process: which of your current workflows are documented and which live in a few people's heads.

People: whether your finance, operations and IT teams have the bandwidth to take part in a project that will take a meaningful share of their working hours. Systems: what you run now, how it is integrated, and what must keep working during a transition.

Why Riyadh businesses need this first

A Saudi implementation carries requirements that a generic readiness framework ignores. These include ZATCA e-invoicing integration and a chart of accounts structured so that Zakat calculation is not a manual reconstruction every year. They also include GOSI and Wage Protection System payroll connectivity, and bilingual Arabic-English reporting for boards and auditors who do not all read the same language.

Assessing readiness against these requirements, instead of a global checklist, makes the output useful.

A hypothetical example

A Riyadh trading group with several legal entities decides to replace its ageing accounting software, and leadership assumes the project is about picking the right product. A readiness assessment would look at whether the entities share one item coding scheme, whether intercompany transactions are reconciled, and who understands the current system. These are data, process and ownership questions, and buying software does not answer any of them.

What you receive

A written readiness report scoring each area, a prioritized list of gaps to close before implementation starts, a realistic view of the internal effort required, and a recommendation on sequencing: proceed now, proceed after specific remediation, or hold. Where the assessment shows you are ready, it feeds directly into the business case and vendor selection that follow.

Why it is worth doing first

An assessment costs far less than an implementation. A project that starts before the organization is ready to carry it is hard to recover, and finding that out before contract signature, not after go-live, is the point.

Deciding what to fix before, and what to fix during

Not every gap needs closing before the project starts. Some, like a missing supplier master, are cheaper to fix as part of data migration. Others, like an undocumented approval process or a finance team already stretched to capacity, will derail the project if left.

The assessment draws that line explicitly, so remediation effort goes where it protects the implementation.