PixelCodeLab
← All articles

 ·  4 min read

What £49 a month buys, against a WordPress care plan

Care plans list the same things: updates, backups, monitoring, support. What sits underneath the list is the difference, and here is ours.

Search for a WordPress care plan in the UK and you find prices from about £30 a month to a few hundred. Most of them promise the same list: updates, backups, uptime checks, security. Our Care plan is £49 a month and makes promises from the same list. The difference is in what sits underneath the list, and that is what this article is about.

What the £49 covers

The Care plan is for a site we built. Each month it covers:

  • Hosting on our own server, not on shared space resold from someone else.
  • An uptime check every five minutes.
  • A backup every night, and one more before every deploy.
  • Framework and security updates.
  • Certificate renewal, so the padlock never lapses.
  • Email support, answered by the person who built the site.
  • One change request a month.

We are not VAT registered, so £49 is the whole price, with no VAT added on top.

Updates without the Tuesday morning surprise

Most of the work on a WordPress care plan is plugins. A typical small business site runs twenty or thirty of them, each from a different author, each updating on its own schedule. A care plan updates them, and the real service is fixing whatever an update broke.

Our sites are built in Laravel on one shared codebase. A booking form, a review feed or a contact inbox is one module, written once and used by every site that needs it. When we change a module, we release one new version. That version goes first to our own site. Each client site then runs its own full test suite against it, and only a site whose tests pass gets the update. If a test fails, the release stops at that site, and the sites after it keep the version that works.

So an update is something we test before it reaches you, not something we repair after you notice.

Backups we have restored, not only taken

A backup that nobody has restored is a hope. Every night, the backups leave the server that runs the sites and go to a second machine. That machine accepts new backups but does not let the first one change or delete the old ones, so a fault on the main server cannot take the backups with it. If a night passes with no new backup, we get an alert. We restored a full site from these backups in September 2026 to prove that the process works.

Monitoring that says something

The uptime check runs every five minutes, from a machine outside the server it checks. When a site stops answering, we get an alert. You do not need to tell us. The same checks record a 30-day uptime figure for each site, and you can see your own figure when you sign in to your account.

Support from the person who built it

On a lot of care plans, support is a ticket queue. On ours, your email goes to the developer who wrote your site. Questions such as "can the form also ask for a postcode" get an answer from someone who knows where that form lives. One change request a month is included. Care Plus, at £99, raises that to three and adds a monthly report on traffic, enquiries, reviews and search health.

What it does not cover

The £49 does not cover new features, new pages or a redesign. Those are quoted on their own, and the prices for our packages are on the pricing page. Care is also only for sites we built, because we only promise to look after code we know.

If you leave

You own your site's content, its domain and its data. If you leave, you get an export of all of it. The care plan pays for the looking after. It does not lock in your site.

In short

A WordPress care plan and our Care plan list similar things. Ours is £49 a month, and the work underneath is different. Updates are tested on your site before they reach it, backups are proved by a restore, and support comes from the developer who built your site. You can see the full list on what you get and how it runs on the platform page.

If you want to see what your own site could look like before you pay anything, ask for a demo below.

Written by Luke Ellis, who builds and looks after the sites this is about.

Want this applied to your site?