Website Maintenance Cost in 2026: What You Are Actually Paying For
12 August 2026
Maintenance is the line nobody reads during the sales conversation and everybody discovers in month three. The site is delivered, the invoice is paid, and then a payment provider changes an API, a dependency ships a security patch, and someone has to do something about it. The question is not whether that work happens — it is whether you budgeted for it or are about to be surprised by it.
Four jobs sold as one word
"Maintenance" covers four activities that have almost nothing in common, and a quote that does not separate them cannot be compared with another quote.
- Corrective — fixing what broke. The one everyone pictures, and usually the smallest share.
- Preventive — dependency and security updates applied before they become incidents. Invisible when it works, which is why it is the first thing cut.
- Adaptive — keeping the application working while browsers, payment providers and third-party APIs change underneath it. Nothing about your code changed; the world did.
- Evolutive — small additions and adjustments. This is where budgets drift, because it is genuinely useful and has no natural limit.
Real annual ranges
The figures below are what this costs on the European market where I work, for a contract covering all four categories with a standard service level — four-hour response during business hours, 99% availability. They are orders of magnitude for a conversation, not a rate card.
- Brochure site, 5 to 30 pages, little ongoing development — €1,200 to €3,600 a year, so €100 to €300 a month.
- Small e-commerce with catalogue, payments and order tracking — €3,600 to €12,000 a year, €300 to €1,000 a month.
- Business web application, internal tool or customer portal — €6,000 to €18,000 a year, €500 to €1,500 a month.
- Growing B2B SaaS, multi-tenant with continuous evolution — €15,000 to €60,000 a year.
- Mature SaaS at volume, strict multi-tenancy, public API, SSO — €50,000 to €200,000 and beyond.
- Embedded AI features — add 20 to 40% to the equivalent application, plus a separate line for inference, which scales with usage rather than with the codebase.
What actually drives your number
Within any of those brackets, the spread is explained less by size than by the state of what you start from. An application with tests, current dependencies and a readable structure costs a fraction of what a rushed one of identical scope costs to keep alive — and the gap widens every year, because each deferred update makes the next one harder. This is the part of a maintenance quote that is really a verdict on the build.
Five things reliably inflate the bill: dependencies left unpatched until the upgrade becomes a migration; a stack nobody else on the market knows; no staging environment, so every change is tested in production by your customers; undocumented business rules that have to be rediscovered before they can be modified; and third-party integrations whose providers change their terms without asking you.
Deferring is financing, not saving
Skipping maintenance works for two or three years. Then the accumulated updates arrive as a single migration, usually triggered by an incident and therefore done under time pressure, at the worst possible rate. Everything saved is spent at once, with the downtime on top. If you decide to defer anyway, do it deliberately and write down when you will pay it back, rather than discovering the schedule when it is chosen for you.
Frequently asked questions
How much does website maintenance cost per month?
For a brochure site of five to thirty pages with little ongoing development, roughly €100 to €300 a month, or €1,200 to €3,600 a year. A small e-commerce site with a catalogue, payments and order tracking runs €300 to €1,000 a month. A business web application sits between €500 and €1,500 a month. Those figures assume a standard service level: a four-hour response during business hours and 99% availability.
What does a maintenance contract actually include?
Four different jobs usually sold as one word. Corrective maintenance fixes what breaks. Preventive maintenance applies dependency and security updates before they become incidents. Adaptive maintenance keeps the application working as browsers, payment providers and APIs change underneath it. Evolutive maintenance adds small features. A quote that does not separate them is impossible to compare with another one.
Can I skip maintenance to save money?
You can defer it, and the bill arrives later with interest. Unapplied security updates accumulate into a migration that has to be done all at once, usually under pressure after an incident. The pattern is predictable: two or three years of savings, then a bill larger than everything that was saved, plus the downtime. Deferring is a financing decision, not a saving.
Why is maintenance quoted as a percentage of the build cost?
Because it correlates loosely with complexity, and it is easy to write in a proposal. Treat it as a starting point rather than a rule: the real driver is the quality of the code you start from. A well-built application with tests and current dependencies costs far less to keep alive than a rushed one of the same size, and the difference grows every year.
Does an AI feature change the maintenance cost?
Yes, in two ways. The maintenance work itself typically runs 20 to 40% above an equivalent application without AI, because models, SDKs and provider APIs move quickly. On top of that sits the inference cost, which is variable and belongs in a separate budget line: it scales with usage rather than with the codebase, so mixing the two makes both impossible to forecast.
When should I renegotiate or change provider?
When you cannot get a straight answer about what was done last quarter, when small changes take weeks, or when every request turns into a quote for a project. A healthy maintenance relationship produces a short, boring report you can read in two minutes. The absence of that report is the signal, well before the invoice becomes the problem.
Before you sign anything
Ask for three things in writing: which of the four categories the contract covers, what the response commitment is and during which hours, and what a quarterly report will contain. A provider who can answer those in a paragraph is one you can hold to it. If the answer is a single monthly figure with no breakdown, you are not buying maintenance — you are buying the hope that nothing goes wrong.