AI implementation in Saudi Arabia.
The Kingdom bought a great many AI pilots between 2023 and 2026. Most of them still are not in production, and the reason is almost never the model. This is what it takes to close that gap here specifically.
What we have actually done here.
Our Gulf delivery record is industrial: chemicals, petrochemicals, solvents, plastics and food manufacturing. Those clients are on the wall below and they are the reason we can be specific about ERP integration in a plant rather than general about AI. We have no Saudi government or GRE engagement to point to, and we will not imply one.
Chemicals and petrochemicals, plastics, construction materials, food manufacturing, engineering and industrial services.
How the business case gets written.
Vision 2030
Budget for this work is rarely approved as an AI project. It is approved as a contribution to a Vision 2030 programme, usually localisation, non-oil GDP or digital transformation, and the internal case is written in that language before it reaches a committee. We write the business case in the form it will actually be argued in, including the parts that are about jobs rather than about margin.
Saudization, and what handover means here
Nationalisation is a scored line in a tender rather than a sentiment. The handover doctrine this firm already runs on answers it directly: source code, model weights, prompts and infrastructure configuration transfer to you, and the people who will run the system are in the room while it is designed rather than trained at the end. Where the engagement is scored on knowledge transfer to Saudi nationals, that is a commitment we can put in the contract, because it is what we do anyway.
The systems this actually has to work inside
SAP and Oracle carry most of the Saudi enterprise estate, with Dynamics and Odoo strong in the midmarket, and an AI system that cannot post back into them is a second screen nobody opens. Integration is where these projects are won or lost, which is why it is a named service rather than a phase at the end.
What it costs, and in which currency
Quoted in Saudi riyal (SAR) where you need it to be. The readiness review is free, the assessment that follows is a fixed fee agreed before it starts, and you will leave the first conversation with a range for your own situation rather than a brochure.
Which model, and does it have to be a local one.
Where a procurement expresses a preference for a national model, ALLaM is usually the one meant, and that is a legitimate reason to select it before any technical argument starts. Where it does not, the model is chosen on measurement against your own documents.
What you are agreeing to.
Selling risk mitigation while carrying none of it would be a strange position to hold. These are the terms, stated before you ask for them.
Fixed fee on phase one
The assessment is quoted as a fixed fee before it starts. No hourly overrun on the part where the scope is least certain.
You can stop at the end of any phase
Each phase ends with a written review against criteria set at the start. Stopping there is a normal outcome, not an awkward one. If the assessment says do not build, that is what it will say.
You own what we build
Source code, model weights, prompts, infrastructure configuration and documentation transfer to you. No proprietary runtime and no licensing dependency.
MSA and NDA on request
A standard mutual NDA is available before the first conversation, and a master services agreement before any work begins.
Bring us the pilot that stalled.
Forty five minutes, no charge, and you leave with a scored shortlist whether or not we work together.
You'll leave with 2 to 3 scored use cases, an effort estimate, and an honest cost range, whether or not we work together.