Service

Maintenance that prevents the emergency, not just responds to it

A website is infrastructure. It needs patching, backing up, watching and occasionally improving. Care plans cover the routine work that stops small problems becoming the ones that take a site offline on a Friday.

  • Tested updates applied on staging, not straight to production
  • Monitored backups with restores verified, not assumed
  • Uptime, error and security monitoring with real alerting
  • A monthly allocation of development time you actually use
Server infrastructure indicator lights representing continuous monitoring

What does website maintenance actually include?

Four things. Keeping the software current, so known vulnerabilities are patched. Keeping backups that have actually been restored at least once, so recovery is a fact rather than a hope. Watching the site, so you learn about a failure from an alert rather than from a customer. And a defined amount of development time each month, so small improvements happen instead of accumulating into the next redesign.

  • Updates tested on staging before they reach the live site
  • Backups verified by performing a real restore
  • Monitoring that alerts a person, not just a dashboard

Care plans

Four levels of cover

Scope differs by what the site does and what it costs you when it stops. Pricing is quoted per site after we have seen it, because a five-page brochure site and a store with two thousand products are not the same commitment.

  • Essential

    For brochure and lead-generation sites where downtime is inconvenient rather than costly.

    • Tested updates
    • Monitored backups
    • Uptime checks
    • Monthly report
  • Growth

    For sites that generate a meaningful share of enquiries and are actively developed.

    • Everything in Essential
    • Priority support
    • Performance monitoring
    • Monthly improvement time
  • Commerce

    For stores, where a failed checkout is lost revenue rather than a delayed enquiry.

    • Everything in Growth
    • Transaction monitoring
    • Store and checkout testing
    • Higher support allocation
  • Custom

    For applications and portals with defined availability requirements.

    • Agreed service levels
    • Release management
    • Logging and alerting
    • Reserved engineering capacity

Included

What the routine work covers

Updates

  • WordPress core, plugin and theme updates
  • Applied on staging and checked before deployment
  • PHP version compatibility monitored
  • A record of what changed and when

Backups

  • Automated scheduled backups
  • Off-site retention separate from the host
  • Periodic restore testing
  • Pre-change backups before any significant work

Monitoring

  • Uptime checks with alerting
  • PHP error and exception logging
  • Form delivery verification
  • Certificate and domain expiry warnings

Security

  • Vulnerability checks against installed components
  • User account and permission review
  • File integrity and unexpected-change checks
  • Hardening recommendations as conditions change

Performance

  • Core Web Vitals tracked over time
  • Page weight and script review
  • Caching configuration maintained
  • Database housekeeping

Improvement

  • A defined monthly development allocation
  • Content and template changes
  • Small feature work
  • A monthly report of what was done and what we recommend

The honest part

What a care plan cannot promise

No maintenance arrangement makes a website immune. A zero-day in a component you depend on, a host outage, a compromised credential on your side — these happen to well-maintained sites too. Anyone promising absolute security is selling you something they cannot deliver.

What a care plan does is shorten the list of things that can go wrong, and make recovery quick and boring when something does. Patched software removes the known vulnerabilities. Tested backups turn a disaster into an hour of work. Monitoring means you find out early. That is the actual value, and it is worth paying for.

  • Known vulnerabilities patched before they are exploited
  • Recovery time measured in hours, because the restore has been rehearsed
  • Failures detected by monitoring rather than by customers
  • A named person responsible when something does go wrong
A support technician reviewing a monitoring dashboard while on a call

Questions

Maintenance questions

Do you maintain sites you did not build?
Yes, after an initial audit. We need to know what we are taking responsibility for, so the first step is an assessment of the code, plugins, hosting and backup situation. Occasionally that audit finds a site we cannot responsibly commit to maintaining without remedial work first, and we will explain exactly what and why.
What does a care plan cost?
It is quoted per site after we have seen it. The cost drivers are what the site does, how much traffic and transaction volume it carries, how many dependencies it has, and how much development time you want included each month. We would rather quote accurately than publish a figure that turns out not to apply to you.
Does unused development time roll over?
The terms are agreed in your plan and stated in writing, including whether time rolls over and for how long. What we will not do is quietly let allocated time expire unmentioned — the monthly report shows what was used.
Can we cancel?
Yes, with the notice period in the agreement. On cancellation you get your backups, your credentials and documentation of the current state. We do not hold sites hostage, and we do not make leaving deliberately awkward.
Is hosting included?
No, hosting is separate and stays in your name. We will advise on a host suited to the site, and we can work with almost any reasonable provider. Keeping hosting in your own account means you retain control of the infrastructure regardless of who maintains the site.

Want the routine work off your desk?

Tell us what the site runs on, who currently maintains it and what has gone wrong before. We will scope a care plan that fits.