UI/UX design people can use without a manual
We design the screens and the flow between them, and then we build them. Because we also write the code, designs come with every state the build needs: empty, loading, error, and what happens on a small phone.
Design that stops at the pretty screens
Design often stops at the pretty screens and skips the hard parts: what an agent sees before there are any leads, what happens when a payment fails, how a form behaves on a slow connection, and whether someone with low vision can read the text.
We design those states on purpose. BrokLeads is a good example: its interface is built so that anyone who can use WhatsApp can use it on their first day.
What we deliver
User flows and wireframes
The journeys that matter, sketched and agreed before any visual design.
Clickable prototypes
Something you can tap through and put in front of real users before it's built.
Visual design and design systems
Colour, type and spacing tokens, and components drawn in all their states.
Usability and accessibility review
An existing product checked against WCAG 2.2 AA, with the worst problems fixed first.
How we build it
Every UI/UX design project runs through our delivery process. These are the steps that are specific to this work. Teal steps are thinking, graphite steps are building, and orange ones keep it running.
Understand the users
Who they are, where they are, and what they do today.
Map the flows
The steps for each key task, before any screens.
Wireframes
Layout and content, quick to change.
Clickable prototype
Tested with a handful of real users.
Design system and handoff
Tokens and components the developers build from directly.
What you get
- User flows for the key journeys
- Wireframes, then a clickable prototype
- Visual design for every state of each screen
- Design tokens and a component library
- Accessibility notes on contrast, focus and labels
- A handoff the developers can build from directly
Typical timelines
| Scope | Range |
|---|---|
| Prototype for a new product | 2–4 weeks |
| Design system | 3–6 weeks |
| Redesign of an existing product | 4–8 weeks |
Planning ranges, not quotes. Your scope sets the real timeline, which we confirm in writing after discovery. See how engagements are priced.
Tools we use
- Design tokens in CSS
- Tailwind CSS
- React
- Next.js
- WCAG 2.2
See it in our work
- BrokLeads
A CRM designed so that anyone who can use WhatsApp can use it on their first day.
Read next
- Why website redesigns keep failing
Five reasons a new design doesn't bring more leads, and a better process.
Questions about UI/UX design
Do you only design, or build as well?
Both. You can hire us for design on its own, but the best results come when design and build stay together, because nothing gets lost in a handoff.
Can you test the design with real users?
Yes. Before anything is built, we put the clickable prototype in front of a handful of people who match your users. That's usually enough to show the biggest problems.
How do you handle accessibility?
We design to WCAG 2.2 AA: readable contrast, visible focus, a label on every field, and tap targets big enough for thumbs.
Often paired with
- Web developmentMarketing sites, customer portals and web applications on Next.js, React and TypeScript.
- Mobile app developmentiOS and Android apps with React Native and Expo, sharing an API with your web app.
- Custom softwareCRMs, internal tools, portals and multi-tenant SaaS with roles, permissions and integrations.
Tell us about your UI/UX design project
A few lines is enough. We'll ask the right questions on the call.
We reply within one working day
By email or WhatsApp, whichever you prefer.
A short call
To understand the goal, the people who'll use it and any deadline.
A written scope and estimate
Before any work starts, so you know what you're agreeing to.
Prefer to talk first?