Industry 14 / Public sector
Public software is judged on whether the least confident user can complete the task. Accessibility and documentation are requirements here, not improvements.
Start a project →Where it usually breaks
01
Universal accessibility
The service must work for every citizen, on old devices and assistive technology.
02
Procurement constraints
Scope, reporting and evidence obligations are fixed before work starts.
03
Legacy integration
Records live in systems that predate the web and cannot be switched off.
04
Transparency
Decisions and data handling have to be explainable to the public.
What we build
01
Citizen portalsApplications, payments and status tracking.
02
Case managementWorkflow, assessment and decision recording.
03
Licensing systemsPermits, renewals and inspection scheduling.
04
Internal platformsTooling for caseworkers and administrators.
05
Open dataPublished datasets and documented APIs.
06
Legacy integrationBridges to existing systems of record.
Stack we use here
ReactNode.js.NETPostgreSQLAzureTerraformGOV-style patterns
How we approach it
We build to WCAG AA and test with assistive technology rather than a checklist. Everything ships with the documentation and evidence procurement requires, produced as we go rather than at the end.