Most small business owners paying a monthly maintenance fee could not tell you what they get for it. That is not their fault. The invoice says "website maintenance", the amount leaves the account, and the website carries on looking the same as it did last month. When nothing visibly changes, it is reasonable to wonder whether anything happened at all.
I run a small web development studio in South Wales and maintenance is a big part of what we do. So here is the unglamorous version: what the work actually consists of, why most of it is invisible by design, and how to tell whether the person you are paying is doing any of it.
The invisible work is the point
A maintenance month that goes well produces no news. Nobody rings to say the site is down, no customer emails to say the contact form bounced, no search ranking quietly evaporates. The absence of events is the deliverable.
That creates an awkward dynamic. The better the work, the less there is to show for it. Which is exactly why a maintenance arrangement should come with a record of what was done, even when what was done was small.
What the work actually is
Dependency and platform updates. Every site is built on layers of other people's code, and those layers get security patches. Applying them is routine right up until it is not: an update occasionally changes behaviour somewhere unrelated, which is why they get applied and then checked rather than applied and forgotten.
Backups you have actually tested. A backup nobody has ever restored is a belief, not a backup. The only way to know it works is to restore it somewhere safe and look at the result. Untested backups fail at the exact moment you need them.
Uptime and certificate monitoring. SSL certificates expire, usually renewing automatically, occasionally not. A lapsed certificate replaces your homepage with a browser security warning, and the first person to notice is normally a customer.
Form delivery checks. I have written at length elsewhere about contact forms that accept a message, thank the visitor, and quietly discard the enquiry. A monthly end-to-end test costs about a minute and catches the failure that costs the most.
Search visibility monitoring. Not rank chasing, just watching for the sudden drops that indicate something broke: pages falling out of the index, a stray noindex tag, a crawl error appearing across a section of the site.
Content and detail corrections. Prices that moved, staff who left, opening hours that changed at Christmas and never changed back. Small, constant, and the thing customers actually notice.
The failure I see most often
The most common problem in sites I take over is not a hack or a crash. It is drift. Nobody did anything wrong; nobody did anything at all. Plugins sit three years behind, the copyright notice says 2021, a phone number points at a disconnected line, and the enquiry form posts to an address nobody has opened since the person who set it up moved on.
Drift is slow enough that no single month feels negligent, and it compounds. By the time it becomes visible it is a rebuild rather than a repair, which is a far more expensive conversation than the one that would have prevented it.
How to tell if you are getting the service
Three questions, none of which should be difficult to answer:
"What did you do last month?" A specific answer beats a reassuring one. "Applied the framework patch, restored the backup to a staging copy and checked it, confirmed the contact form delivered" is a real answer. "Everything is running fine" is not.
"When did you last restore a backup?" If the answer is that backups exist, that is a different question to the one asked.
"How would you know if the contact form stopped working?" If the answer depends on somebody complaining, then the answer is that they would not know.
None of this requires you to understand the technical detail. It requires the person doing the work to be able to describe it in plain terms, which is a fair expectation of anyone taking a monthly fee.
What it is reasonable to pay
I am not going to pretend there is a universal number, because it depends on what the site does. A brochure site with five pages and a contact form is genuinely low effort to keep healthy. A site taking bookings or payments is not, because the failure modes are worse and more of them matter.
The thing worth insisting on is that the arrangement is written down: what is covered, what counts as a change request rather than maintenance, and how quickly something broken gets looked at. Most disputes I hear about are not about price. They are about two people holding different assumptions about what the fee included.
If you want the detail of how this is priced and scoped in practice, we have written it up properly on our website maintenance service page.
The short version
Maintenance is insurance you can inspect. The work is real, most of it leaves no visible trace, and the only way to know it is happening is to ask for specifics and get them. A website that has been quietly ignored for two years rarely announces the fact. It just slowly stops earning its keep, and then one day the form has been broken for nine months and business was never actually quiet.
Jack Warner is the founder of WebDev Wales, a web development studio based in Glynneath, South Wales, building and maintaining websites for small and medium businesses.
Top comments (0)