- Illustrative example
- Case P-01
- Saudi Arabia
One citizen-services platform for mobile, web and kiosk
In this illustrative example, a 9-engineer squad would build one citizen-services platform for mobile, web and kiosk for a national authority.
No card needed · 72 h free hold
one Arabic-first app across mobile, web and kiosk
In short
Case P-01 is an illustrative example the citizen-services super-app a Remote Pro Ai squad would build for a national authority in Riyadh. A 9-engineer squad, 3 of them on-site, would deliver mobile, web and kiosk channels on one services platform with national identity sign-in and Arabic-first design.
In this illustrative example, a national authority in Riyadh needs mobile, web and kiosk on one platform. A 9-person squad would deliver it in 11 months.
One app for every citizen service
Client (illustrative)
A national authority · Saudi Arabia
Team
9 engineers (3 on-site) · 11 months
Model
Managed Delivery
Data pattern
In-Kingdom hosting
Stack
Flutter · Next.js · .NET · PostgreSQL · Redis · Nafath identity integration · headless Arabic CMS · Kubernetes
Assembled in
4 working days for remote and on-site seats
Citizens verifying their identity again for every service
In this example, citizens reach the authority through separate portals for each service, and service-centre kiosks run different software again. Every channel asks for identity verification on its own, cases are re-keyed between systems, and Arabic content is translated from English after the fact rather than designed for Arabic readers.
The authority wants one platform behind all channels, national identity sign-in once, and an Arabic-first experience. NCA control evidence has to ship with the release, and the squad has to contribute to the authority’s Saudization targets.
- National identity integration through Nafath, with no stored credentials
- Arabic-first content and layout, English as the second language
- NCA ECC-2:2024 control mapping delivered with the first public release
- A Saudi ratio on the squad that counted toward Nitaqat commitments
9 engineers, remote seats assembled in 4 working days
| Role | Level | Count | Location |
|---|---|---|---|
| Squad Lead and delivery manager | Lead | 1 | Riyadh, on-site |
| Flutter mobile engineers | Senior | 2 | Cairo |
| Frontend engineer (web and kiosk) | Senior | 1 | Cairo |
| Backend engineers (.NET) | Senior | 2 | 1 Riyadh on-site, 1 Cairo |
| Identity and integration engineer | Senior | 1 | Riyadh, on-site |
| Product designer, Arabic-first UX | Senior | 1 | Cairo |
| QA automation engineer | Mid | 1 | Cairo |
The 3 on-site seats would be filled by Saudi nationals, giving the squad a 33% Saudi ratio.
Service blueprint first, channels second
Weeks 1–4
Service blueprint with the authority’s product owners, an Arabic-first design system and the NCA control map.
Months 2–5
Nafath sign-in, services API and case engine; the first wave of high-volume services live on mobile and web.
Months 6–8
Kiosk channel and Arabic CMS, with accessibility, security and load testing on each release.
Months 9–11
Public launch in phases, support runbooks and hand-over to the authority’s operations team.
- Operating rhythm
- 2-week sprints · weekly executive report to the programme director every Friday · monthly steering · continuity target: zero unplanned turnover across 11 months.
Results
One
Arabic-first app across mobile, web and kiosk
33%
Saudi ratio on the squad
97%
of milestones on time
- These figures are illustrative
- they show the kind of result this squad model is built to deliver, not a verifiable named-client record. The Saudi ratio counts nationals among squad seats across the engagement. Milestone adherence compares delivery dates with the dates committed in the milestone plan.
About this case
Illustrative example
No client quote: this is an illustrative example
This is an illustrative example. No client is named, and the figures show the kind of result this squad model delivers, not a verifiable named-client record. On a scoping call you can ask for a reference under NDA from a comparable engagement, subject to that client’s consent.
Compliance this squad would handle
- NCA ECC-2:2024 control mapping delivered with the first public release
- PDPL consent capture and data minimisation on every citizen form
- Nafath national identity sign-in, with no credentials stored by the platform
- In-Kingdom hosting for all citizen data and logs
- Saudization (Nitaqat): 33% Saudi ratio across squad seats
Related roles & practices
Frequently asked questions
20 minutes with a solutions architect. No sales script.
The platform would integrate with Nafath, so citizens authenticate once with their national identity and the platform never stores their credentials. A dedicated identity and integration engineer would work on-site with the authority’s identity team, which shortens approval cycles for test environments and production certificates.
The squad lead, the identity engineer and one backend engineer need daily access to the authority’s teams and secured networks. Placing them in Riyadh also lets Saudi nationals fill those seats, which gives the 33% Saudi ratio. The remaining 6 engineers would deliver from Cairo in the same working hours.
The design system, content model and layouts are built for right-to-left Arabic first, with English added as the second language. Arabic copy is written by native speakers, not translated, and every screen is tested in Arabic before English. Kiosk interfaces follow the same design system as mobile and web.
The control map would be built in the first 4 weeks, alongside the service blueprint, so every later sprint produces evidence against named controls. Security and load testing run on each release, and the completed map ships with the first public release. The authority’s security team reviews evidence as it accumulates instead of waiting for an end-of-project audit.
Reach is measured as unique authenticated users from the authority’s identity logs, not app downloads. Because every citizen signs in through Nafath, each person is counted once across mobile, web and kiosk. Milestone adherence of 97% compares delivery dates with the dates committed in the milestone plan.
Launching a public service this year? Let’s scope it
Named candidates within 72 hours, and every seat, remote or on-site, starts within 4 working days.
Build your squad online
No card needed · 72 h free hold
20 minutes with a solutions architect
No sales script.