The service stops halfway
A citizen applies online, then waits for a call, a visit or a stamp. The digital part covers the request, not the decision.
Government & Public Sector
Public services that finish online
Citizens should not need to visit a counter for a form, a status update or a certificate. We build the portals, the workflows behind them and the integrations that make an e-service genuinely complete.
- Nafath sign-in
- Hosted inside the Kingdom
- Arabic-first and accessible
- NafathNational sign-in integrated
- KSAData stays in-Kingdom
- WCAG 2.2Accessibility standard we build to
Why an e-service still sends people to a counter
Most public services are partly digital already. The gap is in the middle — the approval that still travels on paper, the department that cannot see the same record, the form that fails on a phone.
01 02 Departments cannot see the same file
Each unit keeps its own system and its own copy, so status questions get answered by phone instead of by the portal.
03 Arabic and accessibility come last
Interfaces built English-first read awkwardly in Arabic, break on right-to-left layouts, and fail screen readers entirely.
04 Reporting is assembled by hand
Performance figures are collected in spreadsheets at the end of the month, which is too late to act on and easy to dispute.
What we build
Systems for public entities
Each one built to be handed over to your team with the source code and documentation.
Citizen e-service portals
Apply, pay, track and receive the outcome online — with a status the applicant can actually follow and notifications at each step.
Nafath & national integrations
Single sign-in through Nafath, plus the integrations your service needs — Absher, Etimad, the Government Service Bus and sector registries.
Digital workflows & approvals
Routing, delegation, SLA timers and a full audit trail, so an approval moves through the entity without leaving the system.
Dashboards for decision makers
Live figures on volume, processing time and bottlenecks — the numbers that drive your digital maturity score, visible daily.
Mobile services
Apps and mobile-first services for the people who will never open a desktop browser, including notifications and digital documents.
Legacy modernisation
An old system that works but cannot be extended gets an API layer and a modern interface, without a risky rip-and-replace.
Rules we build around
Public-sector work is judged on compliance as much as on the interface. These are scoped into the requirements before development begins.
DGA standards & digital maturity
Interfaces, service design and measurement aligned with Digital Government Authority guidance, so the service scores well on assessment.
Data classification & PDPL
Data classified and handled per NDMO policy and the Personal Data Protection Law, with access control and retention documented.
In-Kingdom hosting
Deployment in Saudi cloud regions or your own data centre, meeting cloud computing regulatory requirements for government data.
The services behind this work
Every system above is delivered by the same technology team. These are the services most often involved — each with its own page.
Web Development
High-performance corporate websites, portals and e-commerce platforms that are fast, secure and built to rank on Google.
Custom Software
Tailored ERP, CRM and business systems designed around your workflows to boost efficiency and scale with you.
Cloud Solutions
Secure cloud migration, managed hosting and DevOps pipelines that keep your systems fast, stable and always available.
UI/UX Design
User-centered interfaces and experiences that look stunning, feel intuitive and turn visitors into loyal customers.
FAQ
Questions from public entities
Yes. Most of our public-sector work is integration rather than replacement — connecting a new front end to systems that already hold the data, through the Government Service Bus or direct APIs, with your IT and security teams involved from the first workshop.
We register and bid through Etimad like any other supplier, and we can provide the technical documentation, staffing plan and local content details that public tenders require.
That is how we build it. Standard, mainstream technology, documented code, handover sessions and your own repositories and cloud accounts — a support agreement with us stays optional.
Have a service that is still half offline?
Tell us which step still requires a visit, a call or a signature. That is usually where the project starts.