Step 01
Read
Two weeks with your data, your support tickets and your team, so the work aims at the thing that actually costs you money. We come back with the problem in one sentence, and it is rarely the sentence you gave us.
03 / Studio
3 people, 4 disciplines
Studio
A development atelier, judged on what your product does after we leave. Three people, four disciplines, one bill — and no handoff between the person who designs it and the one who ships it.
Est. 2026
The short version
No slide deck
Nobody buys a design system. They buy an hour back, a customer kept, a risk closed. We work backwards from that and let the craft answer to it.
What that means in practice
We ask what the number is before we ask what it should look like. Then the same three people carry it from that answer all the way to production. Nobody gets to say that's not my part.
What we will not do
Take a project where the interesting decisions have already been made by someone else. Quote a timeline we do not believe. Hand you a system the next team cannot read.
How the work pays for itself
Every project, no exceptions
Step 02
Draft
Directions in the browser, at real widths, with your real content — so you are approving the product, not a picture of it. Static comps hide what breaks, so we skip them.
Step 03
Build
Typed, tested, documented. The design system and the codebase are the same artefact, and they ship together or not at all.
Step 04
Again
A second pass is written into the contract. We revisit the whole thing four weeks after launch, with the real numbers in front of us, and fix what those numbers say to fix — including our own favourite decisions.
Who you actually get
Hover a face
The Team
K
W
V
Three people. Every one of them ships.
Fullstack Product Design Engineer · Agentic SWE · Forward Deployment
AI / ML Researcher · Product Orchestration Lead
Network Security & Infrastructure Engineer