Services
UX/UI design
Screens people can operate, including those who do not use them daily.
An interface that only works if you know how it was meant to be used does not work. So we design from the user's task rather than from the data model — and we settle screens and flows before a line of code is written, because moving a screen in Figma takes minutes and in production takes weeks.
What you get
- A design system and component library that grows with the application
- Prototypes you can click through before anything is built
- Accessibility (WCAG 2.2) from the design up, not as a check afterwards
- Brand carried through to the screen: typography, colour and space
- Handover to developers including sizes, states and behaviour
When this fits
- New staff need a week before they understand the system.
- Every feature that gets added ends up somewhere other than the last one.
- You have accessibility obligations and no idea where you stand.
Accessibility is not an extra
Contrast, keyboard operation and 44-pixel touch targets cost nothing when they are in the design, and cost a rebuild when they have to be added later. For public sector and healthcare clients it is not optional either.
Design and build in one place
We build what we design ourselves. That removes the handover in which half the intent disappears, and it keeps the design honest: we do not draw what cannot be built within the budget.
How a project runs
Scoping
We map what is there, what needs to be added, and where it goes wrong if we misjudge it.
Design
Screens, flows and components are settled before a line of code is written.
Build
Two-week sprints, each ending in something that runs and that you can try yourself.
Release
Live in stages, with monitoring that trips before a user picks up the phone.
Maintenance
The part that lasts longest. Updates, incidents, and the version after this one.
What we work with
Work in this service
Need any of this?
A single half-hour conversation is usually enough to work out whether this fits and roughly what it costs.