Services
UX Design
What does a UX design engagement actually involve? Research with your real users, the architecture underneath the screens, and interfaces your developers can build from.
Most products don’t fail because the interface is ugly. They fail because nobody checked what the user was trying to do before the screens were drawn.
We start there. Over 22 years and more than 500 projects across healthcare, banking, telecom and consumer products, the pattern holds: the expensive problems are decided before anyone opens a design tool.
Design that starts with the problem, not the screen.
We run research with the people who will actually use the product, map what they’re doing today including the workarounds, and design the flow around that rather than around the database schema.
What comes back is usually fewer screens than you expected, a structure your team can keep building on, and a clear record of why each decision was made — so the next person doesn’t undo it.
- 22 years designing digital products
- 500+ projects delivered
- 200+ industries worked across — Healthcare, banking, Finance, Telecom, Consumer,
What you get
-
User research
Interviews, contextual enquiry and usability testing with your actual users — not a proxy panel, and not a survey standing in for a conversation.
-
Information architecture
The structure underneath the screens: what lives where, what it’s called, and why someone would think to look for it there.
-
Interface design
High-fidelity screens covering the empty, loading, error and edge states as well as the happy path, plus a component library your developers can build from directly.
-
Prototypes
Clickable prototypes so a decision gets tested while it’s still cheap to reverse.
-
Design documentation
Written findings and rationale. A design that nobody can explain in six months gets rebuilt from scratch in eighteen.
How it works
-
01
Discovery
We learn the business, the users and the constraints before proposing anything. Usually a week, including stakeholder interviews.
-
02
Research
We talk to users and watch them work. Findings are written up and shared, not just discussed in a call.
-
03
Architecture
Flows, structure and naming, agreed before any visual design starts. This is the step most projects skip and most projects regret skipping.
-
04
Design
Screens, states and components, reviewed with you weekly rather than revealed at the end.
-
05
Handoff
Specs, tokens and a walkthrough with the engineers building it. We stay reachable through the build, because questions always come up.
Questions
How long does a UX design engagement take?
A focused flow takes four to six weeks. A full product usually runs three to five months. We’ll tell you which one your problem is after the first conversation, not after you’ve signed.
What does a UX design project cost?
It depends on scope, but we work to a minimum engagement so that research doesn’t get cut to fit a budget — which is the most common way these projects go wrong. We’ll give you a range on the first call. [Add your actual floor here — a stated minimum filters out the enquiries that waste your time.]
Do you work with our existing developers?
Yes. Most engagements hand off to an in-house team, and we stay available through the build.
What if we already have a design system?
We design inside it, and tell you where it’s getting in the way rather than quietly working around it.
Do you do research, or only design?
Both, and we’d rather not do the second without the first. If budget only stretches to one, research is the part that changes what gets built.
Related work
Alooba.com
UX Design, Product Design, Design System, Front-end
Structuring candidate assessment so two reviewers reach the same conclusion.
01 / 01
