The Maintenance Plan Conversation Nobody Wants to Have

Nobody likes paying a monthly fee for something they don’t think about. And a well-maintained website is, by design, something you don’t think about. This creates a weird business problem: the better the maintenance, the less anyone notices it’s happening, the easier it is to cancel, the sooner something breaks, the more everyone remembers why it existed.

Let’s have the conversation openly instead of letting it play out awkwardly.

What a maintenance plan is for

It’s not for adding features. It’s for keeping what you already have from breaking. Three specific categories:

Software upkeep. WordPress updates, plugin updates, PHP version bumps, security patches. Most of these are fine to apply automatically. Some break things when applied automatically. A human needs to be in the loop, watching for the ones that break.

Monitoring. Is your site up? Is it fast? Has a form stopped submitting? Has a certificate expired? Has a search console started flagging errors? The answer to all of these should be “yes, someone is watching” — because you don’t want to find out your contact form broke three weeks after it stopped working.

Small fixes. Typos in the footer. A broken link. A plugin setting that needs tweaking. A new staff member who needs an author account. An image that isn’t loading. Individually, none of these are worth a meeting. Collectively, they’re the difference between a site that feels cared for and one that visibly isn’t.

What happens without one

The realistic version:

1. Your site works fine for a while.
2. Something small breaks. You don’t notice.
3. Something bigger breaks three months later. You notice.
4. You call the developer who built it. They’re busy.
5. You call someone else. They need to learn the site before they can fix anything. That takes an hour and costs more than three months of maintenance would have.
6. The site gets patched. Other things are found. The bill grows.
7. Everyone agrees this was worse than just having someone on retainer.

This cycle is extremely normal and entirely avoidable.

What a reasonable plan looks like

Most small-business sites need between 2 and 6 hours of maintenance per month. That covers updates, monitoring, and a queue of small fixes. Not a large budget — but it has to be consistent.

A good plan usually includes:

• Automated uptime and performance monitoring with human review
• Scheduled WordPress core, plugin, and theme updates, tested in a staging environment first
• Weekly or monthly security scans
• Regular backups, verified to actually restore
• A monthly report showing what was done and what was found
• A shared task list where you can drop small fixes and they get handled within the plan

What it shouldn’t include: new features, redesigns, or big content pushes. Those are separate projects. If your maintenance plan is being used as a slush fund for feature work, nothing is getting maintained properly.

The fair price

For a standard small-business site, expect somewhere between $150 and $500 per month depending on the size, the host, and the scope of monitoring. That’s not a huge number compared to what a single emergency bill costs. It’s also dramatically less than the cost of rebuilding a neglected site in two years.

If you’re being quoted thousands of dollars a month for a small site, either the scope is larger than you need or someone’s padding the bill. If you’re being quoted under $100 a month, they’re probably not doing much — check what’s actually covered.

The conversation to have

When you’re evaluating a maintenance plan, ask these questions:

1. What exactly is included each month?
2. What counts as “maintenance” and what counts as “new work”?
3. How often will I hear from you, and what will that look like?
4. If something breaks at 11pm on a Sunday, what happens?
5. Can I see a sample monthly report from another client?
6. What happens to my backups if I cancel?

You’re looking for concrete answers. “We handle everything” is not a concrete answer. “We apply updates on the second Tuesday of each month after testing in staging, we run monitoring through UptimeRobot with alerts going to my phone, and emergencies inside business hours get a 4-hour response” is.

The fear nobody says out loud

Some clients worry that paying for maintenance means they’re paying for nothing — because in a good month, nothing visible happens. That’s a reasonable feeling, and the answer is a monthly report. Even if the report says “applied six plugin updates, ran one backup restore test, fixed the small form bug you emailed about,” that’s a record of work done and value delivered.

No report, no plan. Get one that includes it, and the fee starts feeling less like nothing and more like the cheapest insurance you’re buying this year.

Photo by Andrea Piacquadio on Pexels.