UI / UX Design
Design that reduces support tickets.
The most common UX problem isn't that something looks bad — it's that it makes sense to the person who built it and nobody else. People don't read instructions. They don't ask for help. They just leave. Good design is about anticipating that and building something that works for someone who doesn't already know how it's supposed to work.
What this involves
Figma work that survives development
Design files that are actually usable as a handoff — consistent components, real constraints, annotated edge cases, documented states. Developers don't have to guess what the empty state looks like, what happens when the name is 80 characters long, or what the error message says.
Design systems that let teams move faster
One Figma library. One component library. Consistent spacing, typography, and colour decisions that don't need to be relitigated in every Figma comment thread. Saves time arguing about button sizes and lets everyone focus on decisions that actually affect whether the product is good.
Usability work before you build the wrong thing
Testing a prototype is cheaper than testing a shipped feature. We run sessions with real users, watch where they get confused, and surface the problems before you've committed engineering weeks to solving the wrong thing. The findings are usually uncomfortable but always useful.
Fixing what's already broken
An audit of an existing product: what's confusing, what's missing, what should just be cut. Sometimes the right answer is to remove a feature rather than redesign it. We're not trying to give you a longer backlog — we're trying to make the product easier to use.
This is a good fit if…
- You're about to build something new and want design done before engineering starts
- You have a product people use but regularly complain about — and support volume reflects that
- Your engineering team spends time on design decisions they shouldn't have to make
- You want a second opinion on a design direction before committing to it
- Your onboarding drop-off is high and you're not sure if it's a product or messaging problem
Technologies we use
We work in the stack you already have. Here's what we typically reach for in this area.
Common questions
Do you do both design and development?
Yes. The best results happen when design and engineering are in conversation throughout, not separated into sequential handoffs. We design in Figma and build in React or your existing frontend stack.
What does a UX audit involve?
We look at your product as a new user, document where things are confusing or broken, run sessions with real users where there's time, and produce a prioritised list of changes with rationale. Usually takes 1–2 weeks depending on product size.
Do you design mobile apps?
Yes. Mobile-first if that's where your users are. We design for both platforms and account for iOS vs Android conventions where they differ — not just the same screens resized.
How do you handle design handoff to engineering?
Figma files with proper components, design tokens, annotated edge cases, documented states, and a walkthrough session with whoever will build it. We stay available during development to answer questions as they come up.