Design people finish using
Interfaces that get tasks done, and a brand that is recognised.
Four things we design
Each one is tested on paper before it is built.
Flows and screens, tested before they are built.
Pages designed around one action each.
Logo, colour, type and a system to use them.
Components and rules your team can reuse.
Sketched, tested, then built
We draw it on paper, and put it in front of people early.
Flows drawn before screens
The steps to a finished task, checked before any colour.
Tried by real people
A clickable prototype shows where people hesitate.
A kit your team can reuse
Colours, type and components written down once.
How it runs
Listen
Who uses it, what they need and what is in the way.
Sketch
Flows and wireframes, reviewed with you.
Design
Screens, brand and a prototype you can click.
Hand over
Files and notes for developers, ready to build.
Questions we get
What is product design?
Product design is deciding how software works and looks, from the steps a person takes to the screens, brand and components. We design it, test it with real users and hand it to developers, or build it ourselves.
Do you design only, or build too?
Both. You can take the designs to your own developers, or we build them so the finished product matches what was designed.
Do we own the designs and the brand?
Yes, once the project is paid for. You receive the source files and the brand guide.
How do you handle feedback?
We agree the number of review rounds in the scope. Each round has a clear list, so changes do not drift.
Tell us what you’re building.
- A call about the goalThe budget, the deadline and what success looks like.
- A written scopeWhat we build, in what order, and the quote.
- Work in sprintsA demo at the end of each one.