Public sector

We design to WCAG 2.2 AA from the first prototype, write in plain language, and test with keyboards, screen readers and magnification. Automated accessibility checks run in the delivery pipeline, and before major releases we test with people who use assistive technology.

Yes. We respond to tenders and framework requirements, and we can work to fixed or staged scopes with written acceptance criteria. We provide the documentation buyers usually ask for, such as security descriptions, delivery plans and named roles, and we state only what we can evidence. Where a framework sets its own terms, we work within them.

Where your rules say. We work with government or sovereign cloud regions, approved commercial clouds or your own data centres, and we design the system so that you make the hosting decision. Backups, logs and support access follow the same rule, because data often leaves a region through them rather than through the application.

Yes. Many public services depend on long-lived systems. We connect to them through their existing interfaces, files or databases, and put a modern API in front of them where that helps. If a replacement is needed, it happens in stages, with both systems running until the new one is proven.

The number of services and integrations, the identity and payment providers involved, the accessibility and security assessments, and the user research the service needs. We price per stage, so a discovery or a pilot can be approved on its own before the full build.