One maker at the kiln.

I design and build websites on my own, and I've never been able to keep the two apart for long.

I studied banking and finance at polytechnic, then switched to computer science. Finance was never going to stick. I'd been drawing and messing about with graphics the whole way through anyway, and what I actually wanted was to build things — web design is where those two ended up overlapping.

How the work goes: one project at a time, so yours isn't sitting behind three others. I write every line of it, with no page builder underneath and no theme bought and re-skinned. Because I know how long that takes by now, I can give you a fixed price instead of running a meter.

The concept builds in the work section are self-initiated. Nobody paid for those and no client brief shaped them — I'd rather say that outright than dress personal projects up as case studies. They're there so you can see the standard before you spend anything. Executed is the different one: a subscription platform that's live in production, with most of it behind a login.

What each tier includes, and how a project runs →

No framework is a house style here; I pick the lightest thing that does the job. Most of these sites ship as static files with no build step, which is why they load fast and keep working. When a build genuinely needs a library — three.js for real geometry, GSAP for orchestrated motion — I bring in one, tell you what it adds to the page, and you agree to it before it goes in.