/ How We Think

The browser is a tool. We build it that way.

Most studios open Figma before they understand the problem. We open with a different set of questions — and the work gets built from those answers forward.

Overhead shot of a studio desk under working light — a monitor showing a partially built webpage layout, a notebook with handwritten annotations beside it, a coffee cup at the left edge, the scene captured mid-session with no staging
Overhead shot of a studio desk under working light — a monitor showing a partially built webpage layout, a notebook with handwritten annotations beside it, a coffee cup at the left edge, the scene captured mid-session with no staging
— Studio philosophy

A gallery holds work. A tool changes behavior.

Web design that treats the browser as a gallery optimizes for how something looks at rest. We optimize for what happens when someone arrives — what they assume, what they need, and what moves them toward a decision.

This is a small practice by design. Fewer clients means deeper engagement with each one — which is the only way to build something that actually performs.

Three questions come before the brief.

Who is arriving at this page? What are they already assuming when they land? And what's the first thing that needs to break that assumption to move them forward?

The answers determine the structure, the hierarchy, the copy weight, and the interactions — not the other way around.

Specific work, specific fit

See the problems we actually take on.