Website maintenance pays for a mixture of infrastructure, preventative work and access to help. A meaningful UK maintenance quote separates those services: domain renewal and hosting keep the site reachable; updates and recovery arrangements keep it maintainable; support and content changes buy someone’s time. A low monthly fee may cover only the first part.
There is no useful single price without knowing the platform, functions and response commitment. This guide gives you a quote checklist and a worked annual budget so you can compare what is included. A static business website and a WordPress site with payments and daily publishing should not inherit the same plan by default.
Start by separating the bills
Your domain is the renewable registration for the address. Hosting serves the website. Email may be supplied separately, even when all three appear on one invoice. Record the provider, account holder, renewal date and normal renewal price for each. An introductory offer says little about next year’s bill.
Ask whether hosting includes backups, certificate renewal, monitoring and assistance restoring the site. Storage space alone is not a recovery service. Equally, do not pay a care supplier for a second copy of a service already included unless the additional protection has a clear purpose.
A maintenance agreement should also distinguish faults in delivered work from changes requested later. A post-launch support period is not automatically an ongoing care plan. Keep the original project agreement available when discussing a renewal.
Use this maintenance quote checklist
“Essential” means the responsibility needs an owner, not that it must be bought as a monthly add-on. “Scope-dependent” means the need changes with the actual site. Optional work should have a reason to exist.
On smaller screens, scroll across to read all columns.
| Item | Priority | What to ask |
|---|---|---|
| Domain and hosting | Essential | Who controls renewal, DNS and billing? Is email separate? |
| Recoverable backups | Essential | What is backed up, how often, for how long, and when was restoration tested? |
| Account security | Essential | Who manages access, multifactor authentication and departing users? |
| Core, plugin and dependency updates | Scope-dependent | Which components exist, who updates them and what is checked afterwards? |
| Security monitoring | Scope-dependent | What is detected, who receives alerts and is incident response included? |
| Enquiry and availability checks | Essential | Does testing verify receipt, or only that a page loads? |
| Performance and accessibility reviews | Scope-dependent | Which pages and journeys are checked, how often, and are fixes included? |
| Reserved support time | Scope-dependent | What hours, channels and response targets apply? |
| Content updates | Optional allowance | How much time is included and do unused hours expire? |
| SEO campaigns or new features | Optional separate work | What deliverables are agreed beyond keeping the existing site working? |
A quote becomes comparable when each row has an owner and a boundary. “Security included” is too broad to price. Monitoring suspicious activity, investigating an alert and rebuilding a compromised site are different commitments.
Backups are only useful if somebody can restore them
A WordPress recovery may need the database, uploaded files, themes, plugins and configuration. A code repository alone will not contain all of that. For a static custom site, source files and deployment instructions may recreate the pages, but uploaded content, form submissions or an external CMS can need separate recovery arrangements.
Agree how much recently changed information the business could tolerate losing and how quickly service needs to return. A site updated quarterly has different recovery needs from a transactional system. Ask for a documented restore process and occasional evidence that it works, rather than simply a count of stored backups.
Check who holds recovery access if the supplier is unavailable. The business should know where its domain, hosting and source files are controlled, even when a trusted partner manages routine work.
WordPress and custom-coded maintenance differ
With WordPress, core software, themes and plugins form an active application. Updates, compatibility checks and licence renewals are real work. WordPress’s update instructions explain the need to back up before updating; agreeing who tests forms and restores service makes that operational for your business.
A lean custom-coded site can have fewer moving parts at runtime, particularly when it serves static pages without a public admin system. That can reduce routine application upkeep. Build dependencies, hosting accounts, certificates, forms and third-party services still require attention. Adding a CMS, customer portal or database changes the maintenance brief again.
Security also depends on access and responsibility. The official WordPress hardening guidance treats it as risk reduction across software and hosting, rather than a single plugin purchase. The same commercial question applies to either approach: which risks is the supplier managing, and what remains with you?
For a platform decision, use our WordPress versus custom-coded guide. A maintenance comparison should follow the actual architecture, not a presumption that one category is always inexpensive or secure.
What would a transparent annual budget look like?
Consider this entirely hypothetical brochure-site budget. Amounts exclude VAT and are not market averages or Smartcon Works prices:
- Domain renewal: £25 a year.
- Hosting with its agreed backup service: £144 a year.
- Technical care, excluding hosting: £600 a year.
- Separately paid theme or plugin licences: £180 a year.
- Four hours of content changes at an assumed £60 an hour: £240.
The planned annual total is £1,189, equivalent to about £99.08 a month. That monthly equivalent is a budgeting aid: annual invoices may still arrive together. Incident recovery, new functionality, email and internal staff time are excluded from this example. Confirm VAT treatment on every real quote.
Now suppose a £95 monthly plan includes the same hosting, care and licences but no changes or domain. Its comparable annual total is £1,140 + £240 + £25 = £1,405. The £216 difference may be worthwhile if it buys a useful response commitment, or unnecessary if it duplicates support you already have. The headline £95 does not answer that question.
Retainer or ad hoc support?
A retainer can reserve capacity and make recurring work predictable. It suits a business that needs regular changes or cannot accept an uncertain queue when something breaks. Establish whether it buys completed tasks, an allowance of hours or simply availability. Those are different products.
Ad hoc support can suit a stable site with a capable internal owner and infrequent requests. Ask about minimum charges, emergency availability and the cost of investigating a site the developer has not touched recently. Saving a retainer is less attractive if nobody is responsible for routine updates between requests.
Do not confuse response with resolution. “We respond within one working day” may mean an acknowledgement, not a repaired form. Agree how urgent faults are classified, what happens outside working hours and who authorises additional work. Read our website agreement questions alongside the maintenance proposal.
Before signing, ask for a handover you could use
Request an account register, named responsibilities, renewal schedule, support contact and cancellation process. Confirm access to the source repository or export, deployment instructions and relevant licences. Keep business-controlled recovery details current and use individual access rather than a shared password circulated by email.
Then run one practical scenario with the supplier: an important enquiry form stops delivering messages on a Friday afternoon. Who notices, who investigates, what can be restored and what is billable? The answer is more informative than a long list of maintenance features.
If maintenance has become expensive because the site is difficult to change, our WordPress redesign cost framework can help compare repair with replacement. Continuing costs should inform that decision; they should not automatically trigger a rebuild.