A client launches a website and is delighted. Nobody mentions maintenance because the project is finished and everybody has moved on.
Fourteen months later the contact form has stopped sending, two plugins are incompatible with the current platform version, the opening hours are wrong and the site has an outdated security issue.
None of it was noticed because nobody was looking. The site still exists and it has quietly stopped doing its job.
1. Explain that a website is not a finished object
It runs on software that updates, connects to services that change, and describes a business that does not stay still. Clients think of it as delivered rather than running.
2. Explain the security position plainly
Known vulnerabilities in outdated components are how sites are compromised. This is not a theoretical risk and it is the strongest argument for maintenance.
3. Explain what updates actually involve
Platform, plugins and themes, applied carefully rather than automatically, with a backup first and a check afterwards. This is skilled work rather than pressing a button.
4. Explain the backup requirement
Automated, off site and tested. A backup nobody has ever restored is an assumption, which is the same failure as anywhere else.
5. Explain the monitoring
Uptime, forms actually sending, and anything breaking silently. A contact form that stops working is invisible until somebody complains they never heard back.
6. Test the forms regularly
The single most common silent failure on a business website, and the one that costs the most, because enquiries simply disappear.
7. Explain what the plan includes and excludes
Updates and small changes included, new pages and functionality quoted. A plan with an undefined change allowance becomes an unpriced retainer.
8. Explain who is responsible for content
Prices, staff, services and hours. This is the client's to keep current, and a plan that does not say so leaves a site slowly describing a former business.
9. Explain the hosting relationship
Whether hosting is included, who holds the account and what happens if the arrangement ends, which is the ground in hosting and maintenance questions after launch.
10. Explain the performance drift
Sites slow down as content, plugins and images accumulate. A periodic review catches it before visitors do.
11. Explain what happens without a plan
Reactive work at an hourly rate, usually urgent and usually more expensive than the plan would have been. Clients should choose knowingly.
12. Price it so that it is actually delivered
An underpriced plan is a plan that gets done last, which produces exactly the outcome it was meant to prevent.
13. Report what was done
A short monthly note. A client who never hears anything concludes nothing is happening and cancels, which is the commonest way a good arrangement ends.
14. Answer the maintenance question before the project ends
An assistant that explains what maintenance covers, why updates matter, what the client remains responsible for and what happens without a plan makes the conversation part of the project rather than an awkward email afterwards. The change process sits in revision rounds and change request questions, the same aftercare pattern in maintenance and treatment questions after installation, and the wider case in do you need a chatbot seven signs your website. See pricing, run the numbers on the chatbot ROI calculator, and the sector view sits under web designers.