Software maintenance cost is the yearly spend needed to keep live software working, secure and useful. Budgets are commonly planned at about 15 to 20% of the original build cost a year, and some sources go up to about 25%. This is a rule of thumb, not a quote, and it should be replaced by real figures.
This guide is for founders, finance leads and operations managers who need a number for next year's budget, or who have a maintenance quote and want to know whether it makes sense. It covers how to estimate the cost, what the money pays for, how vendors charge and what pushes the figure up or down. For the basics of the work itself, see our guide on what software maintenance covers. If you want a supplier to run this for you, see our software maintenance and support service. All figures here are market rules of thumb or illustrations, not Timeline Digital prices.
Key takeaways
- Start with 15 to 20% of build cost a year as a planning figure, then replace it with actual hours after the first year.
- Split the budget into run costs (hosting, licences, monitoring) and change costs (fixes and features). They behave differently.
- Custom software maintenance and commercial licence maintenance are different things. A licence fee is a percentage of what you paid the vendor, and it normally does not cover your own customisations.
- Compare pricing models on what is excluded, not only on the monthly number.
- Critical systems, many integrations, round-the-clock cover and old code all push the cost up.
- A low maintenance budget does not remove the cost. It usually moves it into a later, larger rebuild.
How much does software maintenance cost per year?
Software maintenance commonly costs about 15 to 20% of the original build cost per year, with some sources using up to about 25%. A system that cost 100,000 to build would therefore need about 15,000 to 20,000 a year. The range is a widely repeated practitioner rule of thumb rather than a measured industry standard.
| Original build cost | 15% a year | 20% a year | 25% a year |
|---|
| 50,000 | 7,500 | 10,000 | 12,500 |
| 100,000 | 15,000 | 20,000 | 25,000 |
| 250,000 | 37,500 | 50,000 | 62,500 |
| 500,000 | 75,000 | 100,000 | 125,000 |
These figures are arithmetic in any currency, not price quotes. Use the lower end for a stable internal tool with few integrations, and the higher end for a customer-facing or fast-changing product. A system still gaining features can pass these figures, which is a sign that part of the "maintenance" budget is really new development.
What does a software maintenance budget pay for?
A software maintenance budget pays for two kinds of cost: run costs that keep the system available, such as hosting, licences, monitoring, backups and patching, and change costs that alter it, such as bug fixes, compatibility work and small improvements. Separating them shows what is unavoidable and what the business can choose to spend.
| Cost line | Type | What drives it |
|---|
| Hosting and infrastructure | Run | Users, data volume, environments, redundancy |
| Third-party licences and APIs | Run | Vendor price changes, usage, seats |
| Monitoring, backups and restore tests | Run | Criticality, retention, recovery targets |
| Security patching and dependency updates | Run | Number of libraries, framework age |
| Support desk and on-call cover | Run | Hours covered, response targets |
| Bug fixes (corrective) | Change | Code quality, test coverage |
| Compatibility and regulatory work (adaptive) | Change | Browser, operating system, API and tax changes |
| Small improvements (perfective) | Change | Business appetite, backlog size |
| Refactoring and clean-up (preventive) | Change | Age and accumulated shortcuts |
The rule of thumb does not always include hosting and third-party fees, so ask any supplier which of these lines their figure covers. A quote that looks cheap often leaves out infrastructure and licences.
What are software maintenance fees on commercial software?
Software maintenance fees on commercial software are annual charges for support and updates, usually set as a percentage of the licence price rather than of a build. SAP Enterprise Support and Oracle support have both been widely reported at about 22% of net licence value. Check your own contract, because rates and terms vary by agreement.
The differences from custom software matter when you compare the two:
- What the fee covers. Vendor support and new releases of the standard product. Your customisations and integrations are normally a separate cost.
- What the base is. A percentage of the licence value, which can stay on the invoice long after the licence was paid for.
- What happens if you stop. Stopping may mean losing updates, and rejoining can carry extra charges. Read the reinstatement clause before deciding.
- Subscription software. With SaaS, support and updates are generally included in the subscription, so there is no separate line, but the price can rise at renewal.
Our ERP total cost of ownership guide shows how these fees fit into a multi-year comparison.
Which software maintenance pricing models are common?
Common software maintenance pricing models are a monthly retainer with included hours, a pre-paid block of hours, time and materials, a per-ticket charge and a fixed annual percentage of the build. The right model depends on how predictable your work is, how critical the system is and how much budget certainty finance needs.
| Model | How it charges | Suits | Watch out for |
|---|
| Monthly retainer | Fixed monthly fee with agreed hours or scope | Live systems needing steady attention | Unused hours expiring; what counts as out of scope |
| Pre-paid hours block | Hours bought in advance, drawn down | Stable systems with occasional work | Expiry dates; no guaranteed response time |
| Time and materials | Hours used, billed in arrears | Irregular or exploratory work | Hard to budget; no incentive to reduce tickets |
| Per ticket | Fee per incident or request | Simple, low-volume support | Disputes over what one ticket includes |
| Percentage of build | Annual fee based on the original cost | Simple budgeting at contract stage | The fee may not match the actual effort |
| Licence maintenance | Percentage of licence value | Commercial packaged software | Excludes your customisations; renewal rises |
Whatever the model, ask for the service level terms in writing. Our guide to what a software SLA should include lists the clauses to check.
What makes software maintenance cost more or less?
Software maintenance costs more when a system is business-critical, has many integrations, runs on old frameworks, lacks automated tests or needs round-the-clock support. It costs less when the system is simple and stable, tests are automated, documentation exists and upgrades are routine. Code quality and integration count are usually the factors a business underestimates.
| Factor | Pushes cost up | Pulls cost down |
|---|
| Criticality | Outage stops revenue or operations | Internal tool with manual fallback |
| Support hours | 24x7 cover with fast response | Business hours only |
| Integrations | Many external systems and vendor APIs | Few, stable connections |
| Code and tests | Little test coverage, undocumented code | Automated tests, written runbooks |
| Technology age | Frameworks past end of support | Current, supported versions |
| Regulation | Tax or sector rules that change often | Few external rule changes |
| Rate of change | New features every month | Feature-complete system |
Worked example: a one-year budget (illustrative)
This example is made up to show the method, with no currency implied. It is not a benchmark or a Timeline Digital price. A customer portal cost 150,000 to build, has three integrations and needs business-hours support. The rule of thumb gives 22,500 to 30,000 a year.
| Budget line | Type | Amount a year |
|---|
| Hosting, backups and monitoring | Run | 6,000 |
| Third-party licences and APIs | Run | 3,000 |
| Security patching and dependency updates | Run | 4,500 |
| Support desk, business hours | Run | 4,000 |
| Bug fixes and compatibility work | Change | 6,000 |
| Small improvements | Change | 3,500 |
| Total | | 27,000 |
The total is 18% of the build cost, inside the expected range. Without the hosting and third-party lines, which some suppliers leave out of the percentage, the figure is 18,000, or 12%. Run costs come to 17,500 and change costs to 9,500. If the business asks to cut 3,000, this split shows the real choice: fewer small improvements is a decision it can make, while removing patching only stores up risk. At the end of the year, replace each line with what was actually spent.
How can you reduce software maintenance cost safely?
You can reduce software maintenance cost safely by removing unused features and integrations, adding automated tests around the riskiest areas, staying on supported framework versions and consolidating overlapping tools. Avoid cutting patching, backups or restore tests. Those savings look good for a year and tend to return later as an incident or a forced upgrade.
- Retire what nobody uses. Every feature and integration needs testing at each upgrade.
- Upgrade little and often. Small regular upgrades are normally cheaper than a large jump after years of neglect.
- Automate the checks that repeat. Regression tests and deployment scripts reduce time spent on each change.
- Review third-party bills yearly. Seats and API tiers tend to grow without anyone deciding they should.
- Keep documentation current. A runbook reduces the time a new person needs to fix a fault.
When is a percentage rule the wrong approach?
A percentage rule is the wrong approach once you have real data, or when the build cost is not a fair guide to the effort. This applies to inherited systems, heavily discounted builds, very old software and products under active development. In those cases, use an audit of the code and actual support hours instead.
- Inherited or legacy systems. The original price may be unknown or decades old. A short technical audit is a better base. Our guide on legacy modernization options covers what to do if the numbers no longer make sense.
- Products still growing. Roadmap development is not maintenance, so give it its own budget.
- Commercial packages. Use the contract percentage plus your own customisation and integration costs.
- Second and later years. Your own actual hours are always better than a market rule.
Glossary: corrective maintenance, fixing defects; adaptive maintenance, keeping up with platform and rule changes; perfective maintenance, improving or extending features; preventive maintenance, reducing future failures; run cost, what it takes to keep a system available; change cost, what it takes to alter it; net licence value, the licence price after discounts, used as the base for many vendor fees.
How Timeline Digital approaches maintenance
Timeline Digital is a custom software development company founded in 2013 and headquartered in Islamabad, Pakistan, that delivers software as managed projects and supports it after launch under a service level agreement. There is no fixed timeframe: the schedule for your system is set from your requirements in the Plan step. The free pilot of 2 to 3 key modules is ready in about 2 days, and with 1,200+ developers we have the capacity to deliver a focused system in as little as 2 weeks. The full project starts after you approve the pilot, and the scope, milestones and terms are agreed after it. Timeline Digital does not publish prices for custom software, because every project is custom.