design.
build.
make it.
I help ambitious startups and small businesses build a brand and digital presence that matches what they're actually building.
One practice, not three services
Most teams hand a product between a designer, an engineer and whoever handles the AI part. I don't hand it over.
Product design
Interface, flow and brand identity, designed against the constraint of what can actually be shipped.
Full-stack engineering
Next.js, React, TypeScript, Tailwind, Node and Postgres. Products that hold up after launch, not prototypes that need rewriting.
AI systems
Model-backed features built around what the product needs, and built to degrade gracefully when the model doesn't cooperate.
How working together goes
No deck, no discovery theatre. Five steps, and you can stop after any of them.
- 1
Understand what you're actually building
Before anything gets designed we establish the product direction: who it's for, what job it does, and what success looks like. Most wasted budget comes from skipping this.
- 2
Design the screens that carry the weight
Not every screen. The three or four flows that decide whether the product works, designed properly, so the rest can follow the pattern.
- 3
Build it, not a mockup of it
Because I design and engineer, there's no handoff gap. What you approve is what gets built, in the same week rather than the next quarter.
- 4
Instrument it before launch
Analytics, conversion tracking and event definitions go in before you ship, not after. You can't improve what was never measured properly.
- 5
Hand it over so you can run it
Documentation, a CMS you can actually edit, and the reasoning behind the decisions. The goal is that you don't need me to change a headline.
Frequently asked
Yes. Most of my work is with teams in the UK. I'm on GMT year-round, which overlaps with UK and most of Europe for a full working day.