Website maintenance for a small business: what a care plan should actually cover

This page may contain affiliate links from which Blur Studio earns commissions.

Once a website is live, "maintenance" covers a specific, recurring set of tasks, not a vague ongoing worry. Knowing what those tasks actually are is the difference between a care plan that's worth paying for and one that's just a monthly fee for something nobody's really checking.

What a real care plan should cover

• Software and security updates. If your site runs on WordPress or a similar platform, the core software, plugins and themes all need regular updates, both for security and to keep working with newer browsers and devices. A site built as custom code needs less of this specific maintenance, but still needs its dependencies kept current.
• Backups, actually tested. A backup that's never been restored even once isn't a real safety net, it's an assumption. A proper care plan includes regular backups and at least occasional confirmation that they'd actually work if you needed them.
• Uptime and error monitoring. Automatic checks that catch a site going down, a broken page, or a form that's silently stopped working, ideally before a customer notices and tells you about it instead.
• Someone who actually looks at what those checks find. This is the part that separates a real care plan from a purely automated one: a person reviewing what came up each week or month, deciding what matters, and fixing the small things before they become big ones.
• Small fixes and content updates, agreed up front so you're not paying a separate invoice every time something minor needs changing.
• A simple way to see how the site and the business are actually doing, not just whether it's technically online, since the point of maintenance is ultimately protecting the business the site supports, not the code itself.

Warning signs you've already outgrown "no maintenance"

• You've genuinely forgotten the last time you looked at the site yourself. If you can't remember, it's likely been long enough that something small has quietly gone wrong without anyone noticing.
• A customer has told you about a problem before you found it yourself. This is the clearest sign that nobody is actually watching, since the whole point of maintenance is catching things before a customer does.
• You don't actually know if your backups work. If you've never tested a restore, you don't have a backup plan, you have an assumption.
• The site is now bringing in real bookings, leads or sales, which changes the cost of an hour of downtime from "mildly annoying" to "a real, measurable loss."

Realistic cost ranges

• $0, do-it-yourself: relying on your host's built-in backup and update tools (many hosting platforms, including Netlify's own deploy previews and instant rollbacks, make some of this close to automatic) plus checking the site yourself periodically. Genuinely workable for a very simple site with low stakes if something breaks for a day.
• $20 to $50 a month, basic automated monitoring: an uptime-checking service or a hosting add-on that alerts you if something goes down, with no human actually reviewing anything unless an alert fires.
• $100 to $300 a month, a freelancer's basic retainer: a developer who checks in periodically, applies updates, and handles small fixes, usually with a cap on included hours per month.
• $300 and up, a fuller care plan with weekly attention: regular (often weekly) checks by an actual person, a written report you receive on a schedule, and small fixes or updates included rather than billed separately each time.

Where a specific plan lands in this range depends almost entirely on how often a real person is actually looking at your site, versus how much is purely automated with nobody reviewing the output. Hosting itself is a separate cost, covered in how much it costs to host a website.

Do it yourself vs. hire someone

Do it yourself genuinely works when: your site is simple, a short outage wouldn't meaningfully hurt the business, and you're comfortable checking it periodically yourself or setting up a free uptime alert.

Hiring makes sense when: the site is actively bringing in business (bookings, leads, sales) so downtime has a real cost, you don't have the time or technical comfort to check it yourself regularly, or you want someone who'll notice a slow decline (a dropping conversion rate, a page quietly broken for a month) rather than just a hard outage.

Before hiring anyone for this, ask a few direct questions: what exactly gets checked, and how often; is it a person reviewing results or purely an automated alert; what happens, and how fast, if something actually breaks; and do you keep full ownership of your code and accounts if you ever leave. A vague answer to any of these is worth treating as a warning sign, since "maintenance" is specific, checkable work, not a mysterious ongoing service you're meant to trust without detail. It also helps to know who hosts your website and who fixes it when it goes down.

How Blur Studio's own Care plan is structured

My own Care plan runs $349 a month with no lock-in, and it's built around the things above done properly rather than just automated and left alone: weekly checks on your app, done by me personally, not just an automated script; a short weekly report in plain language covering how your app is doing and what to do next; small fixes and updates included each month, agreed up front; a dashboard with the numbers that actually matter for your specific kind of business; and a monthly call with me, plus a deeper check every three months. Everything gets logged in what I call a Service Record, a running log of every check, fix and update, similar to a car's service book, so there's always a clear record of what's been done. If you leave, you keep everything: the code, the record of all the work, and anything else built along the way.

This sits closer to the higher end of the cost ranges above, deliberately, because it includes an actual person checking your site every week rather than just automated monitoring running quietly in the background with nobody reviewing what it finds.

A worked example: a local service business with an active booking site

Say your site takes real bookings and a broken form for even a day means lost business you'd never know you lost. For a site like this, the DIY or basic-monitoring end of the range genuinely isn't enough, since nobody's actually watching for the quieter problems (a form that silently stops submitting, a page that's slowly losing its search ranking) that an alert-based system won't catch at all. This is exactly the situation a weekly-check care plan is built for: catching the problem before a customer does, and having a record of exactly what's been checked and fixed along the way. If a broken page does slip through, a rollback can fix it fast, as in going back to yesterday's version.

How I'd approach this

My honest advice: start by being realistic about what a short outage or a silently broken page would actually cost your business, not what maintenance "should" cost in the abstract. A simple hobby site genuinely doesn't need a paid care plan. A site that's actively driving bookings, leads or sales usually does, and the right question isn't whether to pay for maintenance, it's whether what you're paying for actually includes a person looking at it regularly, or just an automated check running quietly with nobody reading the output.