User and stakeholder research
Interviews with the people who will actually use the product, plus a review of what your current flow already tells you.
What we do
Interfaces people understand without being trained
Research, prototypes and design systems that turn a complicated product into something a new user can finish a task in, on the first try.
The short version
Good design is not decoration added at the end. It is the decision about what goes on the screen, in what order, and what gets left off entirely. Those decisions are cheap to change in a prototype and expensive to change in production code.
We work in the open: research notes you can read, prototypes you can click, and a design system handed over as real components rather than a static file. If a screen tests badly, we would rather find out in week two than after launch.
Scope
Every item below is in the written scope before work starts, so nothing on this list is an upsell later.
Interviews with the people who will actually use the product, plus a review of what your current flow already tells you.
The structure of the product: navigation, hierarchy and naming that matches how your users think about their work.
Low fidelity first to settle the flow, then an interactive prototype in Figma you can hand to a real user.
Type scale, colour, spacing, states and components, documented so two developers build the same button the same way.
Tokens and components mapped to code, so the design survives the next three features instead of drifting.
Contrast, focus order, keyboard paths, labels and touch targets checked against WCAG, not left to chance.
How it runs
Five stages, each with something you can see or review at the end of it.
What is the user trying to finish, how often, and what currently gets in the way.
Flows and wireframes reviewed together, so the expensive decisions are made in the cheap medium.
Components and tokens defined once and reused, so the twentieth screen costs less than the second.
Five sessions on the prototype catch most of what a launch would have caught the hard way.
Specs, states and edge cases documented, with us available while the build happens.
Questions
If your question is not here, ask it directly. We answer the awkward ones too.
Yes. Plenty of clients bring us in for research, UX and a design system, then build with their own in-house team. We write the handover for developers we will never meet, which tends to make it better documentation.
That is a large part of our design work. We start with a UX audit of the current product and a prioritised list of fixes, so you get value from the quick wins while the larger redesign is still in progress.
One named decision maker, comments in Figma rather than in chat, and a fixed number of review rounds agreed up front. It sounds rigid, and it is the thing that keeps design projects on schedule.
We handle brand application: colour systems, type, iconography and how the brand behaves in a product. For a full identity from scratch we will tell you if a specialist is the better spend.
Also relevant
Custom websites and web applications built on Next.js and React, tuned for speed, search visibility and real conversions rather than template looks.
Read moreCross-platform mobile apps in React Native and Flutter, with offline behaviour, payments and notifications that work on the phones and networks your users actually have.
Read moreSend us the situation as it is, including the parts that are messy. We will tell you what we would do first and what it would cost.