Web & Digital
Ongoing ownership after launch: patching, backups, uptime and performance monitoring, content changes and a named route for when something breaks.
Maintenance is a schedule with evidence u2014 patches applied, backups restore-tested, uptime measured and a report you can read.
Problems are detected by monitoring, not by a customer phoning in.
Updates are verified on staging with a backup taken before production.
A backup counts only once a restore has actually been performed.
A named route for requests, with agreed response expectations.
Updates, backups with restore testing, uptime and performance monitoring, security scanning, content changes and a monthly report. Scope is agreed in writing.
Yes, after an audit of the platform, plugins, hosting and backups, and any remediation that audit identifies.
Response expectations are set by the agreement. A site-down event is treated as an incident, not a ticket in a queue.
Yes, monthly. Access, credentials and documentation are handed back in full.
Send the environment details and get an engineered proposal with assumptions, risks and a rollback path.