Every UAE enterprise that deploys a no-code agent platform meets the same wall within six months. IT owns the platform. IT builds the first three agents. Departments queue for the next thirty. Demand outstrips supply by an order of magnitude, and the platform investment starts looking like it produced a very expensive bottleneck.
The instinct at that point is to hire more IT engineers. The instinct is expensive and it does not scale. What scales is enabling the people who understand the workflow — the operations manager who knows why the vendor onboarding process really has seven exceptions — to build the agent themselves, inside the same governance the IT-built agents run under. B22 does that enablement as a programme, not a course. The output is measured in agents shipped and quality scores, not training hours attended.
Six streams,
ending in one wave complete.
Curriculum design and champion selection front-load weeks 1–3. Wave-1 rollout and governance oversight run weeks 4–9. Certification and CoE handover close weeks 10–12.
Curriculum tailoring
Foundation, intermediate, and advanced curriculum tailored to your platform, your governance overlay, and the use-case types citizen developers will build first.
Champion cohort selection
5–8 champions identified per business unit — senior enough to sponsor, credible enough to teach peers. Trained first, before the main cohort.
Wave-1 rollout
25–50 citizen developers through foundation and intermediate curriculum. Hands-on agent labs against real business scenarios, not toy examples.
Governance oversight
Every citizen-built agent passes through the same approval gates and evaluation harness as IT-built agents. Governance overhead measured, not assumed.
Certification
Assessment against acceptance criteria. Certified developers earn platform deployment rights. Uncertified developers get remediation, not participation certificates.
CoE handover
Centre of Excellence operating playbook. Wave-2 launch plan. 30/60/90-day post-handover check-ins with wave-1 certified developers.
Twelve weeks per wave.
Eight minimum. Four phases.
One wave. 25–50 citizen developers. 20+ production agents shipped. Wave-2 runs on the same 8–12 week cadence, handed to the CoE.
Programmes scored,
not on seat count.
Every wave design runs a six-criteria scorecard in weeks 1–2. Each criterion scored 1–5 against evidence from the cohort profile and platform state. Signed by your HR/L&D lead and the platform owner before wave-1 begins.
From ungoverned enthusiasm
to certified builders.
A typical pre-engagement state has AI enthusiasm spread across departments, with a handful of unofficial agent experiments built on unmanaged tools. The engagement puts every citizen builder inside the same governance overlay IT already uses.
Reference pattern. Some organisations retain a small IT-only path for the most sensitive agent classes (identity, financial control) even after citizen developers are shipping. What always changes is that departmental shadow builds stop being the only alternative to the IT backlog.
A government wave-1,
certified and shipping.
Representative pattern for a UAE government or semi-government entity of this scale — 40-developer wave-1 cohort, no-code platform already deployed. 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 wave kickoff. Nothing more, nothing less.
Citizen Developer Curriculum
Foundation, intermediate, and advanced tracks tailored to your platform and governance overlay. Hands-on agent labs against real business scenarios.
Governance Guardrails
Approval gates, evaluation harnesses, and deployment limits for citizen-built agents. Same overlay as IT-built agents — no separate governance for citizen work.
Certification Framework
Assessment criteria, testing rubric, badge issuance, and remediation path for developers who do not pass first time.
CoE Operating Playbook
How the Centre of Excellence runs wave-2 and onward — cohort selection, curriculum updates, quality oversight, sponsor alignment.
Wave-Based Rollout Plan
Wave-1 execution, wave-2 through wave-6 forecast (population, timing, business-unit coverage), and adoption and quality dashboards. The document your executive sponsor uses to defend the programme budget for the next twelve months.
Six outcome metrics,
measured pre and post.
Success is not "the training was well-received." It is measured against six specific outcomes — certified developers, shipped agents, quality scores — captured pre-wave and re-measured at wave close and 60 days post.
Honest scoping.
B22 is a fit when specific conditions are met. It is not a fit when other conditions are. We say so before the wave conversation, not after the commercial commitment.
Ideally [[B20|B20 No-Code Agent Platform Implementation]]. Running B22 without a platform produces developers with nothing to ship into.
Someone who can compel five business units to release 25–50 people from day-jobs for the wave. Programme sponsorship at the operational level does not survive the first schedule conflict.
Certification framework needs to sit inside the enterprise's learning architecture. Without HR partnership, badges get issued and forgotten.
One sponsor per BU with authority to prioritise developer time and deploy shipped agents. Sponsors below the operational-lead level lack the standing to defend developer time when the day-job pushes back.
The team that will run wave-2 and onward. Ideally IT + business-unit membership. If no team is identified, subsequent waves stall — B22 explicitly hands over, does not stay resident.
Sequence B20 No-Code Agent Platform Implementation first, then B22 wave-1 begins as B20 hands over.
B22 produces certified developers who ship agents under governance. For awareness or introductory training, dedicated corporate L&D programmes are a better fit.
If sustained agent demand is under 5–10 per year, a small IT team is more economic than a citizen programme. Programme overhead is real; do not incur it for volumes it cannot pay back.
That's B14 Agentic Workflow Agent Build™ — single-agent build with a dedicated team, not a workforce enablement programme.
Fixed fee per wave.
Milestone-based.
Total wave fee agreed in the scope statement. Not time-and-materials. Not day rate. Every wave is preceded by a scope conversation to ensure fit before commitment.
Five, most asked.
Q_01What is a citizen developer in the agentic AI context, and why does the distinction matter?
A citizen developer is a business user — not an IT engineer, not a data scientist — who builds, tests, and ships their own AI agents on the enterprise's governed no-code platform.
The distinction matters because the alternative is not "IT builds all the agents." The alternative is that departments build ungoverned agents on unmanaged platforms, and the governance conversation happens after the incident, not before.
B22 makes the governed path the easy path.
Q_02How is quality actually managed when non-engineers ship production software?
Q_03How is this different from a general AI training programme?
Q_04Do we need to have deployed an agent platform first?
Q_05What comes after wave-1?
One name
on the engagement letter.
A named Practice Lead is accountable for delivery, commercial outcomes, and the client relationship throughout the engagement. Not a project manager who disappears after kickoff. Not a partner who nods at the SOW and vanishes.
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 per wave.
With executive sponsor.
Authorised to negotiate.
CEO within 24 hours.
30/60/90-day check-ins.
Prior. Peer. Next.
No-Code Agent Platform Implementation
The governed platform B22 developers build on. B22 requires B20 (or equivalent) to be in place before wave-1 begins.
Agentic AI Readiness & Use-Case Discovery
3-week discovery of agent-suitable workflows across business units — often surfaces the initial use-case backlog citizen developers work on in wave-1.
CoE-as-a-Service™
Ongoing CoE support after B22 wave-1 handover — for organisations that prefer to keep an external partner running subsequent waves and governance oversight.
Thirty minutes.
No slide deck.
A structured 30-minute conversation with the Practice Lead. You describe the platform state, the BU coverage, and the CoE readiness. We describe whether B22 wave-1 is the right engagement — and if not, what is.