Website Maintenance Plans: What to Charge Monthly

Search for website maintenance pricing and Google will show you agency pricing pages rather than articles. That is what a thin editorial supply looks like: there is demand for the answer and almost nobody has written it, so the search engine falls back to commercial pages.

Here is the answer. What a maintenance plan should cost monthly, what belongs in it, and the mistake that makes agencies price it at a tenth of its value.

A build is revenue once. Twenty builds a year at ₹30,000 is ₹6 lakh, and every January you start from zero.

Twenty care plans at ₹3,000 a month is ₹7.2 lakh a year that arrives whether or not you sell anything — and it compounds, because year two starts at ₹7.2 lakh before the first new client.

That is the whole argument, and it is why the plan should be sold at the same moment as the build rather than offered afterwards.

Assumes ₹30,000 per build, ₹3,000/month care, and that plans persist. The gap is not the plan price — it is that the plan does not reset each year.

The jump from hosting-only to basic care is the important one: it is where you stop selling a commodity and start selling availability.

Most agencies price the plan at what hosting costs them plus a margin. That is pricing your cost, not their value, and it is why so many care plans sit at ₹500 a month doing real work.

What the client is actually buying is that somebody answers. Their menu changed, their timings changed, a photo is wrong, the site is down and they do not know who to call. The technical content of that is an hour a month; the value of it is that the site does not quietly rot.

Say it that way. "₹3,000 a month means when something needs changing, you message me and it is done. Without it you're finding a new developer every time." Every business that has been abandoned by a previous developer — which is most of them — understands that sentence immediately.

Offered afterwards it sounds like an upsell. Included in the original quote as a line item, it sounds like part of how this works.

Quote it as: build ₹30,000, then ₹3,000 a month from launch. Not "and we also offer maintenance". The plan should appear on the first piece of paper they see.

Bundle the first three months into the build price if you need to close. It costs you very little, it gets the habit started, and a client who has had three months of things being fixed rarely cancels in month four.

This is where care plans go wrong. "Small changes included" sounds generous and reads, to a client, as unlimited. Six months later you are rebuilding a page for ₹3,000 a month and quietly resenting it.

The boundary that works is time, not task type. "Up to an hour of changes a month, carried over up to three months." Nobody argues with an hour, everybody argues with whether adding a page counts as small, and the carry-over stops them feeling they lose it by not asking.

Beyond that, quote separately and cheerfully. A client who has a happy monthly relationship approves a ₹6,000 extra without much thought; the same client on an unbounded plan treats every request as a test of whether you will push back.

A client who negotiates the care plan down to ₹800 is telling you they will still expect the same responsiveness. Take the build and let the plan go rather than accepting a number that makes every request feel like an imposition.

The same applies to a site you did not build. Taking over someone else's code for ₹2,000 a month is how agencies end up maintaining things they cannot fix. Quote an audit first, separately, and decide afterwards.