UI/UX & Product Design
Design that survives contact with engineering.
Our designers work beside the engineers who will build the screens. That means prototypes reflect real data, real latency and real edge cases, and the design system ships as code components, not only as a file of pictures.
Schedule 1
What is included
- A-3.1
Research that changes decisions
Interviews, analytics review and usability tests, summarised as decisions rather than a slide deck nobody opens.
- A-3.2
Flows and information architecture
The paths users actually take, mapped before anything is made pretty.
- A-3.3
Clickable prototypes
High-fidelity prototypes you can test with customers before committing engineering time.
- A-3.4
Design systems in code
Tokens and components in Figma and in your codebase, kept in step so the product stays consistent.
- A-3.5
Accessibility built in
Contrast, focus order, screen-reader labels and motion preferences treated as requirements.
Schedule 2
Typical projects
- Designing a new product from a blank page
- Redesigning a product users complain about
- Building a design system for several teams
- Usability audits before a funding round or launch
Materials
- Figma
- FigJam
- Storybook
- Design tokens
- Maze
- Hotjar
Schedule 3
How it runs
- 01
Discovery · 1–2 weeks
We map the problem, the users, the data and the constraints, and agree what success will be measured by.
- 02
Blueprint · end of discovery
Architecture, scope, milestones and a fixed price for the first build phase, all in writing. You can stop here and keep the blueprint.
- 03
Build · weekly demos
Short iterations with a working demo each week, automated tests from day one and a shared board you can always see.
- 04
Launch & handover · planned cut-over
Staged rollout, monitoring switched on, documentation and a recorded handover session with your team.
- 05
Run & improve · optional
A monthly support plan, or nothing: the handover is written so that you never need us to keep the lights on.
Schedule 4
Common questions
Can we hire you for design only?
Yes. Design-only engagements end with a tested prototype and a developer-ready specification, whoever builds it.
Do you follow our brand guidelines?
Yes. Where no guidelines exist, we create a lightweight brand foundation (type, colour, voice) as part of the work.