Techbanq

Public sector · citizen services

A citizen cannot choose another government, so the service has to work for all of them

A commercial product can quietly lose the customers it does not suit; a public service cannot, because the citizen who fails to complete it has no alternative provider and ends up in a queue at a counter. That reverses the usual priorities: accessibility, plain-language Arabic and support for the awkward case are the point rather than the polish, and where the data lives is a design constraint from the first line.

Enterprise delivery credentials

  • ISO

    ISO/IEC 27001

    ISO/IEC 27001 certified

Certifications & registrations

What good means here

A public service has no churn, and that changes what good looks like

We do not have an office in Saudi Arabia

We serve organisations there from our Riyadh office and our engineering hubs in Lahore and Karachi, travelling for the parts of an engagement that need to happen in person.

A commercial product can succeed by serving the customers it suits and quietly losing the rest; the ones it fails switch to a competitor and stop being its problem. A government service has neither luxury. The citizen who cannot complete it has no alternative provider, and their failure does not disappear — it reappears as a queue at a counter, a call to a helpline, a form posted in. The honest measure of a public service is therefore its worst-served user, not its median one: the elderly applicant, the person on a poor connection in a remote area, the one whose name or case does not fit the shape of the form.

That inverts the usual build priorities. Accessibility, plain-language Arabic, flows that tolerate a dropped connection and support for the awkward edge cases are not enhancements added once the happy path ships; on a public service they are the work, because the happy path was never the hard part. And because the data is a citizen’s and the accountability is the Kingdom’s, where and how it is held is a constraint the design starts from rather than a deployment detail settled at the end. Building a public service well is mostly refusing to optimise for the citizen who was always going to manage anyway.

The method

How a counter process becomes a service a citizen can finish at home

Digitising a public service is not putting the old form on a screen. It is redesigning the process around the person who would fail the naive version, then building it on the foundations the wider e-government estate already provides.

STAGE 01

Map the process the counter actually runs

Capture the real path including the exceptions staff handle informally, because the cases the paper process absorbs quietly are the ones a literal online copy drops. The true process, edge cases and all, rather than the one on the form.

STAGE 02

Design for the worst-served first

Build the flow so the hardest user can complete it — the poor connection, the unusual case, the low digital confidence — which is what makes it effortless for everyone else. A service defined by who it must not fail, not who it delights.

STAGE 03

Build on the national rails

Use the shared identity, payment and notification services rather than rebuilding them, so the service fits the estate a citizen already knows and does not ask them to learn a new sign-in. A service that is part of the wider e-government estate, not an island.

STAGE 04

Hold the data in-Kingdom and audited

Design residency and the access trail in from the first line, because retrofitting either onto a live citizen service is expensive and carries a risk the agency owns. A service whose data residency and audit meet the agency’s accountability.

One service

The systems a citizen-facing service has to bring together to feel like one

The citizen should experience a single service; behind it, several systems have to be orchestrated into one flow. The branch is the case a naive service forgets — the citizen whose situation does not fit the standard path.

Four inputs — national identity, agency records, payment rail and documents — converge into one orchestrated journey that produces a completed transaction, an actionable record and a trusted notification, with a branch that routes an unusual case to a caseworker.

  • National identity

    The single sign-on the citizen already uses, rather than a new account per service.

  • Agency records

    The systems of record that hold the facts the service acts on.

  • Payment rail

    The government payment channel, so a fee is paid in a way the citizen trusts.

  • Documents

    Uploads and attestations attached to the case rather than posted or carried in.

What we do

One orchestrated journey

The layer that sequences identity, records, payment and documents into a single flow the citizen reads as one service.

  • A completed transaction

    The citizen finishes without a counter visit.

  • A record the agency can act on

    The outcome lands in the systems the agency runs on.

  • A notification the citizen trusts

    Confirmation through the channel they already recognise.

The citizen should see one service; the integration behind it is the work.

Our role

What we deliver and what stays with the owning agency

  1. 01

    The service, not the mandate

    We build the digital channel; the policy, the eligibility rules and the legal authority behind the service stay with the agency that owns them, and we design to them rather than around them.

  2. 02

    Built on the national rails

    We integrate the shared identity, payment and notification services rather than reinventing them, so the service fits the estate a citizen already uses and does not fragment their experience of government.

  3. 03

    Data where it is accountable

    We design for in-Kingdom residency and a full audit trail from the start; the security sign-off and the acceptance of the risk remain the agency’s, and we build so those decisions rest on evidence.

The mandate, the eligibility policy and the security sign-off remain the agency’s to hold; we build the citizen-facing service and the integration that let the agency deliver that mandate through a channel people can actually finish.

Common questions

What buyers ask

How do you make a service work for citizens with low digital confidence?+

By designing for them first rather than treating them as an exception. The flow is built so the person with the poorest connection, the least familiarity and the most unusual case can still complete it — plain-language Arabic, few steps, no assumed jargon, and a path that survives a dropped connection. Where a citizen genuinely cannot self-serve, the service routes them to assisted help with their progress carried over, so they never start again from zero. A public service designed for its most confident users has failed at the part that was actually difficult.

Can citizen data stay inside the Kingdom under your design?+

Yes, and it is treated as a design constraint from the first line rather than a hosting choice made at the end. The service is architected so citizen data is held to the residency the agency is accountable for, with the access trail that a public record demands built in. We do not hold the data ourselves; we build the service and the controls so it stays where the agency’s policy requires. Retrofitting residency onto a live citizen service is expensive and risky, which is exactly why it is settled before anything is built rather than after a review flags it.

Do we have to replace our existing agency systems to offer a digital service?+

No, and usually you should not. The systems of record an agency runs on hold the facts a service acts on and are expensive to replace; the digital service orchestrates over them rather than supplanting them. We integrate with what exists — the records, the identity rail, the payment channel — and add the citizen-facing flow on top. Replacement of a back-end system is a separate decision, made only where that system genuinely cannot expose its data, and even then sequenced so a citizen service is not held hostage to an internal migration.

Book a working session

A working session that walks one existing counter or paper process end to end, identifying the citizens most likely to fall out of a naive online version and the national rails the service should build on, before any interface is designed.

Start the conversation