Website maintenance is one of the least examined line items in a marketing budget. It is sold as a monthly figure with a short list of bullet points, and most buyers have no way to judge whether they are getting value until something breaks. By then the conversation is about blame rather than about scope.
This is what the work actually contains, what separates a real plan from an invoice for doing very little, and how to buy it without overpaying.
A website is an operating asset, not a delivery
The idea that a website is finished at launch is the root of most maintenance disputes. A live site sits on hosting that changes, runs software that gets patched, depends on integrations that update on someone else's schedule, and is exposed to the public internet continuously.
Left alone for two years, a site does not stay still. It drifts: plugins fall out of date, security patches go unapplied, performance degrades as content accumulates, and forms quietly stop delivering because an email setting changed. None of that announces itself.
What real maintenance covers
Security and patching. Applying updates to the platform, plugins and dependencies, and doing it on a schedule rather than when convenient. This is the single highest value item and the easiest to skip invisibly.
Backups that have been tested. A backup nobody has ever restored is a hope, not a safeguard. Ask when the restore was last actually performed. The answer tells you a great deal about the supplier.
Uptime and error monitoring. Someone should know the site is down before your customers tell you. The same applies to server errors and broken forms, which fail silently and cost you enquiries without ever showing up as an outage.
Performance. Page weight grows as content is added. Periodic attention keeps load times from sliding, which matters for both conversion and search visibility.
Content changes. Usually a defined allowance of hours. Be precise here, because this is where most disagreements start.
Reporting. A short record of what was done and what it prevented. Without it you are paying for invisible work and taking it on faith.
The question that exposes a weak plan
Ask a prospective supplier: what counts as a bug, and what counts as a change?
A bug is something that was supposed to work and does not. That should be fixed under maintenance without argument. A change is new behaviour you are asking for. That is chargeable work. Suppliers who cannot draw this line clearly at the point of sale will draw it in their favour later, when you are already committed.
The second useful question is about response time. Not a promise to reply, but a commitment on how quickly work starts when the site is down versus when a link is broken. Those are different urgencies and a serious plan treats them differently.
What it should cost
Pricing scales with the surface being maintained. A small brochure site with a handful of pages and no integrations carries very little ongoing risk. A store processing live transactions, or a site wired into a CRM and an inventory system, carries a great deal more, and the plan should reflect that rather than being priced from a menu.
Be sceptical of two extremes. A very cheap plan usually means monitoring software and nothing else, with a human involved only when you complain. A very expensive plan should come with a named person, a response commitment and a report you can actually read.
For context on how build budgets and ongoing costs relate, we set out the wider picture in our breakdown of website development cost in Dubai.
The access question nobody asks early enough
Before you sign anything, establish who holds what. Your domain registrar, your hosting account, your DNS, your analytics and your source code should all be in accounts your company owns, with your supplier holding access rather than ownership.
This sounds procedural until you want to change supplier. A maintenance relationship you cannot leave without losing your own website is not a service arrangement, it is a dependency. Ask the question while everyone is still friendly, and get the answer in writing.
Frequently asked questions
Do I need maintenance if my site is simple?
If it is live and takes enquiries, yes, though the plan should be proportionate. At minimum you need patching, tested backups and someone who notices when the site or its forms stop working.
Can I do it myself?
You can, if someone in the business genuinely owns it and has time. The usual failure is not capability, it is that maintenance is nobody's actual job, so it happens until it quietly stops.
What happens if I skip it for a year?
Often nothing visible, which is exactly why it gets skipped. The cost arrives all at once: a compromised site, an outage during a campaign, or an accumulated upgrade that is now a project rather than an update.
How to buy it well
Ask for the scope in writing, with the bug and change boundary defined. Ask what the reporting looks like and request a sample. Confirm that every account is in your name. Then judge the plan on whether it prevents problems rather than on how many bullet points it lists.
We maintain the sites we build and a number we did not, as part of website development. If you are unsure whether your current arrangement is doing anything, send us the details and we will tell you plainly what is and is not being covered.
