We are hiring across engineering, design and delivery.
See open rolesA public service is judged on whether somebody could complete it — including somebody on a phone, on a bad connection, who has never seen it before. We build to that, and we build the back office it feeds, because a form that produces work nobody can process has not helped anyone.
The journey end to end, including the offline steps and the people who do them.
Built to WCAG 2.2 AA and tested with assistive technology, not only with a checker.
What happens after submit, tracked to an outcome with the decision recorded.
Proving who somebody is and what they are entitled to, proportionately.
Talking to the system of record that is not going anywhere.
Volumes, completion and drop-off published rather than filed.
High-volume services with a duty to serve everyone who applies.
Programmes with a standard to meet and a spend control to pass.
Specialist services with small teams and long-lived systems.
Multi-agency journeys where the handover is the hard part.
Teams that have worked in this setting, not a generic squad reading the brief for the first time.
The people who design it are the people who build it and the people who answer for it afterwards.
Something running in weeks, so the direction is judged against a real thing rather than a document.
We have worked in this sector, so the first conversation is about your constraints rather than an introduction to the domain. Where we have not done something before, we say so.
Talk to us
Two weeks with the people doing the work, mapping what actually happens rather than what the process document says.
One narrow slice built and put in front of real users, to test the approach before it is expensive to change.
Delivery in fortnightly increments, each one usable, each one reviewed with you.
Support, monitoring and improvement — or a handover to your team, documented.
Tell us what you are trying to do. If we are not the right people for it, we will say so.
Get in touch
© 2026 Myrris. All Rights Reserved.
