What does software maintenance cost after launch?
Software is not finished when it launches
A launched product sits on top of things that keep changing: operating systems, browsers, libraries, cloud services, payment providers and security threats. Even if you add no features, it needs regular work to keep running safely.
Budgeting only for the build is the most common planning mistake with software.
What maintenance pays for
- Security patches and dependency updates.
- Compatibility with new browser, iOS and Android versions.
- Hosting, backups, monitoring and alerting.
- Fixing bugs that only appear with real data and real users.
- Small improvements and changes to how the product is used.
- Someone who knows the system and can answer quickly when something breaks.
How much should you plan for?
A common rule of thumb is to set aside a meaningful yearly share of the original build cost, often discussed as somewhere around 15 to 25 percent. Treat that as a starting point, not a promise: it depends on how complex the system is, how many integrations it has and how fast you want it to grow.
A simple internal tool with few integrations can cost far less. A product with payments, many users and several third-party services costs more.
What makes maintenance more expensive
- No documentation or tests, so every change is risky.
- Outdated dependencies left unattended for years, which turns small upgrades into rewrites.
- Many tightly coupled integrations.
- Switching vendors without a proper handover.
Ways to keep it predictable
Agree a support plan before launch: what is covered, how fast issues get a response, and how changes are requested and priced. A fixed monthly retainer for support and updates, plus separately scoped work for new features, keeps the budget predictable and the product healthy.
The cheapest maintenance is the kind you start early. Small, regular updates cost much less than a large catch-up after two years of neglect.