Website Design

Most website design work sits on a spectrum from template-shop to studio-scale. We work exclusively at the studio-scale end of that range. The sites we design are the ones where the design is part of how the brand works: editorial publications, premium product sites, founder-led brands where the website is the company’s public self, and documentation sites that treat themselves as first-class product surfaces.

Our design process is research-led and prototype-driven. We start with conversations with the client’s users — actual customers, not personas — and we build information architecture on what those conversations show us, not what the existing site says they should show us. We move quickly from sketches to Figma, and from Figma into the browser, because the browser is where the design actually lives. Our static Figma files are the least interesting artefact of the work; the prototypes are where we make decisions.

We design with engineering in the same conversation from week one. This means our design systems ship with named tokens, component APIs that read like our engineering colleagues would build them, and a Figma file structured so handoff is a non-event rather than a translation exercise. We don’t throw designs over a wall; we walk them to the engineering team and watch them land.

What we won’t do is design sites that are visually impressive for their own sake. The house style is editorial restraint: clear typography, generous whitespace, deliberate motion, and visual noise stripped out rather than layered on. If the brief is “make it more visual,” we’ll usually push back — and we’ll tell you why.