“Maintenance included” is too vague to budget or rely on. It may mean software updates, uptime checks, small content edits, backups, emergency response, or only access to ask for a quote. The useful question is: what exact task will the provider perform, how will you request it, and what happens if it is outside the plan?
Separate four kinds of work
First, list defect corrections: an agreed feature fails to behave as specified. Second, list routine upkeep: platform and plugin updates, backups, security checks, or broken-link review, if the provider will perform them. Third, list content changes: replacing approved copy, adding a page, updating staff details, or uploading products. Fourth, list new capabilities: integration, redesign, new template, or automation. Each category can have a different price and approval path.
Ask whether third-party failures are diagnosed, fixed, or only reported. A form vendor, payment processor, registrar, host, or plugin may have its own account and support obligations. If the provider cannot control that system, the plan should say who opens the vendor ticket and who keeps the business informed.
Define service in operational terms
Write down the support channel, named account or team, working hours, severity levels, acknowledgement target, and whether “response” means a human acknowledgement or a completed fix. The provider may offer different terms; do not infer an emergency guarantee from a general support promise. Ask for the backup location, restore test responsibility, and who can authorize a rollback.
Check whether updates happen on a staging site first, whether the plan covers compatibility testing, and how a failed update is handled. If a site has no supported update path, the proposal should say so; otherwise “maintenance” may simply postpone a later rebuild. For a static marketing site, a large plugin-update package may be irrelevant, while content and form checks may matter more.
Compare the total relationship cost
Put hosting, domain renewal, software licenses, stock assets, monitoring tools, and provider labor on separate lines. Identify who owns each account and receives renewal notices. A monthly price without a cancellation and handover clause can hide the cost of leaving. Ask what access and files you receive when the plan ends.
The agreement should also define what the initial build’s defect-correction period covers. That period is separate from an ongoing maintenance contract. A preference change after launch is not automatically a defect; an in-scope form that never delivered to the specified inbox may be.
ARCHV’s website service page says defect correction, maintenance, recurring costs, and postlaunch support should be agreed in the proposal. It does not publish a universal maintenance package or response guarantee. Use the website quote comparison if one offer says “support included” and another lists specific tasks; compare the actual obligations before comparing price.
Ask for a sample support ticket from request to closure with names removed. It should show how a problem is reported, classified, resolved, and confirmed. If the provider offers emergency coverage, test the contact path before an emergency. If the plan covers only scheduled tasks, make a separate business continuity plan for form, domain, and hosting failures.
For domain renewal and transfer responsibilities, ICANN's transfer-policy overview is a useful independent reference. The website maintenance agreement should name who receives registrar notices and who is authorized to act; a web-design support contract does not by itself change the domain registrant.