01
Updates happen only when something breaks
A defined review rhythm turns maintenance into prevention, with priorities and responsibilities understood before an urgent issue appears.
Remote support, wherever you are based. Care plans are optional, documented and never a condition of working together.
A useful website care plan does more than install updates. It protects important forms and journeys, keeps content accurate, catches deterioration and creates a practical path for ongoing improvements.
Diagram: monthly checks for updates, backups, performance and content; monitoring of uptime, errors and forms; and a handover with accounts in your name and documentation included.
01
A defined review rhythm turns maintenance into prevention, with priorities and responsibilities understood before an urgent issue appears.
02
Critical journeys need deliberate checks. A green hosting dashboard does not prove that enquiries, payments or integrations are completing.
03
A care plan can reserve space for sensible content, UX and performance work instead of consuming every hour with reactive support.
The proposal confirms the exact inclusions. This list shows the areas that can form a complete engagement, not a promise that every project needs all of them.
A clear agreement says which of these are included, how requests are prioritised and what requires a separate scope. That protects both the business and the quality of the site.
01
Routine platform, dependency and technical housekeeping intended to reduce avoidable risk.
02
Investigation and response when a site feature, integration or publishing workflow is not behaving as expected.
03
Publishing or updating supplied text, images and structured content within the existing system.
04
Planned UX, performance, accessibility or feature work that changes how the site operates.
Confirm ownership, hosting, platform, access, current issues and the parts of the site that matter most.
Resolve urgent risks and establish an appropriate update, backup and checking approach for the stack.
Agree how requests arrive, what is included, response expectations and how work is reported.
Use what is learned from real operation to prioritise small changes or identify when a redesign is the honest answer.
Sometimes. The first step is a paid or scoped review of the platform, code quality, hosting, access and current risks. Support is offered only when the site can be responsibly maintained.
Managed hosting may be included where appropriate, but it is not required. The business can retain its own hosting account and grant the access needed for support.
Availability and response expectations depend on the care agreement. The website does not promise 24/7 or instant response; any urgent-support arrangement must be set out explicitly in writing.
Yes. Care should not be a form of lock-in. Account ownership, access, notice and handover details are set out in the specific agreement, with business assets kept under client control wherever practical.
Share the site, platform and the issues you already know about. We will first work out whether ongoing care is a responsible fit.