Product design and build
The expensive part of building software is rarely the building. It's the handoff — a designer produces screens an engineer can't build, an engineer builds something the designer didn't intend, and three weeks disappear. I do both, so that gap doesn't exist.
From £1,500 · 4–5 weeks — Introductory rate for my first three projects of 2026. Brand and site together from £2,000. Full product MVPs are scoped separately.
Who it's for
- Startups that need a marketing site doing real work, not a placeholder
- Teams with a product that works but looks like an internal tool
- Anyone with a Figma file and nobody to build it
What you get
- Product direction and flow definition
- Designed pages or screens, built rather than mocked up
- A production build in Next.js, React and TypeScript
- A CMS you can edit without calling me
- Analytics and conversion tracking configured before launch
- Two rounds of revisions included
How it runs
- 1
Understand what you're actually building
Who it's for, what job it does, what success looks like. Most wasted budget comes from skipping this.
- 2
Design the screens that carry the weight
The three or four flows that decide whether it works. The rest follows the pattern.
- 3
Build it, not a mockup of it
What you approve is what gets built. No translation layer between design and code.
- 4
Instrument before launch
Events, conversions and analytics defined up front. You can't improve what was never measured.
- 5
Hand it over
Documentation, an editable CMS, and the reasoning behind the decisions.
Questions
Then I build against their files and we skip the design phase, which brings the cost down.