WordPress maintenance plans compared: what each tier actually covers

What all WordPress maintenance plans should include

Whatever the tier and whatever the price, a maintenance plan worth paying for covers five things. If one of them is missing, you are buying a tool, not a service.

• Updates with a safety net. WordPress core, the theme and plugins are updated regularly, with a backup taken before the changes and a check of the site afterwards. Clicking "Update all" is not maintenance.
• Backups kept away from the server. A backup stored on the same hosting account disappears together with the site if the account is compromised or the server fails. Off-server copies, several restore points and a known way to restore them are the baseline.
• Monitoring with a person behind it. An uptime alert is automatic. Someone reading that alert, finding the cause and fixing it is the part you are paying for.
• Security basics. Monitoring for malware and suspicious changes, removing plugins nobody uses and reviewing who has administrator access.
• A record of the work. A short monthly log of what was updated, what was fixed and what needs a decision from you.

These five points do not depend on the size of the website. A small brochure site needs them as much as a store; it simply needs fewer hours on top.

Typical tier structure

Most providers sell three or four tiers. The names change, but the logic behind them is usually the same: each step adds testing, faster response and more hours for changes. Here is what each level tends to mean in practice.

• Basic. Regular updates, backups, uptime and security monitoring, a monthly report. Changes to the website are billed separately or come from a small allowance. Response times are counted in business days. This fits a company website that changes a few times a year.
• Growth. Everything in the basic tier, plus updates tested on a staging copy before they reach the live site, checks of forms and the key pages after each update, and a set number of hours each month for content changes, small features and fixes. Response is faster, often the next business day.
• Store or LMS. Built for websites where downtime costs money directly: WooCommerce shops, course platforms, membership sites. On top of the growth tier you should expect monitoring of the checkout or course purchase, a tested way to roll back an update, a larger pool of hours and response measured in hours rather than days.

When you read a tier, check which of these sit in the plan and which are billed as extra work. Response time, the number of included hours and whether updates are tested before they reach the live site are the three lines that separate one tier from the next. Everything else is detail.

Prices across providers vary widely, so I will not quote other people's figures. Compare tiers by what they include and who is responsible when something goes wrong. The monthly number only makes sense once you know that.

What is often left out

The gaps in a maintenance plan are rarely on the pricing page. They become visible the first time something goes wrong. These are the ones I see most often when I review websites that already have a plan.

• Staging. Without a test copy of the site, every update is tested on your customers. For a simple site this may be acceptable; for a store or a course platform it is not.
• Rollback. "We take backups" is different from "we can return the site to its state before the update within minutes". Ask how a failed update is reversed and how long it takes.
• Form checks. An update can stop contact forms sending email without any visible error. If nobody submits a test enquiry after the update, you find out weeks later from a client who never heard back.
• Fixing what the update broke. Some plans report a conflict and quote the fix as extra work. Make sure repairing problems caused by the provider's own updates is included.
• Real support hours. "Unlimited small tasks" often has a definition of small that only the provider knows. A stated number of hours with a clear rate above it is easier to plan around.
• Licence management. Premium plugins need active licences to receive updates. Some plans assume the licences are yours to track, others renew them on their own account. Agree who watches the renewal dates and make sure the licences stay registered to your company.
• A handover at the end. Ask what you receive when you leave: current admin access, the latest backup, a list of plugins and licences, and notes on any custom code. Without this, changing provider means starting from scratch.
• Off-server backups and restore tests. A backup that has never been restored is a hope, not a plan.

If you are not sure what your current setup covers, start with a free website review. I check updates, backups, security and forms, and tell you plainly where the gaps are.

Questions to ask any provider

Put the offers side by side and ask every provider the same questions. The answers will tell you more than the tier names.

• What happens before and after an update? Look for a backup, a review of the changelog, and a check of key pages and forms afterwards.
• Where are backups stored, how long are they kept and when did you last test a restore?
• Who reads the monitoring alerts, and how quickly do they react outside office hours?
• What is the difference between response time and fix time in your plan? A reply within two hours does not mean the problem is solved within two hours.
• How many hours are included each month, what is the rate above them and what happens to hours I do not use?
• Who owns the hosting account, the domain and the plugin licences? They should be in your company's name.
• What do I get if I end the contract: access, backups, documentation?
• Will I talk to the person working on my website, or to an account manager?
• Can I see an example of a monthly report? Why it matters: a sample shows whether you will get a list of real work and decisions to make, or an automated summary of plugin version numbers.
• Which tasks are outside the plan, and how are they quoted? New pages, redesigns, migrations and fixing problems that existed before the contract started are usually separate. You should know that before the first invoice, not after.

A provider who answers these questions clearly is usually one you can work with. Vague answers to the question about rollback or restore tests are a warning sign. If you want a closer look at how responsibilities can be divided between you, your marketing partner and the person looking after the site, see what I can take care of on your website.

How Esumo plans work

I use a simple model: a monthly minimum that covers the ongoing care, plus hours billed as used above what the plan includes. You always know the base cost, and larger tasks do not disappear into a vague flat fee.

Care costs €190 a month (minimum). It covers weekly updates, backups kept off the server, uptime and security monitoring, response within 2 business days and a monthly work log. Hours for changes are billed as used at €49/h. It suits a company website with occasional changes.

Growth costs €390 a month and includes 4 hours. Updates are tested on staging first, monitoring extends to forms and key user journeys, response is within 1 business day and the report comes with recommendations. Extra hours are €45/h.

Partner costs €690 a month and includes 15 hours. It adds rollback, monitoring of the checkout or course purchase, response within 4 hours on business days and a monthly call. Extra hours are €42/h. It is built for online stores, LMS platforms and companies with several websites.

If a website comes with a backlog of updates or problems left by a previous provider, I start with Takeover and clean-up: €690 one-off, two weeks of work. All plans are on a monthly contract with one month's notice, prices exclude VAT, and you keep your own hosting and domain. The full comparison is on the WordPress care page.