Home / Insights / Software Costs and Budgets
Software Costs and Budgets
Software Maintenance Costs: What Businesses Should Budget After Launch
How to plan the cost of keeping software healthy after launch: separate maintenance from new features, inventory what you own, build a cost breakdown, choose a support arrangement and prioritise maintenance risk.
TopicsSoftware Costs and BudgetsArchitecture and Modernization
Key takeaways
- Separate maintenance (keeping software working and secure) from enhancement (new features); budget them differently.
- Build the budget bottom-up from an inventory of dependencies, infrastructure and support needs, not from a percentage rule of thumb.
- Prioritise maintenance by risk: security first, then compatibility, reliability and technical debt.
On this page
Software is never finished. Operating systems change, dependencies release security fixes, cloud services evolve and users find bugs. Without a maintenance budget, these issues accumulate until a small fix becomes an emergency. This guide shows how to plan maintenance costs from what you actually run, rather than from a rule of thumb.
Separate maintenance support and new features
| Category | Examples | Budget approach |
|---|---|---|
| Reactive support | Bug fixes, incident response, data corrections | Reserved hours or retainer |
| Preventive maintenance | Dependency updates, security patches, OS and framework upgrades | Planned monthly or quarterly effort |
| Operations | Monitoring, backups, cost optimisation | Ongoing hours plus tools |
| Enhancements | New features, redesigns, integrations | Project budget or roadmap capacity |
Maintenance categories.
Mixing these leads to problems: urgent features crowd out security updates, or maintenance budgets get spent on new work. Track them separately even if the same team handles both.
Inventory the product first
You cannot budget maintenance without knowing what you maintain. List:
- Applications: web, mobile, admin, APIs, background jobs.
- Frameworks and languages: with versions and support status.
- Third-party dependencies and services: libraries, SaaS tools, APIs.
- Infrastructure: cloud services, environments, domains, certificates.
- Integrations: systems you exchange data with.
- Ownership: who holds repositories, accounts and credentials.
- Documentation: what exists and how current it is.
If you inherited software from another team, start with our checklist on taking over an inherited codebase.
Framework and platform support timelines matter. Many frameworks publish end-of-life dates; mobile apps must keep up with new iOS and Android releases and store requirements. Note these dates in your inventory so upgrades can be planned, not rushed.
Build a maintenance cost breakdown
| Line | Driver | How to estimate |
|---|---|---|
| Engineering hours | Size of system, change frequency, incident history | Review last 6–12 months of tickets |
| Monitoring and tooling | Error tracking, uptime, logs | Tool subscriptions |
| Cloud infrastructure | Usage | Current bills, growth forecast |
| Licences and services | Third-party subscriptions | Current contracts |
| Planned upgrades | Framework or OS end-of-life dates | Estimate each upgrade separately |
| Security work | Patches, audits, penetration tests | Policy and customer requirements |
Maintenance cost breakdown.
Maintenance budget worksheet (illustrative)
| Item | Monthly | Notes |
|---|---|---|
| Reactive support: 25 hours × $30 | $750 | Illustrative rate |
| Preventive updates: 15 hours × $30 | $450 | Dependencies and patches |
| Monitoring tools | $80 | Example subscription |
| Cloud hosting | $350 | Example from current bill |
| Planned upgrade reserve: 10 hours × $30 | $300 | Saved toward next major upgrade |
| Monthly total | $1,930 |
Illustrative worksheet. Replace every figure with your own.
We deliberately avoid the common “X% of build cost per year” rule. Without data from your own system it can be far too high or too low. Your ticket history and inventory are better guides.
Compare support arrangements
| Arrangement | How it works | Good for | Watch for |
|---|---|---|---|
| Reserved hours | A fixed number of hours per month | Predictable needs | Unused hours policy |
| Retainer with response targets | Monthly fee for availability and agreed response times | Business-critical systems | What response targets include |
| Ad hoc | Pay per request | Low-change systems | Slow response, no proactive work |
| Dedicated maintenance team | People assigned to your product | Large or complex systems | Higher fixed cost |
Support arrangements. Terms depend on the agreement you sign.
Prioritise maintenance risk
Priority matrix
| Risk area | Example | Impact | Priority |
|---|---|---|---|
| Security | Known vulnerability in a dependency | High | Fix immediately |
| Compatibility | App fails on new OS version | High | Plan before OS release |
| Reliability | Recurring outages or slow pages | Medium–high | Schedule soon |
| Data integrity | Inconsistent records | High | Investigate quickly |
| Technical debt | Hard-to-change code slowing features | Medium | Plan gradual improvement |
| Cosmetic | Minor UI issues | Low | Batch with other work |
Prioritise by impact and likelihood.
Want a technical health check before you set a maintenance budget?
Prepare a support brief
When requesting maintenance proposals, share:
- Your inventory and current issues.
- Expected monthly change volume.
- Required response times for each severity level.
- Escalation contacts and hours.
- Release process and environments.
- Reporting you expect: hours used, incidents, system health.
Response times and service levels must be agreed in the contract; do not assume a provider’s standard terms match your needs.
Frequently asked questions
How much should I budget for maintenance?
Build it from your inventory and ticket history. The worksheet above shows the structure; your figures will differ.
Can a new team maintain software built by another company?
Yes, after a technical review and knowledge transfer.
Is monitoring part of maintenance?
It should be. Monitoring finds problems before users report them.
What happens if we skip maintenance?
Risks accumulate: security vulnerabilities, incompatible dependencies and app store rejections, which become more expensive to fix later.
Sources and methodology
Facts in this article were checked against the sources below on 5 November 2026. Directory data (ratings, review counts, rate bands and team sizes) changes over time and is shown as published on the date accessed. Illustrative examples are labelled as such and are not quotes.
- PoliteTech: Software Maintenance — accessed 5 November 2026. Service scope and approach
- PoliteTech Insights: Taking over a codebase — accessed 5 November 2026. Takeover checklist
Related reading
Continue your research
Need a maintenance plan you can budget?
Tell us what you run and what keeps breaking. We will suggest a support arrangement and a realistic monthly effort.