You already pay for hosting. WordPress can install updates automatically. So why would you pay somebody every month to maintain the website?
Because hosting and maintenance are different jobs. Hosting keeps the website online. A care plan covers responsibility for the WordPress site itself: updates, backups, monitoring, checks, support and what happens when something stops behaving as expected. In the UK, that can range from a low-cost automated service to several hundred pounds a month for hands-on developer support.
What does website maintenance cost?
There is no single UK rate because “maintenance” can mean very different things. A basic plan may automate backups, updates, scanning and uptime alerts. A hands-on plan can include developer time, form checks, troubleshooting, performance work, content changes and direct support.
My current WordPress care plans start at £180 per month, with higher tiers for businesses that need more hands-on support and development time. They are designed for businesses that want direct practical support rather than a report generated by a monitoring system.
Hosting is not the same as looking after WordPress
A hosting company is responsible for the server environment. Some hosts also provide backups, security tools and managed updates, which is useful. They are not normally responsible for checking whether your enquiry form still sends, whether a plugin update has changed a layout or whether a custom feature still behaves the way the business needs.
This is why a site can be technically “up” while something commercially important is broken.
What are you actually paying somebody to do?
A useful care plan normally covers the things that need ownership rather than simply automation. That can include WordPress core, theme and plugin updates, usable backups, uptime awareness, security monitoring, performance checks, form checks and a clear route for support.
On a healthy site, much of that work is preventative. You may not see dramatic activity every month. You should still know who is responsible for checking the site and what happens when an issue is found.
Why plan prices vary so much
Site complexity: a five-page brochure site is easier to maintain than ecommerce, membership, booking or custom-integrated WordPress.
Developer time: some plans include no hands-on changes at all. Others include a set amount of development or content support each month.
Response expectations: routine support during working hours costs less than a service expected to respond quickly to business-critical issues.
Hosting and licences: these may be included or billed separately. Always check.
Existing condition: an inherited site with outdated plugins, unexplained custom code or existing faults may need a paid review before anyone can sensibly take responsibility for it.
Automatic updates are useful, but somebody still needs to own the outcome
Automation is valuable. I use it where it makes sense. The problem comes when “everything updates automatically” is treated as the entire maintenance strategy.
A security update may need to be installed quickly. A major plugin release may deserve testing first. A routine update may expose an older conflict. A backup may exist but still need somebody who knows how to restore it.
The question is simple: when something changes, who checks the result and who decides what happens next?
Forms deserve more attention than they usually get
A contact form can fail quietly. The page still loads, the button still works and nobody notices that enquiries are no longer arriving.
For a lead-generation website, form checking is a good example of the difference between server monitoring and website care. The host can tell you the site is online. The business needs somebody to know whether the customer journey still works.
What is usually outside a care plan?
Ongoing care should not be confused with unlimited development. A small text change or image swap is very different from designing a new landing page, building an integration or changing the enquiry journey.
A good plan makes that boundary clear. Routine support is covered. Larger work is identified, scoped and agreed separately rather than disappearing into an unlimited promise nobody can realistically deliver.
Questions to ask before you compare care plans
Ask who actually does the work, what is automated, what is manually checked, whether hosting is included, how backups are handled, what happens after an update, whether forms are checked and how additional development is priced.
It is also worth understanding the difference between WordPress hosting and a WordPress care plan before comparing two monthly prices that may cover completely different responsibilities.
Choose the level of support that matches the website
A simple brochure site may only need basic maintenance. A website that generates enquiries, takes orders or supports customers deserves more active oversight because there is more at stake when something fails.
If you are not sure what level of support your WordPress site actually needs, book a call. I can look at the build, how important the site is to the business and the sort of changes you expect, then tell you which level of care makes sense rather than automatically pushing you to the biggest plan.