A maintenance invoice arrives every month, and in most companies nobody can say what it bought. The site did not break, so presumably something worked. That is a difficult feeling to budget around, and it is why website maintenance is the first line people cut and the first thing they regret cutting.
This is what website maintenance services actually cover, what separates a real retainer from a line item, and the questions worth asking before you sign one.
What Website Maintenance Actually Means
Maintenance is not a single job. It is two quite different kinds of work bundled under one word, and confusing them is where most disappointment starts.
The Work You Can See
Content changes, a new team member on the about page, a price update, a landing page for next month’s campaign. This is the part clients think they are paying for, because it is the part that produces something visible.
The Work You Cannot
Updates applied and tested, backups taken and verified, certificates renewed, error logs read, a plugin swapped out before its abandoned code becomes a way in. None of this shows up anywhere. All of it is the reason the visible work is still possible next year.
What Should Be in Every Maintenance Plan
Five things. If a proposal is missing any of them, it is a support arrangement rather than a maintenance plan, which is fine as long as everyone knows which one they bought.
Core, Plugin and Theme Updates
Applied on a staging copy first, checked, then pushed live. Updating straight on production and hoping is common, cheap and the single most likely cause of a site going down on a Friday afternoon.
Backups You Have Actually Restored
Everyone takes backups. Far fewer have ever restored one. An untested backup is a belief, not a safety net, and you find out which it is on the worst possible day. Ask when the last test restore happened and what it took.
Security Monitoring and Malware Scanning
File integrity monitoring, a firewall in front of the login, and someone who reads the alerts. Most compromises are not sophisticated. They are automated scans finding a plugin that stopped receiving updates fourteen months ago.
Uptime and Performance Checks
Uptime monitoring is table stakes. Performance monitoring is the part that matters commercially, because sites do not usually fail, they slowly get heavier until the phone stops ringing and nobody connects the two.
A Named Allowance for Small Requests
An hour or two a month for the small changes, written down in hours rather than described as reasonable. Reasonable is where retainers go to die.
Maintenance is insurance you can measure. The month it feels like a waste of money is the month it is working.
What Website Maintenance Services Cost
The range is genuinely wide, and any agency that quotes you a monthly figure before seeing the site is guessing. Three things move the number more than anything else.
How Much Custom Code Is in There
A site built from a standard theme with well known plugins is cheap to look after, because everything in it is maintained by someone else. A heavily customised build costs more, because every update is a question rather than a routine.
How Often Content Changes
A brochure site that changes twice a year and an ecommerce catalogue that changes daily need completely different arrangements. Buying the second and paying for the first is the most common overspend we see.
What Happens When Something Breaks
Response time is the real cost driver. Next business day is inexpensive. Four hours including weekends means someone is on call, and that is a different price for good reasons.
The Questions to Ask Before You Sign
Ask what is explicitly excluded, and be suspicious of an answer that has to be improvised. Ask who holds the hosting and domain logins. Ask what the report looks like, and request last month’s for another client with the name removed. Ask what happens to the backups and the access if you leave.
The answers matter less than whether they are ready. A team that maintains sites properly has all of this written down already.
When You Do Not Need a Retainer
If your site is small, rarely changes, runs on a managed host that handles updates, and you have someone internally who can log in and fix a typo, you may genuinely not need one. Paying monthly for reassurance you already have is not a strategy.
What you do still need is a backup you have tested and a plan for the day something goes wrong. Maintenance is one way to buy that. It is not the only one.
The Takeaway
Maintenance is not a subscription to nothing happening. It is the ongoing cost of an asset that is on the internet, being scanned continuously, and running software that changes underneath it every few weeks.
- Separate visible content work from invisible technical work in the contract.
- Insist on staged updates, tested restores and someone reading the alerts.
- Get the small change allowance written in hours, never in adjectives.
- Match the response time you buy to what downtime actually costs you.
- If the site rarely changes, a tested backup may be enough on its own.
If you are not sure whether your current plan covers any of this, we are happy to read it and tell you. That is the sort of thing our website design and development team looks at every week, and you can send it over here.