Build
New websites, rebuilds, migrations, and ageing sites that need a stronger foundation.
Builds, rebuilds, and ongoing care.
Most projects begin with a conversation and a clear look at what the website needs: what is working, what is drifting, and what should be handled first.
Ongoing care
Regular checks, updates, uploads, fixes, visibility monitoring, and operational maintenance.
Build + stewardship
A proper rebuild followed by ongoing care, refinement, and website health checks.
How it works
01
Initial call
02
Website review
03
Action points
04
First version
05
Final polish
06
Ongoing stewardship
Websites decay when nobody is looking after them.
Health is not one thing. It is speed, structure, accessibility, search visibility, reliability, content quality, and knowing when something has changed. The workspace gives that ongoing care somewhere to live, so notes, files, audits, checks, and small improvements stay connected to the site.
Selected projects.
Founder
CopyLint
A custom auditing engine for checking copy, metadata, terminology, and consistency across pages.
Client
Connection Clinic
A new therapy practice website built around trust, service clarity, and long-term maintainability.
Practice system
GoAgain
A single-page progressive web app for rhythm practice, built as an interactive product rather than a conventional website.
What clients say.
“An absolute joy to work with - incredibly prompt with changes and strikes the perfect balance between asking for my input and sharing his professional expertise.”
Becky CF.
Connection Clinic
“He understood what the site needed beyond just the design - structure, usability, performance, and how it would be maintained over time.”
Hayley S.
Mother's Memoirs
Things I've been thinking about.
MODERN WEB · OPERATIONS
The problem with “finished” websites
One of the stranger ideas in web development is the idea of the “finished” website.
A business launches a redesign, signs off the final round of amends, pushes everything live, and from that point onward the website is often treated as complete. Attention moves elsewhere. The project is done.
Except it usually isn’t. Content changes. Services evolve. Search behaviour shifts. Dependencies age. The website keeps moving whether anyone actively maintains it or not.
How I got here.
I came to software through music: teaching, performing, writing, and eventually publishing Beginner to Composer In 14 Days.
That background still shapes how I work. Music teaches you to notice structure, repetition, feedback, and small improvements made consistently over time.
Those same ideas now sit underneath my web work: clear systems, maintainable tools, and websites that keep improving after launch.
I still write, compose, and build practice tools alongside client work.
