The UAE federal Agentic AI Mandate is not a strategy paper. It is a delivery deadline — 50% of federal services running on agentic AI within two years of the April 2026 directive. Federal entities that treat this as a strategic conversation have already lost time. Those that treat it as a procurement conversation are discovering that procurement without readiness produces contracts that stall in month three. Every entity we have engaged with in the last two quarters arrives at the same realisation: the Mandate is real, the awareness of the Mandate is high, and the readiness gap between awareness and delivery is bigger than any of the initial procurement conversations assumed.
The instinct is to shortlist platforms and issue an RFP. The instinct produces contracts nobody can operate. What actually produces mandate-aligned delivery is measured readiness across five dimensions (use-case clarity, data foundations, governance, technical integration capacity, change-management bandwidth), a shortlist of 3–5 agent candidates scored on value × feasibility × risk × regulatory alignment, and a 90-day execution backlog with named owners and procurement specifications. A11 does that work on a fixed scope in 3 weeks. 50% in two years is a delivery problem, not a strategy problem — and the honest position is that some entities need to sequence a readiness engagement before the procurement conversation, not after.
Six streams,
ending in the mandate backlog signed.
Stakeholder interviews and use-case discovery front-load week 1. 5-dimension readiness scoring and architecture options run through week 2. 90-day backlog and executive readout close week 3.
Stakeholder interviews
12+ structured interviews across the departments in scope. Mandate accountability owner, IT leadership, business unit heads, data stewards, compliance. Coverage signed before Phase 2.
Use-case discovery workshops
Candidate agent use cases catalogued from every department. Service operations, customer service, document processing, compliance workflows — the four patterns the Mandate's year-one review expects to see progress against.
5-dimension readiness scoring
Use-case clarity, data foundations, governance, technical integration capacity, change-management bandwidth — each dimension scored with named evidence per candidate. This is where most engagements do the load-bearing work.
Platform-agnostic architecture options
Architecture patterns aligned to UAE data residency and sovereignty requirements. Where Abu Dhabi Government supplier integration applies, no-code agent platform readiness scored. No vendor lock-in assumed — platform selection is a B20 conversation, not an A11 one.
90-day execution backlog
Priority-ordered backlog with KPIs, named owners, and acceptance criteria per use case. Procurement specifications completed for the top-priority items so B20 build engagements can start inside the sprint window.
Executive readout & mandate evidence pack
Direct executive committee readout with mandate-alignment evidence pack — the document that goes to the next federal review checkpoint or Abu Dhabi supplier assessment. Charter signature scheduled inside the sprint window.
Three weeks.
Three phases.
Duration is fixed at 3 weeks for federal-mandate delivery velocity. Phase count is fixed at 3. Milestones are signed gates — not aspirations, and not conditional on stakeholder availability once the sprint has started.
The assessment,
run to mandate delivery cadence.
Every A11 engagement follows a fixed methodology tuned to your Mandate scope in the first three days. Not a workshop-driven programme; not a maturity-model interview. The sequence that produces mandate-ready evidence in 3 weeks against the federal directive's year-one delivery window.
From mandate awareness
to signed backlog.
A typical pre-engagement state has procurement conversations started, use cases nominated by department heads, readiness assumed adequate, and no mandate-alignment evidence for the next federal review. The engagement produces the evidence pack under decisions that clear both the federal review and your executive committee.
Reference pattern. Some engagements produce a smaller shortlist than the initial nomination suggested — the honest output is 'these 3 are ready, not 8, and the 5 nominated but not shortlisted have specific readiness gaps.' That's a legitimate deliverable, not a failure. The alternative is manufacturing a shortlist that matches the department nomination count and watching most of it stall in delivery.
A UAE federal ministry,
twenty-two to five signed.
Representative pattern for a UAE federal entity responding to the Mandate — 22 candidate use cases across 4 departments, procurement pressure from the review calendar, no structured readiness measurement. Ranges reflect target outcomes NexITC underwrites in scope for this class of engagement. N=1 — illustrative composite, not a specific client.
Five artifacts,
each with signed acceptance.
Every deliverable has documented acceptance criteria signed at engagement kickoff. Nothing more, nothing less.
5-Dimension Readiness Scorecard
Use-case clarity, data foundations, governance, technical integration capacity, change-management bandwidth — scored with named evidence per dimension per candidate. The scorecard the executive committee accepts before backlog work begins.
Prioritised Use-Case Shortlist (3–5)
Candidates scored on value × feasibility × risk × regulatory alignment. Regulatory alignment specifically to federal Agentic AI framework and sector rules. Sponsor sign-off per shortlisted item.
Platform-Agnostic Architecture Options
Architecture patterns aligned to UAE data residency and sovereignty. No-code agent platform readiness scored where Abu Dhabi Government supplier integration applies. No vendor pre-selection.
Stakeholder Map & Executive Readout
Named stakeholder RACI for delivery, governance, and review cycles. Direct executive committee readout with change-management readiness assessment.
90-Day Execution Backlog & Mandate Evidence Pack
Priority-ordered 90-day backlog with KPIs, named owners, and acceptance criteria per shortlisted use case — with procurement specifications completed for top-priority items so build engagements can commence within the sprint window. Paired with the mandate-alignment evidence pack for the next federal review checkpoint or Abu Dhabi supplier assessment: the document that demonstrates progress against the year-one delivery window and closes the loop between assessment output and federal review process.
Six outcome metrics,
measured pre and post.
Success is not "the assessment happened." It is measured against six specific outcomes captured at engagement start and re-measured at the executive readout and 60-day check-in.
Honest scoping.
A11 is a fit when specific conditions are met. It is not a fit when other conditions are — and "the organisation is not yet within the Mandate delivery window" is a legitimate defer-until-later answer we surface before scoping.
Formally appointed CAIO, digital transformation head, or sprint-team lead with delivery accountability. Without a named accountability owner, readiness scoring lands in review cycles A11 was designed to eliminate.
5-dimension scoring is meaningful across 4+ candidates. Below 4, the scoring exercise produces less signal than direct pressure-testing — sequence [[A5|A5 AI Use-Case Due Diligence™]] on the specific candidates instead.
Interview coverage is Phase 1 load-bearing work. Without scheduling commitment for 12+ interviews inside week 1, Phase 2 scoring lacks the evidence base to be defensible.
For federal entities, applicability is direct. For Abu Dhabi Government suppliers, integration scope confirmed. For semi-government or regulated enterprises mirroring the Mandate, mirror-scope agreed upfront. Ambiguity extends Phase 1.
Backlog appetite agreed at commitment level (not exact figure). Without appetite, even signed shortlists become unfunded backlogs — filed, not delivered.
That's A5 AI Use-Case Due Diligence™ — go/no-go verdict on 1–3 specific AI use cases with data readiness, feasibility, risk, KPI depth. A11 is scoped to agentic patterns and Mandate alignment specifically.
That's A13 CAIO-in-a-Box™ — packaged delivery infrastructure for the accountable leader with governance starter pack, training curriculum, and signed charters. A11 assesses readiness; A13 equips the CAIO.
That's B20 No-Code Agent Platform Implementation — first production agent build in 90 days against a signed charter. A11 produces the procurement-ready backlog; B20 builds against it.
That's B22 Citizen Developer Programme — waves of citizen-developer training with agent-building capability transfer. A11 assesses; B22 scales delivery capacity.
Fixed fee.
Milestone-based. No surprises.
Every A-tier engagement is scoped and priced upfront against defined deliverables. Milestones tied to signed gates. Change orders negotiated through the Practice Lead, not surfaced as invoice surprises.
Five, most asked.
Q_01What is the UAE Agentic AI Mandate and how does A11 help?
The UAE federal Agentic AI Mandate is the Cabinet-approved directive issued April 2026 requiring 50% of federal services to run on agentic AI within two years. It is a delivery deadline, not a strategic aspiration.
A11 produces the readiness evidence, use-case shortlist, and execution backlog federal entities need to start work inside the year-one window — and produces the mandate-alignment evidence pack the federal review process expects to see.
For Abu Dhabi Government suppliers, A11 additionally covers integration readiness with the enterprise-wide no-code agent platform rollout. For semi-government and regulated enterprises mirroring the Mandate, A11 applies the same discipline to organisation-specific timelines.
Q_02How does this differ from A5 AI Use-Case Due Diligence?
Q_03Is this only for government entities?
Q_04Do you require a specific AI platform to be in place?
Q_05What happens after A11?
One name.
Six accountabilities.
Specialist consulting means the person who scopes the work is the person who delivers it — with escalation to CEO on any material issue within 24 hours.
Practice Lead — AI
Present at every phase gate, every scope decision, every difficult conversation. Available for 30/60/90-day post-handover check-ins as part of the engagement.
Including scope amendments.
Signs off all 5 deliverables.
With executive sponsor.
Authorised to negotiate.
CEO within 24 hours.
30/60/90-day check-ins.
Peer. Next.
CAIO-in-a-Box™
Peer 3-week engagement for accountable-leader enablement — governance starter pack, training curriculum, signed pilot charters. Sequence: A11 → A13 for entities running organisational readiness first then CAIO enablement; A13 standalone when readiness is already established.
No-Code Agent Platform Implementation
The natural build engagement after A11. Delivers the first production agent in 90 days against the top-priority charter from the A11 backlog — procurement specifications, architecture options, and KPIs carry over directly as scope input.
Citizen Developer Programme
Alternative or complementary next engagement — waves of citizen-developer training with agent-building capability transfer. Sensible when the mandate delivery window requires scaling agent-building capacity across teams rather than sequential single-agent builds.
30 minutes.
One Mandate question.
Bring the specific Mandate question blocking your agentic AI programme — federal review deadline approaching, procurement conversations started without readiness, use cases nominated but unscored, CAIO newly appointed. A11 is scoped in the clinic — Mandate scope, stakeholder access, timeline, prerequisites. If A11 is not the fit (readiness already scored, or CAIO enablement is the actual need), the clinic surfaces which engagement is.
- —Mandate scope confirmation
- —Stakeholder access sizing (12+ interviews)
- —Use-case candidate count check
- —Fit assessment against A5, A13, B20