The honest answer is that website maintenance does not have one useful market price. Two sites with the same number of pages can have completely different support needs: one is a stable brochure site; the other handles payments, customer data, custom integrations and weekly campaigns.
Instead of beginning with a monthly figure, compare what the fee is responsible for.
The six factors that change maintenance cost
1. Platform and technical complexity
A conventional CMS site, a customised WordPress installation, a Composer-managed Drupal project, a Laravel application and a headless CMS stack do not require the same expertise or workflow. Custom code, abandoned extensions and unusual integrations add investigation and testing.
2. Current condition
A healthy, documented website is cheaper to take responsibility for than one with overdue updates, missing backups, unsupported software and unclear access. A provider may separate one-off stabilisation from the recurring plan. That is often more transparent than hiding unknown remedial work inside a low monthly fee.
3. Business criticality
If the website generates enquiries, takes payment, serves logged-in users or supports operations, downtime and broken journeys have a larger consequence. The maintenance plan may need more frequent checks, more deliberate testing and clearer incident handling.
4. Volume of change
Some organisations need only routine upkeep. Others need page edits, graphics, landing pages, integrations and continuous improvements. Compare whether the plan includes a support allocation, how unused time is handled and what becomes a separate quote.
5. Response expectations
“Support included” is incomplete. Ask when requests are acknowledged, how priorities are defined, what counts as an emergency and whether after-hours work is available. Faster or guaranteed coverage normally requires more capacity to be reserved.
6. Depth of assurance
There is a difference between installing updates and maintaining with backup checks, staging, compatibility review, post-release testing and reporting. The plan should say what evidence you receive and which journeys are tested.
What a useful quotation should show
Look for these components:
- routine software and dependency maintenance;
- backup and restore responsibilities;
- health, uptime and security checks;
- form and critical-journey testing;
- content, design or development allowance;
- response and escalation expectations;
- reporting or recommendations;
- exclusions and separately scoped work;
- onboarding or stabilisation fees;
- hosting, licences and third-party charges.
If these are missing, two monthly prices are not truly comparable.
Common pricing structures
Essential care retainer
This covers a defined maintenance rhythm and monitoring baseline. It suits a stable website that changes infrequently but still needs clear ownership.
Care plus support allocation
The recurring fee includes both maintenance and an agreed amount of content, design or development assistance. It suits active marketing teams that regularly need help.
Dedicated improvement partnership
The provider maintains the site and reserves capacity for a roadmap of performance, user-experience or conversion work. It suits organisations treating the website as an active business channel.
One-off support
Ad hoc work can be appropriate for a specific issue, but it does not create ongoing ownership. Repeated emergency jobs can become expensive because every incident begins with rediscovery.
Questions that reveal value—not just price
Ask each provider:
- What do you inspect before taking responsibility?
- What happens before and after an update?
- Who owns backups and when was recovery last tested?
- Are content and development requests included?
- How are urgent and routine requests distinguished?
- What is excluded?
- What happens if the website is already compromised or unsupported?
- Who in the team will know our website six months from now?
Start with the current website
The most useful first step is a review of the public site and the context you share. A deeper quotation may then require secure access to identify versions, dependencies, hosting and custom work. The cost should follow the evidence and the responsibility you want the provider to carry.