UI/UX & Product Design
Design work that answers a business question, not a taste question. Where users abandon the flow, which words make them hesitate, and what happens to the numbers when those things change.
We research, prototype and test with real people before a single component is built — because the cheapest place to be wrong about an interface is in Figma.
What We Deliver
The work this engagement actually covers — and what you own at the end of it.
User Research
Interviews, analytics review and usability testing that establish what people actually do, which is regularly not what the internal roadmap assumes.
Wireframing & Prototyping
Clickable prototypes of the core journeys, tested with real users while changing direction still costs an afternoon rather than a sprint.
Interface Design
Visual design across every state — loading, empty, error, edge case — so engineering never has to invent a screen that was never drawn.
Design Systems
A documented component library with tokens and usage rules, handed over so your team can extend it without the system drifting apart.
Accessibility Audits
WCAG 2.2 AA review covering contrast, keyboard navigation, focus order and screen-reader semantics, with a prioritised remediation list.
Conversion Optimisation
Funnel analysis and A/B tested changes to the flows where drop-off is costing you money, measured before and after.
What you receive
- Research findings with prioritised recommendations
- Clickable prototypes of the core user journeys
- Complete Figma design files, organised for handover
- Design system with tokens, components and usage documentation
- WCAG 2.2 AA audit with a prioritised remediation list
- Developer-ready specifications and exported assets
How the Work Runs
No stage is a surprise, and every one of them ends in something you can look at.
Research & Audit
User interviews, analytics review and a heuristic audit of what exists today, ending in a written problem statement everyone agrees on.
Structure & Flows
Information architecture and journey mapping — what belongs on which screen, and in what order — before any visual design begins.
Prototype & Test
Interactive prototypes tested with people from your actual audience. Findings change the design; that is the point of doing it.
Visual Design & System
Final interface design across all states, assembled into a documented component library rather than a folder of screens.
Handover & Support
Developer walkthrough, specifications and design QA during the build, so what ships matches what was approved.
What Good Looks Like
Accessibility is not a separate workstream here. Designing for keyboard users, screen readers and low-contrast conditions from the first component is cheaper than retrofitting, and it makes the interface better for everyone.
Technology We Use
Chosen for what your team can hire for and maintain, not for what is new this quarter.
- Figma
- FigJam
- Design Tokens
- Storybook
- Prototyping
- Usability Testing
- WCAG 2.2
- Hotjar
- Google Analytics
Engagement Models
Three ways to work with us. Which one fits depends on how settled your scope is and how long you need the team.
Fixed-Scope Project
A defined outcome, an agreed timeline
We scope the work up front, agree the deliverables and the date, and carry the delivery risk. Best when you know what you need built and want a predictable commitment.
Best for
- A launch with a hard deadline
- A well-understood rebuild or migration
- First projects with a new partner
What's included
- Written scope, milestones and acceptance criteria
- A named project lead and weekly demos
- Fixed delivery date with change control
- 30 days of complimentary post-launch support
Dedicated Team
Our engineers, your roadmap
A ring-fenced team — engineers, designers and QA — working only on your product, in your rituals and your tools. You set the priorities sprint by sprint.
Best for
- Evolving product roadmaps
- Scaling an in-house team quickly
- Long-running platform work
What's included
- Named team members, not a rotating pool
- Your sprint cadence, standups and board
- Direct access to every engineer on the team
- Scale the team up or down at each sprint boundary
Ongoing Retainer
Someone who already knows your system
A monthly block of engineering time for maintenance, security patching, performance work and steady improvement — from the people who built it.
Best for
- Live products that need care, not a rebuild
- Security and dependency upkeep
- Incremental features after launch
What's included
- Essential, Growth and Enterprise tiers
- Monitoring, security patches and dependency updates
- Agreed response times, up to a 24/7 SLA
- Monthly report on what changed and what it cost
Design engagements are usually fixed-scope. Teams shipping continuously often keep a designer on a dedicated-team arrangement instead.
Related Work
Calculator Vault
A privacy-first Android app that hides photos, videos and files behind a fully functional scientific calculator. No account, no network calls, nothing to give it away on the home screen.
AQNEX E-Commerce Suite
A multi-tenant commerce platform that replaced three disconnected systems — a customer storefront, an admin operations hub and a supplier portal — with one synchronised set of data.
Aquison Jewels
A catalogue site for a fine jewellery maison — thirty pieces across five collections, browsed like a boutique and enquired about over WhatsApp or email. No cart, no prices, no server.
From Our Journal
AI-Driven Design Systems
How generative AI is helping designers create more consistent, accessible, and beautiful user interfaces at unprecedented speed.
Building for the Spatial Web
From WebXR to Apple Vision Pro — how to start building immersive 3D experiences that will define the next era of the internet.
UI/UX Design Questions
The things prospective clients ask us before committing to this work.
Can you design without also building the product?
Yes. Plenty of clients bring us in for research, design and a documented design system, then build with their own engineers. Handover includes developer specifications, exported assets and a walkthrough, and we can stay on for design QA during your build so the shipped product matches what was approved.
How do you know the design actually works?
We test prototypes with people from your real audience — typically five or more per round, which surfaces the large majority of usability problems — and we agree the success metrics before the work starts. Where there is existing traffic, changes to critical flows are validated with A/B tests rather than opinions.
What is a design system and do we need one?
A design system is a documented set of components, tokens and rules for using them. You need one when more than a couple of people build interfaces, or when the product will keep growing after we leave. Below that scale it is overhead, and we will tell you so.
Does accessibility cost extra?
No. WCAG 2.2 AA is our default standard on every design engagement, built in from the first component rather than added afterwards. Full remediation of a large existing product that was never designed accessibly is separate scoped work, and we quote it after an audit.
Can you redesign our product without breaking what already works?
That is what the research phase is for. We identify which flows are performing before touching them, redesign in stages, and validate each stage against the baseline. A redesign that lowers conversion is a failed redesign no matter how it looks.