Skip to content
UI/UX & Product Design

UI/UX & Product Design

Tested on strangers before it costs you a sprint.

Research-led design for web and mobile: interviews, flows, prototypes and usability tests, then the interface and the system it is built from. We stay through the build for design QA, because the gap between the file and the shipped screen is where quality leaks.

We start with the people who will use the thing. Interviews, a read of your support tickets and session recordings, then prototypes put in front of strangers before anyone commits a sprint to them. A concept that fails in a test costs an afternoon; the same concept fails in production for a quarter.
Everything ships as a system: tokens, a Figma library, a Storybook and documentation written for the engineer who joins in 6 months. We stay through the build for design QA, and we keep a record of what we got wrong so the next release starts further along.

What you get

Deliverables, specifically.

8 things you can point at. Scope is agreed in writing before the first invoice.

  • Research you can read in an hour: interviews, jobs-to-be-done, survey results and competitor teardowns, with the findings kept separate from the recommendations
  • A UX audit with a prioritised fix list, ordered by effort against expected effect
  • Information architecture, user flows, wireframes and a clickable prototype
  • High-fidelity interface design, plus motion specs and every state for the components that move
  • A design system: tokens, a Figma library, Storybook and documentation your engineers can maintain without us
  • Usability tests with recorded sessions and a written verdict, including the tasks people failed
  • WCAG 2.2 AA reviews, with each failure listed against the screen it happens on
  • Interface patterns for AI features: what the assistant may do, what it must ask first, and what it shows when it is unsure

How it runs

3 steps. Then it compounds.

Our method, narrowed to this service. Every step ends with a document, a build or a number you can check.

  1. 01

    Research

    Interviews, an audit of the product you have, and the success metrics agreed in writing before a single screen is drawn.

  2. 02

    Explore and test

    Concepts and prototypes, tested with people who work for neither of us, and reworked until they succeed without a facilitator helping.

  3. 03

    Systematise and ship

    Final interface, the system behind it, handover to engineering, then design QA through the build and a review against the metrics 30 days after release.

Questions

Asked often.

  • A project for a defined product or redesign, a retainer or an embedded designer for continuous work, or a sprint when one decision is holding up everything behind it. Each one opens with research rather than screens, which is the stage clients ask us to cut and later ask us to put back.

Start with product design.

30 minutes, no deck. We'll tell you what we'd fix first, and whether it needs us.