Written by IILL Editorial. Confirm pricing and contract scope against the actual engagement.
Short answer: choose a monthly retainer when work recurs every month or when an enquiry path must have a standing owner. Choose per-change quotes when the site is stable and someone internal already controls the content, hosting, and domain. The difference is not page count; it is the reserved capacity and operating responsibility included in the quote.
Website maintenance cannot be priced from page count alone. A scheduled monthly copy update is not the same service as incident response with responsibility for deployment, forms, search, and analytics. Before comparing quotes, align the change volume, technical ownership, response target, and completion evidence.
This guide deliberately avoids a market-average monthly price. A useful price example needs anonymised support logs showing request frequency and handling time, not a number copied from unrelated packages.
Split maintenance into four kinds of work
| Responsibility | Recurring work | What the quote should define |
|---|---|---|
| Content operations | Copy, images, people, prices, and articles | Monthly volume, change size, source approval |
| Technical operations | Dependencies, security, domains, hosting, backups | Update cadence, access, recovery boundary |
| Incident response | Site errors, lost form mail, certificate or DNS failures | Intake channel, response target, exclusions |
| Search and analytics | Indexing, 404s, Core Web Vitals, GA4 outcomes | Reporting cadence, fixes, baseline metrics |
Putting all four under one line called “website management” creates mismatched expectations. Mark each responsibility as included, excluded, or separately quoted.
When a monthly retainer fits
A retainer reserves recurring capacity and operating responsibility. It is a good fit when several of these are true:
- team members, services, schedules, or articles change every month;
- requests come from several stakeholders and need triage;
- forms or bookings are tied directly to enquiries or revenue;
- one owner must watch the domain, deployment, analytics, and search together;
- an established incident contact matters more than finding a supplier later.
A retainer is not unlimited work. Define its monthly capacity, request units, priority order, response target, restoration target, unused-capacity rule, and named exclusions. Also set the threshold that turns a request into a separate project, such as a new template, integration, or data model.
When per-change work fits
Per-change quotes are simpler for a stable site with infrequent updates:
- content changes only once or twice a year;
- an internal owner handles routine CMS edits;
- a technical team already owns hosting and domains;
- requests can be grouped into one review and release.
There is still a cost to learning an unfamiliar system during an incident. Even without a retainer, record who owns the repository, hosting, domain, analytics, and recovery contacts.
Five questions that change the price
What actually changes in a month?
A sentence, an image, a new page, and a booking-flow change are not equivalent requests. List the previous three months of work and separate recurring, urgent, and project-sized changes.
Who writes and approves the source material?
Writing and fact checking take a different scope from entering approved copy. Professional services also need an internal owner for qualifications, prices, policies, and regulated claims.
What must happen within the response target?
“Response within 24 hours” is not a restoration promise. Write two clocks:
- Response: a named person acknowledges the request, classifies it, and states the next step.
- Restoration: the site, form, certificate, or DNS record works again. This may depend on a registrar, host, or credential outside the maintainer’s control, so state both the target and the conditions that pause it.
Put hours of cover, third-party delays, and project-sized requests in the same exclusion list. Treating every copy edit as an incident makes the real incident queue less reliable.
Who owns third-party services, dependencies, and AI usage?
Domains, mail, hosting, form delivery, booking, payment, maps, and plugins have different accounts and billing cycles. Separate subscription costs from labour and define how ownership transfers at the end.
For an AI-assisted build, name two more owners. One owns the dependencies introduced by generated code: security notices, compatibility updates, and replacement of abandoned packages. The other owns any metered AI or automation service used in production: billing account, spending limit, failure behaviour when a limit is reached, and whether usage is included in the retainer. Unowned usage becomes either an outage or an unexpected invoice.
What proves the change is complete?
A green deployment is not enough. Verify the live URL, mobile layout, form delivery, search directives, and GA4 event, then retain a change record. Connect the scope to observable checks from Google Search monitoring, the WCAG 2.2 quick reference, and Core Web Vitals where they apply.
Minimum items for a maintenance quote
- Included change types and monthly capacity
- Normal and urgent intake channels and response targets
- Work that becomes a separate project
- Pre-release checks and live verification
- Backup schedule and recovery testing
- Domain, hosting, and paid-service ownership
- Form, GA4, and Search Console review cadence
- Metrics and changes included in the report
- Repository, account, and documentation handover
Next action: list every request from the last three months and label it content, technical, incident, or search and analytics work. That single table is the input a supplier needs to compare a retainer with per-change work.
Confirm ownership at the start and end of the agreement with the website handover checklist and test the recovery promise with the restore test. If you are comparing maintenance with a rebuild, use the website production cost guide or describe the current scope to IILL.
Need a clearer first step for your website?
Start with the situation and outcome. We will help define the scope and next step.