07
UI/UX & product design
Design before decoration. The interface is how the product thinks.
Problem
Pretty screens that cannot be implemented are not design. They are postponement.
We work from the job to be done, through information architecture, into components a codebase can hold. Motion, type, and space are part of that system — not a layer poured on at the end.
- Files that ignore empty, error, and permission states
- Design systems that exist as a Figma page and nowhere else
- Research that never changes a decision
- Handoff as a dump, not a conversation
Capabilities
What this work actually includes.
01
Product discovery
Interviews, mapping, and prototypes that answer a question, not a deck.
02
Information architecture
Navigation, language, and structure for products with more than five screens.
03
Interface design
High-fidelity UI with the states engineering actually needs.
04
Design systems
Tokens, components, and rules that match the frontend, not a parallel universe.
05
UX writing
The words in the product: errors, empty states, and the sentence that makes a choice clear.
06
Design engineering
We implement when that is the fastest way to keep fidelity.
Technology
Tools we reach for here.
- Figma
- Design tokens
- React
- Tailwind CSS
- Motion
- Storybook
Approach
How we deliver it.
01
Start with the work
What is the user trying to finish, and what does the business need to be true.
02
Prototype the hard parts
The dense table, the permission model, the first-run — not the hero illustration.
03
Systematize
Type, color, components, motion — so new screens do not invent a language.
04
Sit with engineering
Handoff is continuous. Ambiguity is a bug.
Use cases
Where this tends to land.
New product definition
From a problem to a product that can be estimated and built.
Redesign of working software
Keep the domain, repair the experience, avoid a vanity relaunch.
Design system rescue
Align design and code so neither is lying.
Complex B2B interfaces
Density, power, and clarity for people who live in the product.
Related industries
Related insights
FAQ
Useful questions.
We can do either, or both. The studio is strongest when design and engineering share the same problem.
Start a project
Start a design project.
A short note is enough. We will come back with questions, not a pitch deck.