Research, interaction, motion, brand systems. We design products that look like a point of view, not a moodboard, and we ship the components engineers can actually build with.
We hire designers who can ship code, and engineers who can defend a layout. The handoff is short because the handoff is mostly internal.
Six recurring archetypes cover most of what we get asked to build. Pick the one closest to yours, or describe your own — we've probably done a cousin of it.
End-to-end product UX. Discovery, IA, flows, prototypes, hi-fi, motion. We sit with engineering through build — designs that ship are designs that survive.
Tokens, primitives, patterns. Built in Figma and shipped as code in lockstep. Documented well enough that the system survives the designer who left.
Marks, wordmarks, motion identity, typography, tone of voice. Brands that hold up at 16 px and at 16 metres.
Sites that read like a magazine and convert like a checkout. Custom typography, art-directed layouts, scroll choreography that respects the reader.
Foundational, generative, evaluative. Diary studies, jobs interviews, usability rounds — synthesised into decisions, not 80-page reports nobody reads.
The stuff between the screens. Page transitions, gesture choreography, loading states that feel intentional, not apologetic.
Every engagement ends the same way: a production system, a team that can run it, and a written record of every decision we argued about.
A deliberately conservative core. We swap in sharp tools when the problem requires them, never because they're trending.
Pick the one that maps to where you are. Or hop between them — most clients start at one and end at another.
Architecture review, prototype of the riskiest interaction, and a costed roadmap. You walk away with a plan whether or not we build it.
Senior pod of 3–5: tech lead, full-stack, design, QA. Two-week cycles, demo every Friday, you own the repo from week one.
Once it's live. A reduced pod stays in your stand-ups, owns the on-call rota, and ships the roadmap quarter-over-quarter.
If yours isn't here, just ask. We respond to most enquiries within a working day.
Yes — most of our work is alongside in-house teams. We default to your repo, your code review, your standup. Where we run our own pods, we still pair-program weekly so the knowledge transfers from day one rather than at handover.
Frequently. We start with a one-week audit: code, infra, team, runway. Output is a frank document — what to keep, what to throw out, what to rewrite — and a costed path to stable. About a third of those projects we then take on. The rest we hand back with a plan they can execute themselves.
You own everything we write — code, designs, infra, docs — assigned on first commit. We keep no kill-switches and no exclusivity clauses. Our standard MSA is six pages and we'll happily redline yours.
For well-shaped, mostly-known scopes — yes, we offer fixed-fee with milestone billing. For genuinely exploratory work we recommend time-and-materials with a hard cap, because anyone who quotes you a fixed price for an unknown is either lying or building you something cheap.
A two-week discovery sprint. Below that we're not adding much value over a good freelancer, and we'd rather refer you to one of the four we trust than do it badly ourselves.