A company near KAFD picking a vendor based on the most polished demo is optimizing for the wrong thing entirely.

This step follows a readiness assessment and feeds the RFP. Its job is to narrow a wide field of platforms and implementation partners to a shortlist that genuinely fits, then run a fair, evidence-based evaluation that survives scrutiny from a board asking why this vendor and not that one.

Why demos mislead

A vendor demo shows the product at its best, running rehearsed scenarios on clean sample data. Your business runs on messy data, exceptions and workflows the demo never touched. The gap between the two is where implementations go wrong, which is why we insist on scripted demonstrations built around your actual transactions: your multi-entity intercompany flow, your Arabic invoice format, your specific approval chain, rather than the vendor's standard script.

The Saudi-specific evaluation criteria

Beyond functionality and price, every platform is assessed on how natively it handles the requirements a Riyadh business cannot avoid: ZATCA Phase 2 e-invoicing integration, Arabic-language interface and reporting, Hijri and Gregorian calendar support, GOSI and WPS payroll integration, and a chart of accounts structure that supports Zakat reporting without manual reconstruction. A platform that handles these through expensive customization rather than standard configuration carries hidden cost the license price doesn't show.

Weighing the implementation partner as heavily as the product

In Saudi Arabia the partner matters as much as the platform. The same product implemented by a partner with genuine local delivery experience and by one working from a global playbook will produce very different results. We evaluate partners on referenceable Saudi projects, Arabic-speaking consultants who will actually be on your engagement, and post-go-live support capacity in Saudi Arabia, not just their headline certifications.

A common Saudi scenario

A Riyadh services company with sixty staff has narrowed to Dynamics 365 Business Central and Odoo. On paper both fit. Scripted demos on their real project-costing data reveal that one handles their revenue recognition pattern in standard configuration while the other would need custom development, a difference that only surfaced because the evaluation used their transactions rather than the vendors'.

What you receive

A weighted scoring matrix comparing shortlisted platforms and partners against your prioritized requirements, documented demo findings, a total cost of ownership comparison over five years including licensing, implementation and support, and a clear recommendation with the reasoning laid out so leadership can defend the decision.

Reference checks that go beyond the vendor's list

Every vendor supplies references, and every reference on that list is a satisfied client. The more useful conversations are with Riyadh businesses of similar size and sector that the vendor did not nominate, found through our own network, who will speak candidly about what went wrong as well as what went right. We build that into the evaluation because it is the only source of information the vendor does not control.

Local context

Riyadh manufacturers tend to weight production planning and asset management capability heavily, while Riyadh trading businesses prioritize multi-warehouse inventory and import cost accounting, so the scoring weights are set per client rather than reused.