In the past six months, federal and Abu Dhabi entities across the UAE have appointed Chief AI Officers, digital transformation heads, or sprint-team leads with accountability for delivering against the federal Agentic AI Mandate. Most arrive to the same reality: no scored use-case portfolio, no operational governance framework, no training plan for the staff who will operate the agents, and a 90-day sprint deadline against which everything must be visibly moving. The role is real. The delivery infrastructure to execute the role is not.
The instinct is to schedule a training programme and hire an external adviser. The instinct produces an inspired office that ships nothing in the first quarter. What actually enables a new AI office to deliver is compressed infrastructure — a scored agent portfolio, a governance starter pack operational within 30 days, a training curriculum with the first cohort scheduled, and 1–2 pilot charters signed inside the sprint window. A13 compresses what a new AI office needs in its first quarter into three weeks. The delivery infrastructure, not the training programme — and the honest position is that entities without a named accountable leader should defer A13 until that appointment lands.
Six streams,
ending in the AI office operational.
CAIO intake and entity capability scan front-load week 1. Portfolio scoring, governance tailoring, and training design overlap week 2. Charter signing and executive readout close week 3.
CAIO intake session
Accountable leader onboarded. Mandate scope, sprint deadlines, federal review checkpoints, and delegated authority named. The delivery brief signed before Phase 2.
Entity capability scan
What exists inventoried — people, data foundations, existing AI initiatives, procurement channels, governance patterns already in operation. Gaps against the delivery infrastructure surfaced with specific evidence.
Use-case scoring workshops
Agent portfolio scored on citizen/business impact × feasibility × risk × data readiness. Scoring runs with the department heads whose services the agents will affect — not a central-office exercise.
Governance starter pack tailoring
Decision rights, risk classification, approval gates, audit logging expectations, kill-switch policy — aligned to Cabinet-approved federal agentic AI framework and the emerging standards of the UAE AI and Data Authority. Tailored to entity risk profile.
Training curriculum & first cohort
Certification path aligned to federal AI upskilling programme. Training curriculum designed with roles-based tracks. First cohort scheduled within 30 days of readout — not deferred to a next-quarter budget cycle.
Charter signing & executive readout
1–2 pilot charters drafted with department sponsors and brought to executive committee signature inside the sprint. Direct readout with mandate progress-reporting template adopted by entity leadership.
Three weeks.
Three phases.
Duration is fixed at 3 weeks to match federal sprint cadence. Phase count is fixed at 3. Milestones are signed gates — not aspirations, and not conditional on stakeholder availability once the sprint has started.
The enablement,
run as delivery not training.
Every A13 engagement follows a fixed methodology tuned to the CAIO's scope and mandate context in the first three days. Not a leadership programme; not a training-only sprint. The sequence that stands up a new AI office's delivery infrastructure in three weeks against the federal mandate's year-one sprint cadence.
From newly-appointed role
to operational AI office.
A typical pre-engagement state has an accountable leader appointed, a mandate deadline visible, and no scored portfolio, no operational governance, no training plan. The engagement produces the delivery infrastructure a new AI office needs to be visibly moving on the first Monday of the sprint window.
Reference pattern. Some engagements surface that the entity does not yet have the accountability structure to sustain an AI office — the honest output is 'the delegation is not yet clear enough to signature charters.' That's a legitimate finding, not a failure. The alternative is manufacturing a delivery infrastructure the entity cannot operate.
A federal entity CAIO,
first quarter equipped.
Representative pattern for a UAE federal entity with a newly appointed AI lead facing a 90-day sprint deadline — no governance framework, no scored portfolio, no training plan for affected staff. 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.
Agent Use-Case Portfolio
Candidates scored on citizen/business impact × feasibility × risk × data readiness. Scored with the department heads whose services the agents will affect — sponsor sign-off per shortlisted item.
Agent Governance Starter Pack
Decision rights, risk classification, approval gates, audit logging expectations, kill-switch policy — aligned to Cabinet-approved federal framework. Written to be operated within 30 days, not filed.
Training Curriculum & Certification Path
Roles-based tracks (operators, reviewers, governance) aligned to federal AI upskilling programme. First cohort scheduled within 30 days of readout — not deferred to next-quarter budget.
1–2 Signed Pilot Charters
Full charters with scope, KPIs, owners, acceptance criteria, and procurement path — drafted with department sponsors, signed at executive committee inside the sprint window.
Quarterly Cadence & Mandate Progress-Reporting Template
Quarterly execution cadence with steering committee membership named, decision authorities agreed, and escalation path signed. Paired with the mandate progress-reporting template your entity uses at each federal review checkpoint — the document that demonstrates first-quarter progress against the year-one delivery window and keeps the AI office's activity visible to entity leadership without requiring bespoke reporting work per cycle.
Six outcome metrics,
measured pre and post.
Success is not "the enablement happened." It is measured against six specific outcomes captured at engagement start and re-measured at the executive readout and 30-day check-in.
Honest scoping.
A13 is a fit when specific conditions are met. It is not a fit when other conditions are — and "the accountability structure is not yet clear enough" is a legitimate defer-until-later answer we surface before scoping.
Formally appointed CAIO, DG-Digital, or interim sprint-team lead with executive-signed delegation. Without delegation, charter signature at week 3 lands in a review cycle A13 was designed to eliminate.
Federal entity, Abu Dhabi Government supplier with integration deadlines, semi-government mirroring federal directive, or regulated enterprise with structured agentic AI expectations from regulator. Mirror-scope agreed upfront.
The department heads whose services the agents will affect must engage in Phase 2 scoring workshops. Without departmental engagement, the portfolio does not land — sequence a leadership conversation first.
First cohort scheduling requires committed budget. Deferred cohorts signal the training will not happen. Appetite agreed at commitment level (not exact figure).
Charter signature at week 3 requires executive committee availability inside the sprint window. Signature deferred to a next-quarter meeting signals downstream delivery risk.
That's A11 Agentic AI Readiness & Use-Case Discovery — 5-dimension readiness scorecard, use-case shortlist, 90-day execution backlog. Sequence: A11 → A13 when both are needed; A13 standalone when readiness is already established.
That's A5 AI Use-Case Due Diligence™ — go/no-go verdict on 1–3 specific candidates with data readiness, feasibility, risk, KPI depth. A13 packages CAIO delivery infrastructure; A5 pressure-tests individual use cases.
That's C9 Managed Agent Operations — operational management of deployed agents including monitoring, incident response, continuous improvement. A13 stands up the office; C9 operates the agents.
A13 packages the full delivery infrastructure. If governance, portfolio, and charters are already established and only staff training is needed, B22 Citizen Developer Programme is the direct fit — scaled training delivery with agent-building capability transfer.
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_01How is this different from A11 Agentic AI Readiness & Use-Case Discovery?
A11 is an organisational readiness assessment — 5-dimension scorecard across the entity, 12+ stakeholder interviews, use-case shortlist, platform-agnostic architecture options, 90-day execution backlog.
A13 is an enablement package for the accountable leader — governance starter pack, training curriculum, reporting cadence, and signed pilot charters that a new AI office needs to start executing immediately.
Sequence: entities often run A11 first, then A13. Either can stand alone. A11 answers 'is the organisation ready?' — A13 answers 'is the leader equipped?'
Q_02We do not have a formally appointed CAIO yet. Is this still relevant?
Q_03Does the governance pack align with federal framework requirements?
Q_04Can the training component scale to hundreds of employees?
Q_05What happens after the three weeks?
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.
Agentic AI Readiness & Use-Case Discovery
Peer 3-week engagement for organisational readiness scoring — 5-dimension scorecard, use-case shortlist, 90-day execution backlog. Sequence: A11 → A13 when both are needed; A13 standalone when readiness is already established. A11 answers 'is the organisation ready?' — A13 answers 'is the leader equipped?'
No-Code Agent Platform Implementation
The natural build engagement after A13's chartered pilots. Delivers the first production agent in 90 days against the top-priority charter — scope, KPIs, and acceptance criteria carry over directly as scope input.
Managed Agent Operations
Alternative next engagement for deployed agents — monitoring, incident response, continuous improvement, quarterly release cadence. Sensible once first agents are in production and the entity is scaling toward the Mandate's year-two delivery window.
30 minutes.
One CAIO question.
Bring the specific CAIO question blocking your first quarter — newly-appointed accountable leader, mandate deadline visible, no scored portfolio, no operational governance, no training plan. A13 is scoped in the clinic — mandate scope, delegation status, timeline, prerequisites. If A13 is not the fit (readiness assessment needed first, or accountability structure not yet clear), the clinic surfaces the honest alternative.
- —CAIO delegation and mandate scope confirmation
- —Entity capability quick-scan
- —Charter signature availability check
- —Fit assessment against A11, B20, C9