No handover
The usual way a web project goes wrong is a handover: sold by one person, built by another. There is no handover here, because there is nobody to hand over to. I take on a limited number of jobs at a time, and when I am full, I say so rather than take a deposit and sit on it.
Before this
Five years at an IT managed service provider in Norwich, where I finished as a service engineer still running the first-line team of six. Servers, Azure, cloud identity, networks and the machines on people’s desks, for businesses paying somebody to pick up the phone when it all stopped. That is why the support side of this is a real offer rather than an add-on bolted onto web design, and it is the part most people building websites cannot do.
How it works
You get a fixed price in writing before anything starts, and you see the site while it is being built rather than at the end. The code is yours when it is done. If you want me to keep looking after it, that is the monthly option, and if you want to take it elsewhere you can, and I will help you move it.
Two things happen here: helping you grow, and keeping it running. Growing means a new website, a full brand, and being found in search and in AI answers. Keeping it running means ongoing IT support: backups, email, the laptop that will not start.
I am based in Lowestoft, Suffolk, and the work is remote first, deliberately: a client in Lowestoft and one on the other side of the world get the same attention on the same day. When a support job needs hands on the equipment, I come out anywhere in Suffolk by arrangement. Local knowledge still counts for the search work, because I know which towns your customers search from and which trades are competitive round here.