Most sites I build use WordPress. For sites that rarely change, there's a second option — a static site, which will be faster to load, with less that can go wrong, and a lower cost to maintain. Want to know more? Carry on reading for what that means, and what the trade-off is for you.
A normal WordPress site runs live software on the server every time someone visits — checking a database, running plugins, assembling the page on the fly. That's powerful, but it's also the whole reason WordPress sites need ongoing security work: updates, monitoring, and they carry a login page that's a permanent target.
A static site has none of that running live. Every page is built in advance into plain files, then simply served with nothing to hack, no database to break into, and nothing that needs monthly patching. It's a genuinely different set-up, with a much lower chance of anything going wrong.
You're paying for the design and development work, not the platform underneath it — so the build price is the same as a WordPress build: Quick launch from £350, Simple site £500, Multi-page from £800. Full detail on what each tier includes is on the main Wordpress page.
A WordPress site needs the ongoing work covered by the £180/year Managed hosting tier — core, plugin, and theme updates, security monitoring, an admin login that needs watching. A static site doesn't carry any of that workload, so it doesn't cost the same to keep running.
[1] Same rate as everywhere else on this site — £50/hour, and most requests take under an hour. If you're likely to want frequent changes, that's usually a sign WordPress is the better fit from the start and I'm happy to talk through which makes more sense for what you need.