Eight years building the ERP, AI and integration layers that companies across the Kingdom run their daily operations on — and staying accountable for them long after go-live.
Pro Max Gulf started from a gap anyone who has run an ERP programme in the Kingdom will recognise: global platforms arrive with world-class engineering and none of the local reality — Arabic that does not read properly, no ZATCA, no connection to the logistics and payment providers the business already depends on. AI has since arrived the same way: impressive demos with no route to the data that actually runs the company, and no answer for who is accountable when it acts.
We built the practice to close the first gap. Our teams implement and extend Microsoft Dynamics 365 Business Central and Finance & Operations, Odoo and ERPNext — then write the extensions, integrations and compliance layers that make them work here. Seventeen-plus Business Central extensions, ZATCA Phase 2 e-invoicing, OTO and FarEye logistics and a dozen payment gateways came out of that work.
We answered the second gap the same way. Instead of selling pilots, we build governed AI platforms — ZIJ, Intelligent Workforce Resources, AI Code Worker, Smart AI Salesman — that reach your live business data, keep every answer traceable, and let nothing act on your systems until a named person has approved it.
To be the technology partner Saudi enterprises call first — setting the benchmark for digital transformation in the Kingdom through engineering rigour, integrity and operational excellence.
To give organisations intelligent, scalable and genuinely integrated systems that produce measurable business outcomes — and to stand behind them long after the project closes.
Enterprise software fails on process far more often than on technology. Ours is deliberately short, and staffed by the people who will still be there at go-live.
We map the processes you actually run — not the ones in the manual — and agree what go-live has to look like before anyone writes code.
Solution architecture, integration contracts and the data model, signed off in writing. Surprises surface here, where they are still cheap.
Implementation in short visible cycles, with extensions, compliance and integrations built alongside the core rather than bolted on afterwards.
Migration, training in Arabic and English, then monitoring and a support line staffed by the team that wrote the code. Handover is not an exit.
Six commitments we are happy to be held to — each one a thing you can check, not a slogan.
ZATCA Phase 2 runs as a managed platform — certificate lifecycle, monitoring, automatic retry. A regulator change becomes our problem, not your finance team's.
Full RTL interfaces and bilingual documents from the first sprint. Retrofitting Arabic at the end is where most localisation budgets quietly disappear.
ERP, applied AI, custom software and the hardware on the warehouse floor — so there is no integration gap between three vendors pointing at each other.
Role-based access, per-team cost limits and a complete audit trail. Every automated action is attributed to a named person and stays reversible.
ZIJ, IWR, GEO and AI Code Worker are ours. When you need a change it goes on our roadmap — not to a vendor's support queue.
Monitoring on managed platforms with alerting before your users notice, and support from the engineers who built the thing.
The platforms our work is certified on, and the paperwork enterprise procurement asks for — available before you ask.
A short call with the people who would actually run your project — not a sales team. If we are the wrong fit, we will say so.