Website maintenance costs: a checklist for small businesses

Website maintenance costs are easier to understand when the quote names the responsibilities. “Hosting and support” might mean keeping a server available, updating software, editing content, fixing integrations or a combination of those tasks. The label alone is not enough to compare plans.

For a small business, the practical question is who notices a problem, who fixes it and what the agreed fee covers. This guide provides a responsibility checklist and a budgeting method without presenting invented market prices.

Separate the services you are buying

Start by listing the website’s moving parts. A domain registration, hosting plan, content system, form service, booking tool and image licence may have separate owners and renewal dates. Some may be bundled into one invoice, but they are still distinct dependencies.

Responsibility	What to ask	Evidence to keep
Domain and DNS	Who controls the account and renewal?	Account owner and renewal record
Hosting	What is hosted and who handles incidents?	Plan details and escalation route
Software	Who applies and tests updates?	Maintenance scope and change log
Backups	What is backed up and how is recovery tested?	Retention schedule and restore record
Enquiries	Who checks delivery and spam handling?	End-to-end test results
Content changes	What edits are included and how are they requested?	Allowance, exclusions and response terms

Keep access information securely rather than placing passwords in a shared planning document. The maintenance register should identify where credentials are managed and who is authorised to use them.

Distinguish hosting from maintenance

Hosting makes the site available on infrastructure. It does not necessarily include checking the contact journey, replacing outdated opening hours or fixing an incompatible integration. Ask for the boundary in writing.

Likewise, an update service may install software without reviewing every customer journey afterwards. For WordPress, the official updating guide recommends backing up before an update. Your agreement should explain who performs the backup, checks the result and restores the site if necessary.

A framework-based or static website still needs care. Its content, deployment process and third-party services can change. A site with no database may have a simpler recovery process, but “nothing to maintain” is rarely a useful operational description.

Build an annual cost register

For each item, record the supplier, renewal frequency, current amount, account owner, cancellation terms and business purpose. Mark whether it is included in another fee so that it is not counted twice.

Use this formula: annual recurring commitment = twelve monthly payments + annual renewals + agreed scheduled work. Keep one-off improvements separate. This makes it easier to see whether a maintenance plan is being compared with a hosting-only subscription.

For illustration only, imagine hosting at £18 a month, a £20 annual domain renewal and an optional £60 monthly support allowance. The annual total is £956 before any tax treatment or additional work. These are invented inputs demonstrating the calculation, not typical UK prices or Business Web Development charges. Replace every figure with your actual agreements.

Ask what happens to unused support time and whether emergency work is charged separately. A lower monthly fee may be entirely appropriate if you are comfortable commissioning changes as needed; a retainer is not automatically better value.

Agree a meaningful check routine

The right frequency depends on how often the site changes and how important each function is. A brochure site and a busy booking system do not have identical risks. Start with the consequences of failure and assign a proportionate check.

A useful routine might include a test enquiry after relevant changes, a review of renewal notices, an update log and periodic content verification. Record the destination inbox and confirm receipt; seeing a thank-you message is not proof that the business received the enquiry.

Include usability checks when forms change. W3C’s forms guidance explains the importance of instructions and correction feedback. A technical update that leaves the form confusing still needs attention.

Make recovery practical

Ask a provider to explain the recovery process in ordinary language. What would be restored, from which date, by whom and with what access? Does the backup contain just the website code, or also uploaded files, content and configuration?

Agree a response target separately from a resolution promise. A provider may be able to acknowledge an incident promptly without knowing how long a third-party outage will last. The contract should make that distinction clear.

Keep a simple change log with the date, change, person responsible and verification performed. When an enquiry route stops working, knowing what changed recently can shorten the investigation.

Review the arrangement when the website changes

New booking systems, payment tools, languages or regular publishing can alter the maintenance requirement. Revisit the register when adding them, rather than allowing responsibilities to accumulate informally.

If you are commissioning a new site, include maintenance and handover in the website brief. If you are comparing suppliers now, use the website cost guide to bring one-off and ongoing commitments into the same comparison.