ServicesProduct Design & UI/UX
Product Design & UI/UX
Software people can use without being trained to use it.
Talk to an engineerWhen companies call us about this
You will probably recognise one of these.
New staff need a week of training before they can use the system.
The screens follow the database, not the job. People keep a printed cheat sheet next to the monitor.
Every screen looks like a different product.
Three teams built three parts of the app and each chose its own buttons, colours and patterns. Users learn the same thing three times.
Customers sign up, look around and leave.
Activation is low and nobody knows which step loses people. Decisions about the interface are made by whoever argues longest.
You have been told the product is not accessible and do not know where to start.
A customer, an auditor or a procurement team has raised it. There is no list of what fails or what fixing it would take.
What we do
Five things, each with something you keep.
Product and UX design
We start with the job the user is trying to do and design the shortest route through it. Every screen is tested with real users before it is built.
Deliverable: User flows, clickable prototypes and the research notes behind them
Design systems
One set of components, tokens and rules that every team builds from. New screens are assembled, not invented.
Deliverable: A component library in code and in the design tool, with written usage guidance
Front-end engineering
Interfaces built by engineers who work alongside the designers, so what ships is what was designed. Performance and responsiveness are measured, not assumed.
Deliverable: Production front-end code in your repository, with component tests
Accessibility
We audit against WCAG 2.2 AA, fix what fails and show your team how to keep it that way. Keyboard, screen reader and contrast issues are dealt with at the component level.
Deliverable: An audit report with severity ratings, the fixes applied and an accessibility statement
Usability testing
Structured sessions with five to eight real users per round, watching them attempt real tasks. Findings are ranked by how many people were blocked, not by opinion.
Deliverable: Session recordings, a findings report and a prioritised change list
What we work with
Chosen for fit, not for fashion.
We choose based on what fits the problem and on what your team can maintain after we leave. A stack nobody in your organisation can operate is a liability, however good it is.
- Front-end frameworks
- Application backends
Questions we are usually asked
The ones competitors avoid.
What does an engagement like this cost?
Most engagements land between $15,000 and $70,000. The range is driven by the number of distinct user roles and screens, and by whether the front-end build is in scope or only the design. A standalone accessibility audit sits at the bottom of that range.
How long before we see anything working?
A clickable prototype of the core journey, tested with real users, within three weeks. Built screens follow from week five if engineering is in scope.
Who will actually be on the team?
A lead product designer with eight or more years on shipped software, a researcher for the testing rounds, and one or two front-end engineers where the build is included. Kunal Khurana, our CTO, is the accountable technical lead for anything that ships as code.
Who owns the IP?
You do. Design files, research findings, the component library and every line of front-end code are your property from the day they are produced. We keep no licence and reuse nothing without your written agreement.
Tell us what you are building.
A 30-minute call with an engineer who will work on it.A 30-minute call with an engineer who will work on it. No sales sequence, no obligation.
Book a consultationor email us directly