Can I not just click the update button myself?

You can, and for a simple site you may be fine for a long time. The risk is not the clicking, it is the month a plugin update conflicts with your theme and takes the site down while you are asleep. What you are paying for is that the update was rehearsed somewhere else first, that there is a restore point that has been proven to work, and that somebody other than you notices when it breaks.

What actually happens if the site goes down at two in the morning?

Monitoring pings the site from outside on a short interval, so the alert arrives without waiting for a customer to tell you. What happens next depends on the response time written into your plan. Some plans are next-business-day and some are same-day for a store. That number is agreed in writing before the plan starts, because a promise of round-the-clock cover that nobody sat down and costed is worth nothing.

Do unused small-change minutes roll over?

No, and that is deliberate on both sides. Rolled-over minutes accumulate into a bank that gets spent in a single week, which turns a predictable plan into an unpredictable one. The allowance resets each month. Work beyond it is quoted separately before it starts, never billed as a surprise.

Why does a shop cost more than a brochure site?

Because downtime on a shop is money leaving in real time, and because a store has more moving parts that change without warning — payment gateway updates, shipping plugins, tax rules, stock feeds. The checking is longer, the tolerance for a broken update is lower, and the response time in the plan is usually tighter.

What happens if an update breaks something on staging?

It gets held back, not forced through, and you are told which update it was and what it broke. Sometimes the honest answer is that a plugin has been abandoned by its author and needs replacing, which is a separate piece of work with its own quote. A held-back update is the plan working, not the plan failing.

Am I tied in for a year?

No. It runs month to month. A care plan that needs a long lock-in to make sense is usually one that is not delivering enough each month to justify itself, and you should be able to see the value in the monthly report rather than in the contract.

Web Development & Engineering

Website maintenance and care plan

Updates rehearsed on staging, backups that have actually been restored, uptime watched, and a written limit on what the small-changes allowance covers.

From: $80–$600/mo
Typical time: ongoing
Usually bought by: Every website client

What this actually solves

The site went live, the developer moved on, and you were left holding something you do not have the vocabulary to look after. Nobody told you that plugins expire, that an SSL certificate renews, that a backup is not the same thing as a restore. So nothing gets touched, because touching it feels dangerous, and eighteen months later the site is running software with published security holes and a contact form that quietly stopped delivering in March.

That last one is the part owners find hardest to believe. Contact forms do not announce their own failure. A mail provider changes an authentication rule, or a plugin update changes how mail is sent, and the form keeps showing its cheerful thank-you message while the enquiries go nowhere. There is no error, no bounce, no alert. The first sign is usually a customer phoning to ask why nobody replied, and by then you have no way of knowing how many did not bother to phone.

So what is actually being bought here is not a list of technical chores. It is the removal of a low, constant worry — the sense that something is quietly rotting and you would not know until it was expensive. The chores are just how that gets delivered.

What we do, and in what order

The value is in the order and in the proof, not in the individual tasks. Anyone can press update. The difference is where it gets pressed first and what gets checked afterwards.

Set the plan up properly once. Access collected and stored securely, monitoring configured to check the site from outside, a staging copy created, off-site backups scheduled somewhere that is not the same server as the site, and the scope written down — including the small-changes allowance and the response time. This is a one-off at the start. Half a day to a day.
Rehearse the month's updates on staging, then promote them. Core, plugins, themes and dependencies go onto the staging copy first. The site is then walked through — the pages that matter, the checkout if there is one, the form. Anything that breaks is held back and reported rather than forced onto the live site. Only what passed gets promoted. One to three hours a month, longer on a store.
Restore a backup and prove it works. Not check that a backup file exists — actually restore it somewhere and open the result. This is the step most plans skip, and it is the one that matters, because a backup nobody has restored is a belief rather than a safety net. Corrupt archives, partial database dumps and backups that silently stopped running weeks ago are all common and all invisible until the day you need them. Thirty to sixty minutes a month.
Run the checks that catch silent failures. Submit the contact form and confirm the email physically arrives in the inbox it is meant to reach. Confirm SSL is valid and not about to lapse. Run a security scan. Look at the month's uptime record and the response times behind it. Check the loading numbers against last month so a slow drift gets caught while it is still small. Thirty minutes a month.
Do the small changes, then write the report. Content edits, a new photo, changed opening hours, a price update — up to the agreed allowance. Then a short report in plain English saying what was done, what it means for you, what is being watched next month, and anything waiting on a decision from you. If the month was quiet, the report says the month was quiet. That is good news, not a reason to pad it. Thirty to sixty minutes a month.

Tools, so you know what is running rather than taking it on faith: UptimeRobot or BetterStack for external monitoring, UpdraftPlus or the host's own snapshot system for backups, and ManageWP or MainWP where several sites are being looked after from one place. Each site has a written record of its plan, its dates and what was done, so the history does not live only in somebody's memory.

What moves the price

The range is $80–$600/mo, it runs ongoing rather than in a fixed block, and it is set by four things.

What the site is built on. A static site with no database and no plugins needs very little attention — monitoring, certificate watch, an occasional content edit. A WordPress build with two dozen plugins has two dozen independent authors shipping changes on their own schedules, any of which can conflict with another, and every one of those has to be rehearsed rather than trusted.

How much small-change work is included. The allowance is the single biggest variable and the one most worth being precise about. Thirty minutes a month and two hours a month are genuinely different plans, and it is better to price the larger one honestly than to price the smaller one and then argue about it every month.

Whether money moves through the site. An active store raises the price for reasons that are not about effort alone. The checks are longer, the update caution is higher, and the response time in the plan is tighter, because every hour of downtime has a number attached to it that a brochure site simply does not have.

What usually goes wrong

The small-changes allowance is written without a limit. The plan says small changes are included, everyone nods, and by month three the requests add up to three hours of work a month with nothing written down to measure them against. It poisons an otherwise good relationship. The wording that prevents it is specific and unglamorous — sixty minutes of small changes are included each month, work beyond that is quoted separately, and unused minutes do not carry forward.

The backups have never been restored. Plans advertise daily backups and almost none of them ever open one. Backups fail silently in all the usual ways — the plugin stopped after an update, the destination filled up, the database dump completed but the file archive did not. The month it matters is the worst possible month to find out. A restore takes half an hour and converts a claim into a fact.

Nobody tests the contact form. It is the most valuable thing on many small business sites and the thing most likely to break without a single visible symptom. A form that stops delivering costs you every enquiry until someone notices, which is often months. Actually submitting it and confirming the mail lands takes two minutes and is worth more than most of the rest of the checklist.

See where the site stands before you brief anyone.

If the site is already live, start from what it scores rather than from a guess. The audit reports what it checked, what it found, and — the part most tools leave out — what it could not check, and why.

See the website audit Talk about this work

Questions people ask before they commit.

Can I not just click the update button myself?: You can, and for a simple site you may be fine for a long time. The risk is not the clicking, it is the month a plugin update conflicts with your theme and takes the site down while you are asleep. What you are paying for is that the update was rehearsed somewhere else first, that there is a restore point that has been proven to work, and that somebody other than you notices when it breaks.
What actually happens if the site goes down at two in the morning?: Monitoring pings the site from outside on a short interval, so the alert arrives without waiting for a customer to tell you. What happens next depends on the response time written into your plan. Some plans are next-business-day and some are same-day for a store. That number is agreed in writing before the plan starts, because a promise of round-the-clock cover that nobody sat down and costed is worth nothing.
Do unused small-change minutes roll over?: No, and that is deliberate on both sides. Rolled-over minutes accumulate into a bank that gets spent in a single week, which turns a predictable plan into an unpredictable one. The allowance resets each month. Work beyond it is quoted separately before it starts, never billed as a surprise.
Why does a shop cost more than a brochure site?: Because downtime on a shop is money leaving in real time, and because a store has more moving parts that change without warning — payment gateway updates, shipping plugins, tax rules, stock feeds. The checking is longer, the tolerance for a broken update is lower, and the response time in the plan is usually tighter.
What happens if an update breaks something on staging?: It gets held back, not forced through, and you are told which update it was and what it broke. Sometimes the honest answer is that a plugin has been abandoned by its author and needs replacing, which is a separate piece of work with its own quote. A held-back update is the plan working, not the plan failing.
Am I tied in for a year?: No. It runs month to month. A care plan that needs a long lock-in to make sense is usually one that is not delivering enough each month to justify itself, and you should be able to see the value in the monthly report rather than in the contract.

Often taken together.

Start with the brief, not the invoice.

Send what you are trying to achieve. You get a written scope, a price and a date — or an honest “this is not the right service for that”.

Talk about Website maintenance & care plan All Web Development & Engineering services