What six small-business sites taught me about maintenance

Alongside the bigger agency projects, I look after a handful of small-business sites directly — a groundworks company, a fuel management firm, a canal-side studio, a care home, a sweep, a leadership consultancy. None of them are technically exciting. All of them have taught me something about what “maintenance” actually means once the launch excitement wears off.

Updates are not optional, but timing is a choice

Plugin updates break things. Not often, but often enough that “update everything the moment it’s available” and “never update anything” are both bad strategies. What works is a staging copy, a five-minute click-through of the pages that actually make the business money, and updates on a schedule the client never has to think about.

The client doesn’t care about your stack

They care that the contact form emails them and the site loads on their phone in the van. Every one of these projects reminded me that clever architecture is worth nothing if the boring, visible things are flaky. I’ve gotten a lot more disciplined about testing forms after every deploy because of exactly one incident I’d rather not repeat.

Small sites still deserve a proper process

It’s tempting to treat a five-page brochure site as “not worth” version control or a staging environment. It is worth it — the sites are small, not the consequences of getting them wrong. Every one of these now gets the same git-backed, staging-first workflow as the bigger builds, just scaled down.

None of this is groundbreaking. It’s just the stuff that only becomes obvious after you’ve maintained enough sites for long enough.