Do you know what your website maintenance plan actually bought you last month?
Most owners can't answer that, and it isn't because they're careless. It's because website maintenance plans are usually sold as one line item covering three different jobs, and the invoice never separates them. The result is a monthly charge that feels reasonable, produces nothing you can point at, and quietly becomes the thing nobody wants to bring up.
The three jobs are worth naming, because almost every dispute we see between an established company and its web vendor traces back to the blur between them.
Hosting is renting the machine your site runs on. It's a commodity, it's cheap, and it happens whether anyone is paying attention or not.
Maintenance is keeping the software on that machine patched, backed up and working. Updates, security fixes, monitoring, restoring the thing when it breaks.
Improvement is making the site better than it was. New pages, new sections, changes that respond to what your buyers are doing.
A plan priced as though it covers all three, while scoped to deliver only the first two, is the most common arrangement in this market. It isn't usually dishonest. It's just written loosely enough that any month's work can be described as covered, which conveniently means no month's work can be checked.
What website maintenance plans should include
A plan worth paying for names its scope in writing. Not in the proposal's marketing section, in the actual agreement. At minimum it should specify:
- Update cadence. How often the content system, plugins and dependencies get patched. Monthly is normal. Quarterly is a decision, not a default.
- Backups, and whether restores are tested. A backup that has never been restored from is a belief, not a backup.
- Monitoring, and who gets alerted. Uptime is the obvious one. Error monitoring and form-submission monitoring matter more, because a quote form that silently stopped sending email will not show up as downtime.
- Included changes. How many hours of content or layout work are covered, and what counts as a change versus a project.
- Response and resolution times. These are different things, and pinning both down is what a service level agreement is for.
- What's excluded. The most useful sentence in any maintenance agreement is the one listing what gets quoted separately.
That last point is the one to push on. Vague scope isn't generous, it's ambiguous, and ambiguity in a service agreement resolves in favor of whoever wrote it.
The test you can run this week
Ask your vendor for a dated log of everything they changed on your site last month.
That's the whole test. It takes one email and the reply tells you more than a year of invoices.
A team doing real maintenance produces it in a day, because the log already exists. It lives in their ticketing system or their version control, and exporting it is a two-minute job. A team that has been quietly collecting a retainer will produce something written after you asked: a summary in categories rather than events, describing the kind of work they do rather than the work they did.
Neither reply is an accusation. But one of them is evidence and the other one isn't.
If you want a second data point, ask when the content system was last updated and to what version. A specific version number that's close to current is a good sign. A vague reassurance that everything is up to date is the same non-answer in a different shape.
What accumulates when maintenance is skipped
Deferred maintenance is not a flat cost. It compounds, and it does so invisibly for a long time.
Every month of skipped updates widens the gap between your site's software and the current release. For a while, nothing happens. Then the gap gets wide enough that updating is no longer a task, it's a project, because the jump spans breaking changes that have to be worked through one at a time. Companies that cancel maintenance to save a few hundred a month often discover two years later that closing the gap costs more than the maintenance would have.
The security dimension is the one that gets attention, and it's real. But the more common outcome for a B2B company is quieter: a site that gradually stops working properly in ways nobody inside the company notices, because everyone inside the company already knows where everything is. The contact form that stopped delivering. The certification page that 404s from the footer. The mobile layout that broke when a plugin updated itself.
Our audit of more than 55,000 B2B websites found that 57% give a buyer no clear next step above the fold, and one in three keep the phone number in the footer only. Not all of that is neglect. A fair amount of it is drift, which is exactly what maintenance is supposed to catch and usually isn't scoped to.
The ownership question hiding inside the plan
There's one more thing worth confirming before you renew, and it has nothing to do with the work.
If the plan bundles hosting on infrastructure you can't access, a content system you have no login to, and a domain registered to the vendor rather than to your company, then cancelling maintenance doesn't just end the maintenance. It ends the website. That's a materially different arrangement from the one most owners believe they bought, and it's much better discovered at renewal than during a disagreement.
The check takes ten minutes. Can you log in to the content system as an administrator? Is the domain registered to your company, with someone at your company as the admin contact? Do you have access to the code, wherever it lives? If any answer is no, that's worth resolving while the relationship is good. We wrote about the fuller version of this in you don't own your website.
None of this is an argument against paying for maintenance. A B2B site running current software, with tested backups and someone actually watching the error log, is worth the monthly cost and considerably cheaper than the alternative. The argument is for knowing what the line item buys, because the same $500 a month buys wildly different work depending on who wrote the scope.
If your plan turns out to be mostly hosting with a monitoring dashboard attached, that's useful to know. It means the money you thought was going into keeping the site current is available to actually keep the site current. For where that sits against a bigger decision, see how much a B2B website costs and how to choose a web design company.
