Government and enterprise
Your work, your files, your rules about where they sit.
Training built around the department's own tools, systems that do the department's own work, and infrastructure that keeps its data where the rules say it must stay.
Public sector and enterprise teams rarely need a general course about AI. They need to know what it does to their own workflow, with their own files, under their own rules about where the data may sit.
Formats
A day, or six weeks.
That is why the shortest engagement is a briefing and the longest is a cohort built around what the team already does. Both start from the work rather than from the technology, which is also why they survive contact with the actual job.
Executive briefings
From one day.
Department cohorts
Four to six weeks, built around the team's own tools and files.
Operator workshops
Cobot operator workshops for factory teams.
AI at Work tracks for twelve jobs, including Government and Public Sector, Legal and Compliance, Finance and Analysis, HR and People Ops.
Delivered in Arabic or English, at your offices or our Abu Dhabi campus, across the six GCC countries.
Systems
Agents for procurement, HR and finance.
The work that fills a department's calendar is not the decision itself. It is assembling the file the decision needs, and that is the part a system can do.
The work of a department is documents and approvals. Agents that read the tender against the policy, match the purchase order to the budget and the vendor history, and prepare the file so the director decides only the exceptions. Workflows that route the approval to the right desk with the context attached. Chat and voice agents that answer the public in Arabic and English and log every conversation.
One procurement queue in production today: every purchase order pre-classified against budget, vendor history and policy, so the director sees the four that need a call, not the forty-two.
Where the data sits
Start from the constraint.
Where information cannot leave the building, that constraint shapes everything downstream, and it is usually the question that decides whether a pilot is allowed at all. Raise it first rather than last.
Where the data may sit is not a technical detail to settle later. It decides the architecture, so it is the first question rather than the last.
Where information cannot leave the building, we design for that first. Desk-side machines and servers that hold and run real models on your own network. Nothing goes out, nothing is metered, and nothing depends on a service staying available or staying priced the way it is today. Work, faces and data stay on a machine in your building. No third-party terms and nothing to disclose.
Context
Aligned with the UAE AI Strategy and Vision 2031.
Local trust. Local availability. Regional fluency. An Abu Dhabi team that works from your offices and stays in the region after handover.
How it runs
The constraint first, then the format.
Every engagement here starts from the constraint rather than the catalogue, because a format chosen before the constraint is understood is a format that gets abandoned at the security review.
- 01
Constraint
Where may the data sit, who may see it, which systems are in scope. Settled before anything else.
- 02
Briefing
A one-day executive briefing on what AI does to this department's work, on the department's own examples.
- 03
Cohort or build
A four to six week department cohort on the team's own tools and files, or a scoped first build on one workflow, or both.
- 04
Infrastructure
Where the constraint requires it, the models and the systems installed on hardware the department owns.
- 05
Run
We stay, on a support arrangement, and build the next system on the same map.
Questions
What departments ask.
Can our data stay inside the building?+
Yes. Where the rules require it, training runs on your examples on your premises, and systems run on hardware you own. Nothing goes to a cloud unless you permit it.
Do you deliver in Arabic?+
Yes. Training, chat and voice agents, and documentation in Arabic and English.
How long is a department cohort?+
Four to six weeks, built around the team's own tools and files. An executive briefing is one day.
Where does the training happen?+
At your offices or our Abu Dhabi campus, across the six GCC countries. Where the constraint requires it, on your premises with your own files and nothing leaving the building.
Tell us the department and the constraint. The format follows from those two, and we would rather scope it around a real process than sell a course catalogue.