The short answer
- Running costs after launch come from hosting, third-party services, security and dependency updates, operating system and app store changes, monitoring, support and small improvements.
- A common rule of thumb is to budget 15 to 20 per cent of the original build cost each year, but a bottom-up estimate for your own system is more reliable.
- Mobile apps add a yearly cycle of work, because Apple and Google raise their technical requirements and each new operating system changes how apps behave.
Software maintenance is the work and spending needed to keep an application running, secure and useful after it launches, and it starts on the day the software goes live. The main costs are hosting, third-party services, security and dependency updates, operating system and app store changes, monitoring, support and small improvements. A common rule of thumb puts the yearly total at 15 to 20 per cent of the original build cost, but your own figure depends on what the software does and how it was built.
Why software costs money after launch
Software sits on top of things that keep moving. The framework it is written in releases new versions and eventually stops supporting old ones. Browsers, iOS and Android change every year. Security flaws are found in packages that were safe when you launched. Third-party services change their APIs and retire old versions. None of this is visible to your users until something breaks.
The other half is the business itself. Once people use the software, they find things it should do differently, and processes change. A system that nobody changes for two years is usually a system people have started working around.
Much of the long-term cost is set before launch, by choices about platforms and features. Our guide to what drives app cost covers the build side.
The cost drivers
This table sets out where maintenance money goes, what makes each item larger and how often it comes up.
| Cost driver | What it covers | What makes it bigger | How often |
|---|---|---|---|
| Hosting and infrastructure | Servers or serverless functions, databases, file storage, backups, content delivery | Traffic, stored files such as photos, uptime requirements, extra environments for testing | Monthly |
| Third-party services | Payments, email and SMS sending, maps, search, AI models, video | Usage-based pricing that grows with your customers, per-seat tools | Monthly |
| Security updates | Patching known vulnerabilities in packages and operating systems | Number of dependencies, how far behind they are | Weekly to monthly |
| Dependency and framework upgrades | Moving to supported versions of languages, frameworks and libraries | Large version jumps left too long | Several times a year |
| Operating system and app store changes | New iOS and Android versions, new store requirements | Number of platforms, use of device features | Yearly, with deadlines |
| Monitoring and incident response | Error tracking, uptime checks, logs, someone responding to alerts | Out-of-hours cover, strict response times | Continuous |
| Support | Answering users, investigating bugs, correcting data | Number of users, complexity of the workflows | Weekly |
| Small improvements | Changes users ask for, new reports, adjusted business rules | How fast the business changes | Monthly |
| Renewals and compliance | Domains, developer programme memberships, data protection requests | Number of accounts, products and markets | Yearly |
Mobile apps and the yearly platform cycle
Mobile apps carry a cost that websites mostly avoid. Apple and Google release a major operating system version every year, and each one can change permissions, background behaviour or how screens are laid out. Both stores also raise their minimum technical requirements on a schedule.
- Google Play requires new apps and updates to target a recent Android API level, and the required level rises each year. Apps that fall too far behind stop being available to new users on newer devices.
- Apple periodically requires apps submitted to the App Store to be built with a recent version of Xcode and the iOS SDK. An app that cannot be built with current tools cannot ship an update, including an urgent fix.
- Store policies change too. Requirements for in-app account deletion, privacy labels and Google’s Data safety form have all arrived over the past few years, and existing apps had to comply.
Estimark runs on the web, iPhone and Android, so every one of these cycles applies to it. For any product with apps in both stores, plan for platform work every year whether or not you add a feature.
How to budget for maintenance
Start with the rule of thumb
The figure you will hear most often is 15 to 20 per cent of the original build cost each year. It is a rule of thumb passed around the industry. No study stands behind it, and it can be wrong in both directions. It is useful as a sense check. If your software cost £80,000 to build, the rule suggests £12,000 to £16,000 a year, or about £1,000 to £1,333 a month.
Then build it from the bottom up
A better estimate adds up the drivers for your own system.
- List every paid service with its current monthly bill, then estimate how each grows as you add customers.
- Count the engineering days needed each year for security patches, upgrades and platform changes. A web app with few dependencies needs fewer than a product with apps in both stores.
- Estimate support time from the number of users and how often they get in touch.
- Decide how much improvement you want each month, in days.
- Add a contingency for the unexpected, such as a vulnerability that needs an urgent fix or a provider retiring an API you depend on.
Compare the total with the rule of thumb. If yours is far lower, check whether you have left out improvements.
Separate keeping the lights on from improving the product
Split the budget in two. Keeping the lights on covers hosting, services, security, upgrades, monitoring and bug fixes, and it is not optional. Improvement covers new reports, changes to workflows and new features. It is where the software keeps earning its place, and it is the part most easily cut when money is tight. A budget that covers only the first tends to fall short, because users always ask for changes.
What makes maintenance cheaper
Most maintenance cost is decided during the build. These choices reduce it for years afterwards.
- Fewer dependencies. Every package is something to update. Add one only when it saves real work.
- Automated tests. An upgrade is cheap when a test suite tells you within minutes whether anything broke, and expensive when someone has to click through every screen.
- Small, regular upgrades. Moving one version at a time every few months is far easier than jumping several versions after years of neglect.
- Managed services. A managed database with automatic backups usually costs more per month than a server you run yourself, and much less in engineering time.
- Monitoring from day one. Error tracking tells you about a problem before a customer does, while it is still small.
- Ownership and documentation. If the code, accounts and runbook are yours, you can change who maintains the software without paying someone to rediscover how it works.
Ways to pay for maintenance
Maintenance is usually paid for in one of three ways. A monthly retainer buys a set amount of time and often an agreed response time for problems. Pay-as-you-go work is billed when you need it, which suits stable software but gives no guarantee that anyone is available when something breaks. An in-house developer gives continuity, though one person may not cover security, infrastructure and both mobile platforms. Whichever you choose, write down who responds to an outage, how quickly and at what hours. The trade-offs are similar to those in choosing between an agency, a freelancer or an in-house team.
Questions people ask
How much does it cost to maintain an app each year?
There is no single figure, because it depends on hosting, services, platforms and how much you want to change. A common rule of thumb is 15 to 20 per cent of the build cost each year. Use it as a sense check, and build a bottom-up estimate from your own services and engineering time.
Can I stop paying for maintenance once the software is finished?
You can stop adding features, but you cannot safely stop hosting, security updates or platform changes. Unpatched software becomes a security risk, and a mobile app that falls behind store requirements can no longer be updated and may disappear for new users. Software that people use is never finished in that sense.
Why does a mobile app need updating when nothing has changed?
The platforms it runs on have changed. Apple and Google release new operating systems every year and raise the minimum requirements for apps in their stores. An app that is not updated gradually stops meeting them, and eventually cannot be updated at all without a larger piece of work.
Is hosting the biggest maintenance cost?
Often it is not. For many business applications, engineering time for updates, support and improvements costs more than the servers. Hosting becomes significant when an application stores large files, processes video or calls AI models at high volume.