What does a maintenance retainer actually cover?
Website maintenance is one of the least transparent line items in this trade. Not because it's complicated, but because what's in it is rarely spelled out.
Let me start at the end, because that's the fair way: not every site needs a retainer. A rarely changing brochure site with no database and no plugins will run for years without attention. There, renewing the domain and hosting is the only recurring task, and that needs no contract.
The need for maintenance doesn't come from the website, but from the moving parts inside it. There's a separate piece going through what happens to a neglected site. If the site takes payments or bookings, or connects to other systems, the picture changes — there, doing nothing is also a decision, and it has a price.
What a sensible retainer includes
Updates. Keeping the system and its extensions current. The point isn't the newest version but avoiding accumulation: jumping across many skipped versions is far riskier than stepping a little each month.
Backups. One question matters here: has anyone ever restored from one. A backup that was never tested isn't a backup, just a file on the server. This is the item most arrangements mention and fewest people verify.
Fixes. What breaks gets repaired — including what broke by itself because the environment moved on. This is the real content of a retainer: not that somebody works every month, but that there's no separate negotiation when something goes wrong.
Small changes. A text edit, a price update, a new image, opening hours. Individually these are minutes; collectively they are exactly what gets left undone when every small thing needs a quote.
- without upkeepOne large item at the endthe faults arrive together, at once
- with continuous upkeepMany small steps throughoutpredictable load
the same work — different timing and price
What typically isn't included — and that's fine
A new feature isn't. Adding a booking system, another language, a shop: those are projects with their own estimates. Anyone promising them inside a retainer either hasn't thought it through, or has set the price high enough to absorb them.
Writing content isn't either. The text and the images belong to the business; maintenance looks after what exists, it doesn't produce it.
And the hosting fee isn't. This is the most common source of misunderstanding: when the two go as one figure, the client assumes the hosting fee bought the upkeep too. Hosting is the place where the site runs. Maintenance is the work that keeps it running.
Five questions for examining an offer
One: what happens in a month when nothing breaks? The honest answer is that updates and backups still happen, and the rest is availability. That's fine — as long as it's said out loud.
Two: do I get told what happened? Not a report; a few sentences will do. If no word comes for months, that doesn't mean all is well — it means you don't know.
Three: has anyone restored from the backup? If the answer is vague, so is the value of the backup.
Four: how quickly does someone respond if the site is down? This is the one item where response time genuinely matters, and precisely the one usually left out.
Five: can it be cancelled, and what remains afterwards? If the site stops working once the arrangement ends, it wasn't maintenance but rental. There's a separate piece on that too: who your website is tied to.
For my part I do this on a monthly arrangement, for several clients. The amount depends on how large the system is and how often it changes — the maintenance page sets out the detail. One thing I'll say here as well: if your site has no moving parts, don't sign one.
Questions on this topic
Does every website need a maintenance retainer?
No. A rarely changing brochure site with no database and no plugins runs for years without attention; there, renewing the domain and hosting is the only recurring task. A retainer is justified where there are many moving parts: a regularly updated system, payments, bookings, integrations.
What must definitely be included?
Updates, backups, fixes and availability. On backups the essential question is whether anyone has ever restored from one: a backup never tested isn't a backup, only a file.
How can I tell that nothing happens for the fee?
By there being no trace. If no word arrives about what happened during the month, and the last update date in the admin is old, then the fee buys availability, not work. That can be fine — but then let's call it that.
Is the hosting fee the same as maintenance?
No, and it's worth keeping them apart. Hosting is the place where the site runs; maintenance is the work that keeps it working. Much confusion comes from billing the two as one figure, leaving the client to assume the hosting fee bought the upkeep as well.