Situation
The operating reality
The existing service estate was a patchwork of forms, PDFs, and call-center flows. Citizens routinely abandoned applications mid-flow, and call-center volume was outpacing budget.
Case study · Government
A citizen-services portal a million people could actually use
Designed and launched a citizen-services portal handling 1.1M monthly active users, with offline tolerance, accessibility conformance, and a 4.2× drop in call-center load.
Anonymized delivery dashboard
Government outcome cockpit
MAU
1.1M
Call-center load
−76%
WCAG conformance
AA
Before
Constraint
Build
Controlled cutover
After
Measured gain
- Client
- National government agency
- Industry
- Government
- Service
- Web Development
- Engagement closed
- March 2025
Storyline
From constraint to measurable change.
Every engagement is framed around the business situation, the constraint that made it hard, and the decision that turned delivery into a controlled path to value.
Constraint
Why it was hard
The existing service estate was a patchwork of forms, PDFs, and call-center flows. Citizens routinely abandoned applications mid-flow, and call-center volume was outpacing budget.
Decision
The path we chose
Mapped citizen journeys end-to-end, including offline steps, before deciding what the portal should digitise.
Build
Service-design before software-design
Each citizen journey was mapped end-to-end — including the offline steps — before any screen was drawn. The portal explicitly designed for the journeys it could not fully digitise.
WCAG 2.2 AA conformance was audited externally before launch. Forms worked on low-bandwidth mobile, were resumable across sessions, and degraded gracefully when JavaScript failed.
Outcome
Measured impact
Sustained 1.1M monthly active users within six months of launch.
Call-center load on the digitised services dropped 76%.
What changed after launch
New behavior
Citizens could complete core services on low-bandwidth mobile, while the agency saw call-center pressure fall sharply.
Outcome
The numbers that mattered.
- MAU
- 0.0M
- Call-center load
- −0%
- WCAG conformance
- AA
“The service finally worked for citizens with older phones, patchy connectivity, and no patience for government complexity.”
Before and after
The transformation the client could see.
The work was not abstract modernization. It changed day-to-day behavior, ownership, and the evidence leaders used to make decisions.
Public service platform
Before
- Patchwork of PDFs and forms
- High abandonment mid-application
- Call-center volume outpacing budget
After
- Resumable mobile-friendly journeys
- 1.1M monthly active users
- 76% lower call-center load
Architecture and delivery
A controlled path from discovery to launch.
The delivery plan made the system boundary explicit, then used rehearsals, gates, and telemetry to optimize safely before launch.
Delivery architecture
Government control loop
Discover
Service-design before software-design
Each citizen journey was mapped end-to-end — including the offline steps — before any screen was drawn. The portal explicitly designed for the journeys it could not fully digitise.
Launch
Accessibility and resilience
WCAG 2.2 AA conformance was audited externally before launch. Forms worked on low-bandwidth mobile, were resumable across sessions, and degraded gracefully when JavaScript failed.
Build
How we shaped the work.
Service-design before software-design
Each citizen journey was mapped end-to-end — including the offline steps — before any screen was drawn. The portal explicitly designed for the journeys it could not fully digitise.
Accessibility and resilience
WCAG 2.2 AA conformance was audited externally before launch. Forms worked on low-bandwidth mobile, were resumable across sessions, and degraded gracefully when JavaScript failed.
What changed after launch
What shipped, and what it changed.
- Sustained 1.1M monthly active users within six months of launch.
- Call-center load on the digitised services dropped 76%.
- Independent WCAG 2.2 AA audit passed at launch and re-confirmed at six-month review.
After launch
Citizens could complete core services on low-bandwidth mobile, while the agency saw call-center pressure fall sharply.
Stack
What we built it with.
Next.js
TypeScript
NestJS
PostgreSQL
Azure
Cloudflare
Related case studies
View all workSimilar delivery patterns.
A similar problem?
Let’s talk about your project.
A senior engineer will follow up within one business day with an opinionated take on the shape of the work.