A supplier website changes as products, documents and staff responsibilities change. Maintenance should account for that everyday editing work as well as software updates.
Write down the recurring work
We can agree a support scope covering a defined website, reviewed updates and a manageable issue process. Product accuracy remains with the business. Hosting, domain and provider accounts need named owners, and renewal notices should reach someone who can act on them.
The handover can include common editing tasks, document replacement, a record of dependencies and instructions for reporting a fault. Response arrangements, included work and exclusions are agreed in writing. A maintenance discussion is not a promise of uninterrupted service or a substitute for the host's own recovery arrangements.
Practise the routine task
Ask the appointed editor to update a fictional product and replace a test document using the instructions. Review what happens when that editor leaves the business. A useful handover makes the next change understandable without relying on the original developer's memory.