Frame
The job the interface has to do, in the user's words.
UI/UX Design
We design in systems: tokens, states, empty cases, error cases, the sixteenth row of the table. The result feels obvious to use and is inexpensive to extend.
- Typical duration
- 4 – 10 weeks
- Engagement
- Project or retained
- Deliverables
- 5
- Phases
- 4
Signals
Signs you needthis work.
The screens that get designed are the happy ones. The screens that get used are the other ones — nothing loaded yet, permission denied, one item, four hundred items, the connection dropped mid-save. We design those first, because they are where products lose trust, and because a system that handles them cleanly makes every other screen simpler.
Every new feature arrives looking slightly different from the last.
Developers are inventing states the designs never covered.
Users keep asking how to do something the interface already does.
Sequence
How the work runs.
Flow
Paths, decisions and dead ends mapped before any pixel is placed.
System
Type, space, colour, components — defined once, reused everywhere.
Specify
States, motion and edge cases documented for the people building it.
Included
Product discovery and user flows
Wireframes through to high fidelity
Design system with tokens and states
Prototypes for real interaction testing
Developer handover specifications
Typical stack
Figma
Design tokens
Prototyping
Accessibility audit
Handover docs
Questions
Yes — and we specify it properly for your engineers. But we price and plan knowing it has to be built, which is why our designs tend to survive contact with a sprint.
Start here
Have a projectthat needs this?
Tell us what you are trying to achieve and we will come back with an honest view on scope, sequence and whether ui/ux design is really the thing you need first.