Interface design and design systems for products
We design interfaces for the tools people work in every day and build design systems that speed up development and bring order to a company's products.
Who we work with and what we solve
What’s included
Scenarios by role, a walkthrough of the current screens, a map of the problems in priority order.
Clickable prototypes of the key scenarios — before development gets expensive.
Screens in Figma: states, responsive layouts, handover to development.
Tokens, components and rules — in Figma and in code through Storybook.
Logo, typography, collateral — tied to the digital products.
Reviews of the built front end, ongoing work on the system, design for new features.
Process
Timelines are indicative for a mid-sized company — we fix the exact ones after the audit.
Roles, tasks, a walkthrough of what exists today.
Screen structure, tested with real users.
Screens, tokens, components, documentation.
We work with the developers until the interface matches the designs.
Stack and tools
Questions
Can we get design only, without development?
Yes. We hand the designs, prototypes and design system to your team and stay with you through implementation.
Why do we need a design system?
It removes repeat work: new screens are assembled from components that already exist — faster, and without drift between products.
Do you do brand identity?
Yes: logo, typography, guidelines. Usually — alongside a website or a product, so the identity lives on something real from the start.
What tools do you work in?
Figma for designs and the system, Storybook for components in code, HTML prototypes for the complex scenarios.