Industries

Public Sector

Accessible, procurement-friendly delivery — and a paper trail.

Public sector software has three constraints most vendors treat as paperwork: accessibility, procurement, and the fact that the service must work for someone on a ten-year-old phone in a queue. We build to WCAG 2.2 AA as a floor, deliver in increments a procurement officer can actually contract, and document everything the audit will ask for.

Book A Call Run the numbers first

Google Cloud for the public sector

We build on Google Cloud where data residency and assurance allow, and on open standards elsewhere. Cloud Run, BigQuery and Vertex AI cover most service-delivery workloads; where a jurisdiction requires a sovereign or in-country arrangement, we design for that constraint from the architecture stage.

01 · Intake

Cloud Run · Accessible forms

A service that works on a ten-year-old phone in a queue.
02 · Case

BigQuery

Case state, correspondence and entitlement in one place.
03 · Decide

Document AI

Routine determinations automated; exceptions to an officer.
04 · Publish

WCAG 2.2 AA · Conformance log

The accessibility statement is generated from the build.

SASB-aligned — no published standard for public agencies

SASB standards ↗

SASB does not publish a standard for public administration. These KPIs are adapted from the closest published metrics (TC-IM for infrastructure, FN-CB for data security) plus WCAG 2.2. They are a defensible starting set, not a compliance claim.

Adapted — TC-IM-130a.1
Service footprint

energy consumed (GJ), % grid, % renewable

Cloud billing exports already carry region and service; we turn them into a per-service intensity figure.
WCAG 2.2 AA
Digital accessibility

% of pages conforming, open defects by severity

Automated axe checks in CI plus a manual review log, published as a conformance statement.
Adapted — FN-CB-230a.1
Data security

breaches, records affected, % involving PII

Citizen data holdings mapped to a register, with access logging on every store that touches it.
Records management
Retention compliance

% of records within retention schedule, exceptions logged

Retention rules encoded as metadata with automated disposition, so the annual return is generated rather than assembled.

Sustainability disclosures, their SASB code, the metric and how we would instrument it
Standard	KPI	Metric	How we instrument it
`Adapted — TC-IM-130a.1`	Service footprint	energy consumed (GJ), % grid, % renewable	Cloud billing exports already carry region and service; we turn them into a per-service intensity figure.
`WCAG 2.2 AA`	Digital accessibility	% of pages conforming, open defects by severity	Automated axe checks in CI plus a manual review log, published as a conformance statement.
`Adapted — FN-CB-230a.1`	Data security	breaches, records affected, % involving PII	Citizen data holdings mapped to a register, with access logging on every store that touches it.
`Records management`	Retention compliance	% of records within retention schedule, exceptions logged	Retention rules encoded as metadata with automated disposition, so the annual return is generated rather than assembled.

Where we help

Services that pass accessibility review: WCAG 2.2 AA implemented in the component layer, with automated checks in CI and a manual screen-reader pass per release — not a remediation project at the end.
Case work that removes steps: Case management, forms and correspondence digitised so an officer handles the exception rather than the routine. Every automated decision is logged and explainable.
Procurement-shaped delivery: Scoped phases, fixed acceptance criteria and a handover pack — including the source, the runbooks and a training session — so the capability stays after the contract.

Working on something in Public Sector?

A 30-minute call is usually enough to work out whether this is a quick win or a rebuild — and we will tell you if it is the second one before you spend anything.

Book A Call

Calculator

What is manual case handling costing the service?

Most case work is routine until it is digitised. Model the officer hours spent on steps a system could take.

Indicative

Public Sector

Cost avoided / year

$443k

Cases handled / year: 69k
Admin hours / year: 23k
Hours returned / year: 8,050

Caseworkers 60

5 3000

Cases per caseworker / week 25

3 150

Admin minutes per case 20 min

5 min 120 min

Fully loaded hourly cost 55 $

Model assumptions

Assumes 46 working weeks and a 35% reduction in administrative handling through forms, integration and automated correspondence.
Excludes any headcount decision — the saving is usually reallocated to case quality, not removed.
Accessibility and audit requirements are costed in, not out.

An order-of-magnitude model, not a quote. We will send the version with your real baselines, the assumptions replaced, and the implementation cost netted out.

Send me the full model

I agree to the Terms and Privacy policy.