WordPress Care Plans: What They Cover and How to Price One Honestly

A WordPress care plan and a WordPress maintenance plan are the same product under two names, and what you are actually buying is a person who applies updates, watches for trouble, and answers when the site breaks.

The tooling in these plans costs almost nothing. Update notifications are built into WordPress, uptime monitors are free, and backups come with most decent hosting. What costs money is somebody being accountable when a plugin update takes the checkout page down on a Thursday afternoon.

Knowing that reframes the comparison. You are not shopping for features, you are shopping for response time, scope of commitment, and how much of your hosting you would be paying for twice.

Table of contents

• The five things a plan genuinely provides
• What overlaps with your hosting
• The questions that expose a padded plan
• Doing it yourself, honestly assessed
• Reducing the surface that needs caring for
• How this fits the rest of the stack
• FAQ

The five things a plan genuinely provides

Cut through the bullet lists and the substance is short.

• Updates applied and verified. Core, themes and plugins, on a schedule, with someone confirming the site still works. The confirmation is the labour.
• Off-site backups with tested restores. Stored somewhere other than the hosting account, and periodically proven by actually restoring one.
• Security monitoring, and cleanup if it fails. Malware scanning and vulnerability alerts are cheap. The commitment to clean a compromised site is not, and it is the biggest single driver of the price.
• Monitoring with a human response. The monitor is free. Somebody reacting at 11pm is the product.
• A change allowance. Hours or requests for text edits, image swaps and small fixes, which is what most clients actually use the plan for month to month.

If a proposal is priced as though it were only the tools, it is selling you tools you could run yourself for a few pounds. The person is the line item.

What overlaps with your hosting

This is where money leaks, because several standard plan items are already covered by any reasonable managed host.

1. Daily backups with one-click restore. Standard on managed WordPress hosting. Check retention and whether restores are self-service.
2. TLS certificates. Provisioned and renewed automatically. Paying separately for certificate management is paying for a solved problem.
3. Server security and firewalling. This is the host’s layer. A care plan cannot provide it and should not bill for it.
4. Staging environments. Increasingly included, and the right place to test updates.
5. Basic uptime monitoring. Often in the hosting dashboard already.

Read your hosting plan, then read the care plan proposal, and ask about every item appearing in both. A good provider will answer straightforwardly that they use your host’s backups as one layer and add their own off-site copy as another, which is a real answer. A vague one tells you something too.

The questions that expose a padded plan

Proposals converge on the same wording. Process questions do not.

• Do you test updates on staging first? Direct-to-production is cheaper for the provider and makes your live site the test environment.
• What is the documented rollback if an update breaks something? You want a procedure and a time, not reassurance that it rarely happens.
• Where are backups stored, and when did you last restore one? A backup inside the account you are protecting does not protect against losing the account.
• Is the response time business hours only? A four-hour target on a Friday evening means Monday.
• Is hack cleanup included, or billed hourly during the emergency? This is the largest difference between two plans that look identical on paper.
• Does unused change time roll over? It decides whether the middle tier is worth the step up.

Ask for the name of the person who would actually do the work. Plans sold by a large team and delivered by a rotating queue behave differently from plans where one person knows your site, and neither is wrong, but you should know which you are buying.

Doing it yourself, honestly assessed

Self-managing is entirely reasonable for a simple site, and the routine is short enough to write down.

1. Enable automatic updates for core security releases and for plugins you trust. WordPress does this natively.
2. Apply major plugin and theme updates manually, on staging first, once a month.
3. Verify a backup exists and restore one to staging quarterly. Not reading the file, actually restoring it.
4. Keep a free uptime monitor pointed at a page that touches the database, not just the homepage, so you detect a broken database rather than a working cache.
5. Audit the plugin list twice a year and delete what is unused.

That is perhaps two hours a month with the quarterly restore amortised. The question is not whether you can do it; it is whether you will do it in a busy month, and whether you want to be the one debugging a fatal error on a Saturday.

The genuine argument for a plan is not capability, it is that it happens whether or not you are busy, and someone else is on the hook.

Reducing the surface that needs caring for

Most WordPress maintenance load is self-inflicted, and the cause is nearly always plugin count.

Every plugin is an update to apply and verify, a vulnerability surface, a compatibility risk with the next core release, and a performance cost. A site with forty plugins needs a care plan because it has forty plugins. An afternoon spent deleting the fifteen nobody uses is frequently the highest-value maintenance work available.

The other lever is making recovery cheap. A bad update stops being an incident when you can restore in one click, read the error log without a support ticket, and edit a file or a database row directly.

That last part is where hosting choice actually reduces the care burden rather than shifting it. RunxBuild’s managed WordPress puts a file manager and a database browser in the dashboard, so the two things you need during a bad update, seeing the files and reading the options table, are available without an SFTP client or hunting for phpMyAdmin credentials. The ladder starts at $3 a month and the WordPress database docs cover the browser.

How this fits the rest of the stack

Before signing a care plan, lay it beside your hosting invoice and mark every item that appears on both, because the overlap is usually bigger than the proposal implies. The RunxBuild hosting calculator prices the hosting half including the WordPress ladder, storage and bandwidth, which makes it much easier to read a care plan for what it genuinely adds on top.

Useful related references:

• Squarespace vs WordPress: The Question Behind the Question
• WordPress Maintenance Services: What You Are Actually Paying For
• WP-CLI: The Commands That Make WordPress Administration Bearable
• Services on RunxBuild

FAQ

What is the difference between a WordPress care plan and a maintenance plan?

Nothing substantive. They are two names for the same service: routine updates, backups, security monitoring and a small allowance of changes, delivered monthly. Agencies tend to say maintenance and the WordPress community tends to say care plan.

Do care plans include hosting?

Some do and some do not, and it is the first thing to establish because it changes the comparison entirely. A plan bundling managed hosting is competing against your current host as well as against other plans. A maintenance-only plan sits on top of hosting you already pay for.

Can I just enable automatic updates instead?

For a simple site with few plugins, largely yes. Enable automatic security updates, apply major versions manually on staging, and keep a monitor and a tested backup. The gap a plan fills is that it still happens in a busy month, and someone answers when an update breaks something.

How many plugins is too many?

There is no fixed number, but every plugin is an update, a vulnerability surface and a compatibility risk, so the honest test is whether each one earns its place. Sites needing the most expensive care plans are usually the ones carrying plugins nobody has used in two years.

What happens if my site gets hacked?

It depends entirely on your plan, and this is the question most worth asking before signing. Some plans include full cleanup and restoration; others offer it at an hourly rate during the emergency, which is when you have the least leverage. Get the answer in writing.