Most disagreements over website maintenance are not about the price. They are about something the contract never said — how fast is “fast”, whether that request counted as included, who was supposed to be holding the backups — so neither side is wrong and the argument has nowhere to go.
A website maintenance contract does not need to be long. It needs to answer a specific set of questions before either party has a reason to care about the answers.
Scope: what is included, listed as tasks
“Maintenance of the website” is not a scope. Tasks are. Plugin and core updates, backups and where they are stored, uptime monitoring, security scanning, an agreed number of content changes each month, and whatever else is genuinely being done.
Just as usefully, list what is not included: new features, redesigns, content writing, SEO campaigns, work on a second site. Not because anyone is being difficult, but because those are the four things clients most often assume are covered.
If you are reading this because you are already thinking of moving, how to change website maintenance provider covers what to secure before you give notice.
Response time and resolution time are different
This is the clause people misread most often. “Four-hour response” means somebody replies to you within four hours. It does not mean the site is working within four hours, and no honest provider can promise that for a problem nobody has seen yet.
What a contract can sensibly commit to is a response window, a stated set of working hours, and a definition of what counts as urgent. If a site being down at 11pm on a Sunday must be dealt with at 11pm on a Sunday, that has to be written down and it will cost more than office-hours cover. If it can wait until Monday, say so — it is cheaper and everybody sleeps.
Hours, allowances, and what happens when they run out
Most plans include some amount of hands-on time: a number of hours, or a number of change requests. Both work. What matters is what happens at the ceiling.
Does unused time roll over? Is extra work billed at a stated hourly rate, or quoted each time? Is there a point at which the provider will tell you the plan no longer fits rather than quietly absorbing it? A retainer that runs out silently in month three is the most common way these arrangements sour.
Backups: where they live and who has tested them
A backup nobody has restored is a hope, not a backup. The contract should say how often backups are taken, how long they are kept, where they are stored, and whether a restore has ever been tested.
Storage location matters more than it sounds. Backups kept only on the same server as the site protect you from a bad plugin update and from an accidental deletion, and not from much else. If the hosting account is suspended or compromised, they go with it.
Who owns the accounts
The hosting, the domain, the DNS, the SSL certificate, the WordPress administrator account: these should be registered in your name, on your email address, whoever administers them day to day. Your provider gets access. Your provider does not become the owner.
This costs nothing to agree at the start and is the single hardest thing to fix later, particularly if the relationship ends badly. Ask for it in the contract even when you trust the person completely — especially then, because the awkward version of this conversation happens when the person you trusted is no longer reachable.
Notice period, and what you get on the way out
Almost nobody asks about the exit clause, and it is one of the more revealing parts of any agreement. Thirty days either way is common and not unreasonable, though shorter is better for you — ours is seven days, with no cancellation fee. Twelve-month lock-ins with no break clause are worth questioning.
More important is what you receive when it ends: a current full backup, all account credentials, and any custom code written for you. If you are on the receiving end of that handover right now, our guide to taking over a website from another developer covers what to check before you change anything. If a contract is silent on this, ask for a line about it. A provider who is comfortable putting it in writing is telling you something useful about how they work.
Annual contracts versus monthly
Annual maintenance contracts — often written as a website AMC contract in India — are usually the same work billed twelve months ahead, sometimes at a discount for the commitment. Annual maintenance charges for a website in India are normally just the monthly figure multiplied by twelve, occasionally with something taken off for paying up front; if the annual number is far lower than that, check what has been removed from the scope. It can be a fair trade if the provider is known to you.
If they are not, a month-to-month arrangement is worth more than the discount. The first three months tell you almost everything about how somebody actually works, and they are exactly the months an annual contract signs away. Our own entry price is ₹1,499 a month for one basic WordPress site, with the Basic Care tier at ₹2,999; both are billed month to month for exactly this reason.
One thing an annual contract genuinely does help with is budgeting, and if that matters to you it is a reasonable reason to sign one. Just read the exit clause first.
About contract templates
People search for a website maintenance contract format or sample, and the honest answer is that a downloaded template is a starting point and not much more. The clauses above are the ones that decide whether it protects you; the wording around them is comparatively unimportant, and a template drafted for a different country or a different kind of work can quietly leave all of them out.
If you would rather see terms already written for this than assemble your own, our website maintenance plans set out scope, response times and notice period on the page before anybody has to sign anything, and what website maintenance costs in India covers what the market actually charges.