Digital products for government
Secure, reliable public services, built alongside your team and explained in plain English. We take on the complexity without making it your problem.
A technology partner you can rely on.
Sound familiar?
You have been here before. A supplier who went quiet, a project that overran, or public money spent with little to show for it. Meanwhile the users are the public, the information is sensitive and the systems are old. Much of the difficulty isn’t technical, but the security has to be right from the outset.
The supplier went quiet
The last project started well, then the updates thinned out and the deadline slid. By the time you found out, the budget was spent and the explanation was full of jargon.
The old system nobody dares touch
A service runs on software older than most of your team, and the person who understood it has left. Every change feels risky, so nothing changes.
Nobody can answer the security questions
Your assurance team asks where the data lives, who can access it and how it’s encrypted. The answers come back vague, so the project stalls before it starts.
What we build
What we build for government
Practical services for the people who run them and the people who use them. Everything is accessible, secure by design and documented, so your team can run it after we leave.
01
Secure case-management tools
Internal tools that show a caseworker everything about a case in one place, with clear next steps and an audit trail. Access is controlled by role, and records are encrypted in transit and at rest.
Case queues
Role-based access
Audit trails
02
Citizen-facing services
Online services built to the GOV.UK Service Standard and tested with the people who’ll use them. They replace PDF forms, phone queues and email back-and-forth.
Applications and claims
Booking and appointments
Status tracking
03
Safeguarding and anonymisation workflows
Systems that remove names, dates and locations from sensitive submissions before a person reads them. We built this for Everyone’s Invited, where it has reviewed over 50,000 submissions.
Automatic redaction
Review queues
Secure submission forms
04
Legacy modernisation
We work out which parts of an old system are genuinely holding you back, then replace those parts one at a time. The service keeps running while it improves.
Data migration
APIs over old systems
Secure cloud hosting on AWS
Public sector work we’ve delivered
Digital Outcomes and Specialists 7
Buying a digital product from us, the public sector way
Product development
AI + data
Infrastructure + security
Secure prototyping for the public sector
Proving an idea safely, before anyone commits to scaling it
Product development
Infrastructure + security
Everyone's Invited
Safeguarding children in schools with AI
AI + data
Product development
Design + branding
Infrastructure + security
- The problem
A safeguarding charity taking more than 100 submissions a day, each one needing names, dates and locations removed by hand before anyone could read it. The site also had to survive sudden national attention without falling over.
- What we built
We built an AI submission system that strips identifying detail automatically. Their team got a CMS they can run without a developer. The site moved to serverless infrastructure that scales with the traffic.
- What changed
Over 50,000 submissions reviewed automatically, and roughly 12,500 hours of manual anonymisation removed from the process.
How it works
How a project runs
We follow the GDS phases, so each one ends with evidence and a decision rather than a sunk cost. Timings are agreed per phase, once we understand the work.
01
Discovery
Typically a few weeks
We research the users, the policy, the systems you already have and the security requirements. You get a clear view of the problem, and an honest answer on whether to build anything.
02
Alpha
Typically a few weeks
We prototype different ways of solving the problem and test them with real users. The aim is to find what works before committing to build it.
03
Beta
Agreed per phase
We build the real service, assess it against the Service Standard and open it to users in stages. Accessibility and security testing run throughout, not at the end.
04
Live
Ongoing
The service is running and supported, and we keep improving it from real usage. When you’re ready, we hand over to your team with the code and documentation.
What you should expect from us
Government technology has to work properly, reliably and securely.
We can handle the complexity without making it your problem.
We’ll tell you what we think, not just what you want to hear.
We take data protection, encryption, access control and secure infrastructure seriously.
We work alongside your team rather than disappearing into a development process.
We care about the people who will actually use what we build.
Complexity is the job, not the excuse
Large user numbers, highly sensitive information, legacy systems, many stakeholders and a budget that has to be justified. We explain what needs to happen in plain English, and we say early when something isn’t working. From the first conversation, we can show you how your information will be protected.
Confidence in complex projects
Security is part of the plan from the first conversation.
We set out the security requirements, the risks and the decisions needed to protect sensitive information before any build starts. We encrypt data in transit and at rest, control access by role, and show how each measure fits the wider system. We’re an approved supplier on Digital Outcomes and Specialists 7, through the Government Commercial Agency.
Technology that works for people
The public didn’t choose to use it.
Public-sector technology has to work for the people using it, not just the organisation commissioning it. Accessibility is a requirement, not an audit at the end. The test is whether someone can finish the task on a bad day, on an old phone, with no help available.
Modernising with purpose
Not everything needs replacing.
A full rebuild is sometimes the right answer, and often an expensive way to end up where you started. We look at what you have, name the parts genuinely holding you back, and leave the rest alone. We won’t invent a problem so we can sell you the fix.
A proper partner
We stay responsible for the relationship, not just the code.
You work with the same people throughout, and you get a straight answer when you ask for one. The handover leaves your team able to run the service without us. We stay reachable afterwards, because projects are judged years after the final invoice.
Confidence in complex projects
Security is part of the plan from the first conversation.
Technology that works for people
The public didn’t choose to use it.
Modernising with purpose
Not everything needs replacing.
A proper partner
We stay responsible for the relationship, not just the code.
Questions people ask
How do we buy from you?
We’re an approved supplier on the Digital Outcomes and Specialists 7 (DOS7) framework, through the Government Commercial Agency (GCA). You can run a call-off under the framework and invite us to respond. If you’re unsure which route fits your budget and timeline, talk to us first. We’ll explain the options plainly.
How do you protect sensitive data?
We plan security from the outset, not after the build. Data is encrypted in transit and at rest, access is controlled by role, and sensitive actions are recorded in an audit trail. We collect only what the service needs. We document how each measure fits your wider system, so your security and assurance teams can review it properly. Through our Secureframe partnership, we can also get you ready for ISO 27001 and SOC 2 Type II.
Will the service meet accessibility requirements?
Yes. We build to WCAG 2.2 AA, the level public sector websites and apps are expected to meet. We check with screen readers and keyboard-only navigation as we build, not in an audit at the end. If an issue remains at launch, we record it in your accessibility statement with a date for the fix.
Who owns the code?
You do. The code, the designs and the documentation belong to you, and they live in repositories you control. That means you can bring the work in-house, hand it to another supplier or publish it openly. You’re never locked in to us, and we’ll make the handover easy if you move on.
Can you work in the open?
Yes. The Service Standard asks teams to make new source code open unless there’s a good reason not to, and we’re happy to work that way. We can publish code, write weeknotes and run show-and-tells your stakeholders can join. Anything sensitive, such as security configuration, stays private.
Do you work with legacy systems?
Yes, and we don’t assume they need replacing. We map what the old system does, find the parts genuinely causing problems, and often put a modern layer in front of them. The service improves while the system underneath keeps running. You replace it only when that’s worth the money.
Got a service that has to work properly?
Tell us what you’re dealing with, including the security requirements. We’ll give you an honest view of where to start, even if the answer is a smaller job than you expected.
Our newsletter
Occasional emails about what we’re building and what we’ve learned the hard way
You may unsubscribe from these communications at any time. For information please review our privacy policy.