Service 04 — 05
Product
Interfaces and design systems. We take products with forty screens and find the twelve that matter — then make those twelve feel inevitable.
What a product project entails
We start by deleting. A week inside your analytics, your support inbox and three real user sessions usually shows that half the interface is apologising for the other half. The redesign begins with what we can remove.
What remains gets a system, not a set of screens: tokens, components and motion rules your engineers can build from without asking us twice. We stay through the first release, then hand over the keys with documentation written for humans.
Product in the wild
Fair questions
Do you work with our engineers?
Gladly — it is the usual setup. We join your stand-ups, spec in your tracker, and review builds the way we review type: closely, kindly, in writing.
Figma, code, or both?
Both. Figma for decisions, working prototypes for the things static frames lie about — usually motion and density. Developers get tokens, not screenshots.
What if we only need the system?
A systems-only engagement is one of our favourite shapes: audit, tokens, components, docs — then we get out of your team’s way.