We take on a small number of client projects alongside our own products. The work is the same either way: one clear question, screens that explain themselves, and engineering that holds up.
Finding the one question the product has to answer, and what it must never do.
In our own workPurser started from one question, what is safe to spend before payday, and one refusal: it never moves money.
Screens that explain themselves, designed in light and dark, for phone and tablet, from the first sketch.
In our own workEvery Purser screen ships in two themes and two sizes, from one set of colour tokens.
Native apps in SwiftUI and back ends that run without servers to babysit.
In our own workPurser is a SwiftUI app on a serverless back end, and its safe to spend number is computed by pure, unit-tested functions.
Connecting security tools so the data you depend on actually arrives, and you know when it does not.
In our own workOur Security Field Guides document four integration pairs we tested end to end, including what silently fails.
We agree on the one question the product answers, and what it must never do.
We design the real screens in both themes and on both sizes, with real words in them.
We engineer it in small, tested pieces, and you see working software early and often.
People walk through the finished product before it ships. Done means it was used, not just merged.
Write to us with what you are building, who it is for and when it needs to be right. A person reads every message.