Websites rarely fail on launch day. They fail eighteen months later, when an update breaks the contact form and nobody notices for a fortnight — because nobody was watching, and enquiries dropping is a quiet symptom.
Hosting keeps the server on. Maintenance is the part where somebody notices that the thing running on it stopped doing its job three weeks ago.
Platform, plugin, and dependency updates applied on a schedule and tested on staging first, rather than accepted blindly or deferred forever.
Monitoring on the pages that matter and the paths that earn money, so a broken checkout or contact form raises an alert rather than a mystery.
Backups verified by actually restoring them, with a recovery time you've been told. An untested backup is a hope.
Core Web Vitals tracked over time, because sites get slower gradually as content and scripts accumulate and nobody notices the trend.
The small edits that otherwise queue for months — a new page, a price change, a staff update — handled without a project being raised.
A monthly note covering what was patched, what broke, what was fixed, and what needs a decision. Short, and written for a non-technical reader.
The expensive part isn't any individual failure. It's the weeks between something breaking and somebody noticing, which is where the lost enquiries live.
If the site is beyond maintaining, see website redesign. For apps rather than sites, that's app maintenance.
Send us the URL and tell us who maintains it today, if anyone. We'll audit what state it's in, what's out of date, and quote for taking it on.