Skip to content
DT Nova

Software maintenance cost: what to budget each year

Software maintenance cost is the yearly cost of keeping a system secure, working and useful after launch. It is set by how large the system is, how many libraries and outside services it depends on, how often the business needs changes, how critical the system is and what condition the code is in. This guide explains the four kinds of maintenance, what drives the yearly cost, the pricing models, the hidden costs of skipping maintenance, and how to compare offers.

It does not quote our own prices. It explains how a maintenance budget is built, so any offer you receive, from us or from anyone else, can be compared on the same basis. For what we cover, see software maintenance services; for apps, see mobile app maintenance.

The short version

  • Maintenance is not optional. The environment around software changes even when the software does not.
  • Four kinds of work: fixing faults, adapting to change, improving and preventing.
  • Running costs sit beside it: hosting, third-party services, monitoring and backups.
  • A written scope turns maintenance from surprises into a predictable line in the budget.

The four kinds of software maintenance

KindWhat it coversExample
CorrectiveFixing faults found in useA report shows wrong totals for one month
AdaptiveKeeping up with a changing environmentA connected service retires the interface version you use
PerfectiveImproving what already worksA slow screen is made faster; a form gets a new field
PreventiveReducing future problemsLibraries upgraded before they lose security support

Corrective work is what most people picture, but adaptive and preventive work usually decide whether a system stays economical to own. Our guide to technical debt explains why.

What drives software maintenance cost

  • Size and complexity. More screens, rules and data mean more to keep working.
  • Dependencies. Every library, framework and outside service publishes updates on its own schedule.
  • Integrations. Each connection breaks when the other side changes. See API integration cost.
  • Rate of change. A system the business changes monthly needs more perfective work.
  • Criticality. Faster response times and out-of-hours cover cost more.
  • Code condition. Missing tests and documentation make every change slower and riskier.
  • Regulation. Under the EU Cyber Resilience Act, manufacturers of products with digital elements must handle vulnerabilities effectively for a support period that reflects how long the product is expected to be in use (Regulation (EU) 2024/2847, Article 13(8), read 12 November 2026). See our guide to the Cyber Resilience Act.

People's time

Maintenance is labour, and labour costs follow location. Eurostat's release of 31 March 2026 puts average hourly labour costs across the whole economy in 2025 at €34.9 in the EU and €38.2 in the euro area, from €12.0 in Bulgaria to €56.8 in Luxembourg (read 12 November 2026). Knowledge matters more than rate: a team that knows the code spends fewer hours on each change, which is why documentation and tests pay for themselves.

Pricing models for maintenance

ModelHow it worksWhat to watch
Fixed monthly fee for a scopeAn agreed list of systems, tasks and response timesWhat counts as new work, and how it is priced
Retainer of hoursA set number of hours each month for any maintenance workWhether unused hours roll over
Time and materialsWork billed when neededNo preventive work happens unless someone orders it
Licence maintenanceA yearly fee for updates to bought softwareCustomisations are usually not covered

For most business systems, a fixed monthly fee for a written scope, with new features priced separately, gives the most predictable budget.

Running costs beside maintenance

Hosting, databases, email delivery, monitoring, backups, domains and certificates are recurring costs that grow with use. Keep them in the same budget line as maintenance, and review them yearly; unused resources are a common source of waste.

How to set a maintenance budget

Start from the system, not from a percentage. List what it depends on: frameworks and their support dates, outside services and their interface versions, certificates and domains. Add the changes the business already knows it will need next year. Then agree the response times that match how critical the system is. Each item becomes a line in a written scope, and the total becomes the yearly budget. Review it once a year against what actually happened: if most hours went to faults, invest in tests; if most went to forced upgrades, plan them earlier.

The hidden cost of skipping maintenance

  • Security exposure from libraries that no longer receive fixes.
  • Forced upgrades done in a hurry when a platform or service ends support.
  • Slower changes as old code becomes harder to understand.
  • Rewrites that cost far more than the maintenance would have.
  • Dependence on one person who still knows how the system works.

How to compare maintenance offers

  • Which systems, environments and integrations are covered?
  • Which of the four kinds of work are included?
  • Response and fix times by severity, and support hours?
  • How are dependency and security updates handled, and how often?
  • Is monitoring included, and who receives alerts?
  • What counts as new work, and how is it priced?
  • Notice period, and handover if the agreement ends?
  • Are code, hosting and domains in your company's name?

Ways to keep maintenance cost down

  • Fewer dependencies, kept current in small steps.
  • Automated tests and deployments make each change cheaper and safer.
  • Monitoring finds faults before users do.
  • Remove unused features. Code nobody uses still needs upkeep.
  • Mainstream technology keeps the pool of people who can maintain it large.

Maintenance belongs in every budget from the start; see custom software development cost and managed IT services cost. All our services are on the services page, and every guide is in the guides library.

Questions people ask

How much does software maintenance cost per year?

It depends on the system: its size, how many outside services and libraries it depends on, how much it changes, how critical it is, and its technical condition. A rule of thumb expressed as a percentage of the build cost is often quoted, but it hides the real drivers. A written scope of what is covered, with response times, is a far better basis for a budget.

What are the four types of software maintenance?

Corrective maintenance fixes faults. Adaptive maintenance keeps the software working as its environment changes, such as new operating system versions, browsers and interfaces. Perfective maintenance improves what already works. Preventive maintenance reduces future problems, for example by upgrading libraries and paying down technical debt.

Why does software need maintenance if nothing changes?

Because everything around it changes. Libraries publish security fixes, operating systems and browsers update, connected services retire old interface versions, certificates expire, and new laws apply to software sold or used in the EU. Software left alone becomes less secure and harder to change every month.

Is maintenance cheaper with the original team?

Often, because they know the code. But it should never depend on them: code in your own repository, written documentation and mainstream technology let another team take over. That option keeps the price honest.

How do we reduce software maintenance cost?

Keep dependencies few and current, automate tests and deployments, monitor the system so faults are found early, remove features nobody uses, and pay down technical debt in small steps rather than waiting for a rewrite.

Sources

Your maintenance scope checklist

  • Systems, environments and integrations to cover.
  • How critical each system is, and the response times needed.
  • Support hours: office hours or around the clock.
  • How often you expect changes, and roughly how large.
  • Dependencies and outside services the system relies on.
  • Monitoring, backups and who receives alerts.
  • Known technical debt to pay down.
  • Security update rules that apply to your product.
  • Notice period and handover terms.
  • Ownership: code, hosting and domains in your company's name.