Interfaces people trust, including AI ones.
What we build.
Research and flows
Talk to the people who will use it, then map the paths they take.
Product design
Screens and prototypes for web and mobile, tested before they are built.
Design systems
Tokens, components and rules your engineers can build once and reuse.
AI interaction design
How an AI shows its sources and its confidence, and asks before it acts.
How an engagement runs.
Goals, users and what success looks like.
Flows, screens and prototypes, tested with real users.
A design system and specs your engineers can build.
Design support while it is built and after.
A typical engagement.
- Duration
- [3–8 weeks]
- Team
- [1–2 designers, an engineer on call]
- You get
- Tested flows, a prototype and a design system
- Starts with
- A scoping call
What engineers get.
Design system
Tokens and components, in [Figma] and in code
Flows
Every path, with the edge cases
Specs
Spacing, states and behaviour for each screen
Prototype
Clickable, and tested with real users
Questions about the design work.
Do you test with real users?
Yes. Short sessions with the people who will use it, before anything is built.
Can you also build what you design?
Yes. Our engineers sit in the design work, so what we hand over is something that can be built.
How do you design for AI that can be wrong?
By showing sources, making confidence visible, and putting a person in charge of anything that cannot be undone.