Website Maintenance: What It Covers and What It Costs

The call usually comes months after launch, and it almost always starts the same way: "someone quoted me 15,000 a month for maintenance, is that normal?"

It is impossible to answer without knowing what is inside that 15,000. Maintenance is one of those words, like marketing, that sounds specific and means nothing until someone lists the tasks.

So here is the list. This is what I actually do on a maintenance retainer, and what it should cost.

What maintenance actually is

Maintenance is not one job. It is three unrelated jobs bundled under one invoice.

1. Keeping the thing running. Dependency updates, security patches, server or hosting configuration, monitoring, backups. Nothing here adds features. All of it prevents a bad day. A site running on software from two years ago is not a site with old features, it is a site with known published vulnerabilities.

2. Keeping the data safe. Off-site backups you have actually tested restoring, uptime alerts that reach a human, and a documented recovery path. Most sites I audit have backups that have never been restored once. An untested backup is a hope, not a backup.

3. Changing things. New pages, updated prices, new team members, a new form field, a campaign landing page. This is the part clients notice, because it is the part they ask for by email.

A serious quote breaks those three apart. If your quote is one number with no breakdown, you are not being told what you bought.

What maintenance is not

Maintenance does not include a redesign, new features, new integrations, or marketing. Those are projects, and they get scoped and quoted separately.

This matters because the most common maintenance dispute I hear about is a client asking for a new pricing page with a comparison table and being told it is outside the retainer. That was never a maintenance task. Someone should have said so at the start.

What it actually costs

Real numbers, from how I price and from what I see quoted in Chennai and internationally:

• Small marketing site, low change volume: 5,000 to 12,000 per month in India, or 50 to 150 USD internationally. Covers updates, backups, monitoring and a couple of hours of changes.
• Site with a blog, lead forms and integrations: 12,000 to 30,000 per month, or 150 to 400 USD. More moving parts, more to watch, more change requests.
• Web app with logins, payments or customer data: 25,000 to 75,000 per month, or 400 to 1,200 USD. Security updates, database backups, and error monitoring are no longer optional at this size.
• Hourly, if you prefer: 1,500 to 4,000 per hour in India, 60 to 150 USD internationally, billed in blocks.

Two things to notice. The floor is not zero, because monitoring and backups cost real time every month whether or not you ask for anything. And the ceiling is driven by consequence, not by size: a five-page site holding customer payment details needs more care than a fifty-page brochure.

The cost of skipping it

A neglected site does not fail loudly. It degrades in three ways, in this order.

First, speed. Dependencies accumulate, images get added without compression, and the site quietly gets slower, which shows up in your enquiry numbers long before you notice it technically. I have written about how a slow site loses customers because it is the most expensive invisible problem a business can have.

Second, security. An unpatched form or an abandoned plugin is the most common way small business sites get compromised, and the recovery bill is always larger than a year of maintenance.

Third, rebuild cost. When the stack has drifted far enough, the next change is not a change, it is a migration. That is the point where a cheap initial quote costs more later, and it is the trap I see most often with sites built on plugin-heavy platforms.

How to keep the cost down

• Own your accounts. Domain, hosting, repository, analytics, email. On your accounts in your name, not a developer's. This is not a trust issue, it is a continuity issue, and it is the first thing I check on any handover.
• Keep the stack small. A site with six plugins needs six plugins patched. A site built on Next.js and Firebase with few dependencies needs almost none. Fewer moving parts, lower monthly cost, permanently.
• Separate content from code. If updating a paragraph requires a developer and a deploy, your monthly cost is inflated by design. Content should be editable without touching the build.
• Give change requests a channel and a cadence. One email thread with a running list beats a WhatsApp message every third day, both for your cost and for the person doing the work.

How I price maintenance

I keep it simple: a monthly retainer sized to the site, with a stated number of change hours inside it, and anything beyond that quoted before it starts. No surprise invoice, no work done silently and billed later.

For small sites I would rather you spend the retainer on content and visibility than on patching, because a well-built static or Next.js site genuinely needs very little monthly attention. If your site needs a lot of maintenance, that usually says something about the platform it was built on, not about websites in general.

If you have a maintenance quote and you are not sure what is inside it, send it to me on WhatsApp. I will tell you in one message whether it is fair, thin, or padded.