In continuous production
Shipped and deployed globally
Average infrastructure reliability
Direct founder-engineer attention
How we think about making software.
Most companies treat software as a delivery problem. We treat it as a thinking problem. The code is the least interesting part. The interesting part is figuring out what the code should say.
We work across the full range of what making software means — from the architecture of complex distributed systems to the micro-interactions of a single button label. Both matter. Neither is decorative.
Four things we believe.
Start with the decision.
Every product ultimately serves a decision. Not a user story. Not a workflow. A decision a person needs to make and the quality of that decision matters. We design toward the decision first.
Complexity belongs in the system.
The interface should be simple. The system underneath it can be as complex as the problem demands. We resist the temptation to expose complexity to the user because we haven’t hidden it properly in the system yet.
Speed is a design decision.
Fast products feel respectful. Every interaction has a tempo, and that tempo communicates what you think a person’s time is worth. We optimise for speed as a baseline requirement, not a stretch goal.
Earn trust, don’t assume it.
Especially in AI-powered systems. Users need a working model of what the system is doing. We design for legibility — making the system’s reasoning followable, not just its outputs visible.
Let's make something.
We work with founders, leadership teams, and technical builders who take pride in making things that last.