Comparison
Website maintenance plan vs DIY: do you really need one?
On a care plan, my team does the updates, backups and checks. Doing it yourself means you do them.
Overview
The question I ask first
I settle website maintenance plan vs DIY with one question: who on your side updates the site every week? If there is a person who takes a backup first and checks that backups restore, doing it yourself works, and you should carry on. If nobody has that job, a care plan hands it to my team.
The work is the same either way. A WordPress site needs its core, plugins and theme updated for as long as it is live, and a Next.js site needs its dependencies kept current.
Comparison
Website maintenance plan vs DIY, task by task
Each row is a task that any live site needs, with what it asks of you on each side.
A staging copy is a private copy of your site where updates are tried first. The live site only gets an update once it has worked there.
| CRITERION | Doing it yourself | Care plan |
|---|---|---|
| Updates | ~Yours to run, with a backup before and a check after | ✓Weekly, on a staging copy, after a backup |
| Backups | ~The host's copy, plus any you keep elsewhere | ✓Kept off the host and restored on a schedule as a test |
| Spotting a problem | ~Your own checks, or a monitoring tool you set up | ✓Uptime, login and file-change alerts that reach a person |
| When something breaks | ~You work out the cause, or call someone in | ✓My team, who already know the site |
| Security | ~Your own review of users, plugins and XML-RPC | ✓Closed during the first audit and kept closed |
| Small changes | ✓You make them in the editor | ✓Included up to an agreed amount |
| Reporting | ~Your own notes | ✓A monthly report of what was done |
| Cost | ✓No monthly bill; your time instead | ~One flat monthly line |
- No monthly bill
- You set the timing
- Small changesboth
- Backups restored as a test
- Alerts reach a person
- Someone who knows the site
- A monthly report
Why it matters
Keeping a site current, with or without me
Most of the hacked WordPress sites I repair came in through an old plugin. Exposed usernames and an open XML-RPC are the next two doors. Weekly plugin updates close that route. That is why updates come first on the plan. A repair after a break-in is much harder when there's no clean backup to restore from.
On the plan, an alert from the uptime, login or file-change monitor goes to a person on my team, who looks at the site and tells you what was found.
Monitoring can be done yourself too. An uptime monitor emails you when the site stops responding, and the login and file-change logs show who has been in and what changed.
A website maintenance DIY routine has five parts, and I will send you the checklist after the call.
- Take a backup and store it away from the host
- Update core, plugins and theme on a staging copy first
- Click through the main pages on a phone
- Restore a backup somewhere, now and then, to prove it works
- Read the login and file-change logs
What the research says
Four published figures on speed, trust and checkouts
Speed, trust and checkout figures, each from a separate published study.
These figures are other people’s research, quoted as published. Your own site’s numbers come from the free checks and the audit.
Plan or DIY, the same first step
Take the backup before you press update. If the update breaks the site, that backup is the one you restore.
Case study
Activus, IMX and Arch Management Group
Activus Insurance wrote in their review: "This is the second website he has created for us."
IMX Maintenance ended their review by saying they'd hire us again, and Arch Management Group described me as "professional, responsive, and skilled".
Pricing
Paying for upkeep: your time or a monthly line
Doing it yourself costs time every week and nothing on an invoice. If an update goes wrong, a repair is priced after a diagnosis. A rebuild after a hack is priced like a new site.
The first round on a site that hasn't been touched in a while is the heaviest. The clean-up from the audit comes before the routine, so that round carries more work than the ones after it.
A host move or a new feature is quoted on its own, and the monthly report says when one is coming. Support is the whole team, not one person — reach us any time, and someone picks it up.
The plan itself is one flat monthly line, and the scope you sign covers these five things.
- Weekly updates on a staging copy
- Backups kept off the host
- Uptime, login and file-change alerts
- Small changes, up to an agreed amount
- A monthly report
Next step
Start with the free WordPress check
Run your site through the free WordPress site check. It lists plugins that haven't been updated and doors such as XML-RPC that are open. Bring the result to a call, and you'll leave with either the checklist or a plan scope.
Do I need a website maintenance plan?
- If the site brings in enquiries, orders or bookings and a break would cost you some of them, a plan is worth having. A website maintenance plan is one flat monthly line, so it's simple to weigh against what the site earns.
My host does backups. Isn't that enough?
- No, a host's backup covers only one part of upkeep. Upkeep also covers updates, monitoring, and a person who notices when the site misbehaves. Before relying on the host's copy, ask where it is stored, because a copy on the same server goes down with the site.
My site is small. Is a WordPress maintenance plan still worth it?
- Size alone doesn't decide it, because small WordPress sites are broken into through the same old plugins as large ones. A small site that earns little, and that you'd be happy to rebuild, gets less from a plan.
What happens if I don't maintain my website?
- It keeps working until something around it changes. A PHP update on the server meets an old plugin, and the site shows a blank error screen. Or a known hole in an old plugin is used to add spam pages to the site.
Isn't maintenance part of my hosting?
- No, hosting and maintenance are separate jobs. Hosting is the server space the site lives on. Maintenance is the work on the site itself, from updates and backups to watching for trouble. My team offers both, and you can buy either one without the other.
Does a Next.js site need a maintenance plan too?
- Yes, it does. On Next.js, the risk is a dependency that has fallen several major versions behind, so the plan keeps dependencies current after a backup and checks the pages after each round.
Published · Updated