Document the support boundary and responsibilities
Define what maintenance covers before buying a monthly plan. Updates, backups, content edits, uptime monitoring and incident response need named owners and agreed limits. New integrations and redesigns should be estimated separately instead of being assumed to fit a support retainer.
Record the systems covered, backup destination and retention, restore responsibilities, support contact and escalation route. Agree how content requests are prioritised and which incidents depend on the hosting or platform provider. A backup schedule should include a defined way to check recovery.






