In short: budget 15 to 20% of the initial development cost each year to keep an app in working order, which means €6,000 to €12,000 a year for an MVP that cost €40,000–€60,000. In practice, this ranges from a few hundred euros a month for a stable, rarely changed app, to €1,000–€4,000 a month for a maintenance contract with guaranteed response times, and from around €5,000 a month once you also want to keep developing the product.
Maintenance is the line item most often forgotten in a business plan. Yet an app that is no longer maintained does not stay "as it is": it deteriorates. Recent weeks illustrate this well. On 3 November 2026, Next.js released patch versions 16.4.5 and 15.5.29 to fix seven vulnerabilities, three weeks after an emergency update that fixed a remote code execution flaw. If nobody is watching your app, nobody is applying those patches.
This article explains what maintenance covers, what it costs, and how to choose the right contract model.
Why does an app cost money even when nobody touches it?
Your code does not change, but everything around it does. A modern app relies on a framework, a runtime, dozens or hundreds of open-source libraries, third-party services and, for mobile, on Apple's and Google's rules. Each of these moves on its own schedule.
A few concrete examples from 2026:
- The app stores set their own rules. Since 28 April 2026, Apple has required every app uploaded to App Store Connect to be built with Xcode 26 and the iOS 26 SDK. On Android, since 31 August 2026, new apps and updates published on Google Play must target Android 16 (API 36). An app that does not keep up simply cannot publish an update any more, not even to fix an urgent bug.
- Runtimes reach end of life. Node.js 20 has not been maintained since 30 April 2026: no more security patches are released. Node.js 22 will follow on 30 April 2027. An API still running on Node.js 20 works, but it is exposed to flaws that will never be fixed.
- Frameworks ship security patches. Next.js maintains several major versions in parallel, but versions that are too old no longer receive fixes. The longer you wait, the heavier the upgrade becomes.
- Mobile architectures are being renewed. React Native has run entirely on its new architecture since version 0.82, and the team is gradually removing the old one with each release. An app stuck on an old version ends up accumulating incompatible libraries.
The result: an app left unmaintained for twelve to eighteen months often needs an upgrade project that costs several times the price of regular maintenance.
What exactly does app maintenance include?
There are traditionally four types of maintenance. A serious quote states which ones are included.
- Corrective maintenance: fixing bugs reported by users or detected by monitoring.
- Preventive and security maintenance: applying security patches, updating dependencies, monitoring errors and performance, checking backups.
- Adaptive maintenance: keeping up with changes imposed from outside, such as a new version of iOS or Android, an app store requirement, a third-party API that changes or a runtime reaching end of life.
- Evolutive maintenance: adding features, improving what exists, developing the product based on user feedback.
The first three keep the app alive. The fourth makes it grow. This is the main source of difference between two quotes: one covers maintenance in the strict sense, the other includes development capacity.
How much does maintenance cost? Price ranges
| Service level | What is included | Indicative budget (excl. VAT) | For whom |
|---|---|---|---|
| Minimal maintenance | Security updates, dependencies, backups, occasional fixes | €300 – €1,000 / month | Stable app, few users, no planned changes |
| Maintenance contract with commitments | Monitoring, fixes, app store and version updates, guaranteed response time | €1,000 – €4,000 / month | App used daily by customers or teams |
| Maintenance and new features | All of the above, plus regular development capacity | From €5,000 / month | Growing product, active roadmap |
| Full outsourced product team | Development, design, product and maintenance in one team | €8,000 – €25,000 / month | Startup or SME whose core business is the product |
These amounts are orders of magnitude for an experienced team in France. They exclude running costs, covered below.
The 15 to 20% per year rule remains a good starting point. For a €60,000 mobile app, that means €9,000 to €12,000 a year, or roughly €750 to €1,000 a month for maintenance in the strict sense. For a €150,000 SaaS, expect €22,000 to €30,000 a year.
What drives the maintenance budget
The quality of the original code
This is the first factor. Tested, documented code built on mainstream technologies is quick to maintain. Code written in a hurry, without tests, with exotic or abandoned libraries, turns every update into an investigation. AI-generated prototypes pushed to production without being reworked are an increasingly common case.
The number of platforms
A web app alone requires less effort than an iOS, Android and web app. Each platform adds its own rules, annual updates and testing. A shared codebase, with React Native for example, limits this effect without removing it.
The number of integrations
Payments, CRM, ERP, maps, messaging, AI APIs: every third-party service can change its API, pricing or terms. The more you have, the heavier adaptive maintenance becomes.
The level of service required
An internal app can wait until the next day. A payment platform or a health app requires continuous monitoring, on-call cover and response times of a few hours. Guaranteed response time is one of the most expensive items in a contract.
How old the versions are
An app maintained continuously moves from one version to the next in a few hours. An app two or three major versions behind, whether on Next.js, React Native or Node.js, can require several weeks of work. We explain this snowball effect in our article on reducing technical debt.
Running costs not to confuse with maintenance
Maintenance pays for human work. Alongside it, your app generates running costs you will pay whatever the provider:
- Hosting and databases: from a few tens of euros a month for an MVP to several thousand for a high-traffic platform.
- Developer accounts: 99 dollars a year for the Apple Developer Program, 25 dollars one-off for Google Play.
- Third-party services: transactional email, SMS, maps, search, error monitoring, often billed by volume.
- AI APIs: billed by usage, they can become a significant cost if your product depends on them.
- Domain names and certificates, usually marginal.
Ask your provider to list these costs separately. A maintenance quote that silently includes hosting makes comparisons impossible.
Fixed fee, time and materials, subscription or in-house: which model to choose?
| Model | How it works | Advantages | Limitations |
|---|---|---|---|
| Fixed-fee maintenance | Fixed monthly amount for a defined scope and response time | Predictable budget, guaranteed response times | New features are billed separately |
| Time and materials or hours bank | Pay for time spent, at a daily rate | Flexible, suited to occasional needs | Unpredictable cost, no continuous monitoring |
| Product subscription | Monthly capacity covering maintenance and new features | One team responsible for everything, priorities adjustable every month | Higher commitment, best kept for active products |
| Freelancer | An independent developer works on demand | Economical for a small app | Dependence on one person, uncertain availability |
| In-house hiring | One or more salaried developers | Full control, business knowledge | A senior developer often costs more than €6,000 to €8,000 a month including employer charges, and one person cannot cover every skill |
Our honest view: if your app is stable, used by few people and has no roadmap, a minimal maintenance plan or an hours bank is more than enough. Paying for a dedicated team would be a waste. Conversely, if your product is at the heart of your business and must evolve every month, splitting maintenance and new features between two providers creates more problems than it solves.
What should you do if your app has not been maintained for a long time?
This is a common situation: the original agency or freelancer is no longer available, the app still works, but nobody dares touch it any more. Three steps get you out of it without nasty surprises:
- Take stock. A technical audit identifies outdated versions, known vulnerabilities, code quality and the risk of being blocked on the app stores. It usually takes a few days of work.
- Deal with blockers first. An unmet app store requirement or a runtime without security patches comes before everything else.
- Put regular maintenance in place. Once the app is back up to date, a few hours a month are often enough to avoid going through the same situation again.
Sometimes the audit concludes that a rebuild costs less than an upgrade. This is rare for a well-built app less than five years old, and more common for a prototype that was never reworked. To estimate the cost of a new version, see our guide to the cost of a mobile app.
Frequently asked questions
What percentage of the initial budget should be set aside for maintenance?
Expect 15 to 20% of the initial development cost per year for maintenance in the strict sense: fixes, security, version and app store updates. This percentage rises if the app is critical, heavily integrated with other systems or available on several platforms. New features come on top of this budget.
Can a mobile app do without maintenance?
Not for long. Since 2026, Apple has required the iOS 26 SDK for every new submission and Google Play has required apps to target Android 16 to publish an update. Without maintenance, you quickly lose the ability to publish a fix, and the app deteriorates with each new operating system release, usually within twelve to eighteen months.
What is the difference between maintenance and new development?
Maintenance keeps the app in working order: fixing bugs, applying security patches, keeping up with app store and framework requirements. New development adds value: new features, a better experience, new user journeys. A good contract clearly separates the two, or explicitly groups them in a monthly capacity.
What should a maintenance contract include?
The exact scope (corrective, preventive, adaptive, evolutive), response times by severity, the hours covered, how incidents are reported, the reports provided, ownership of the code and access, whether hosting costs are included, and the exit conditions if you change provider.
Can maintenance be handed to a different agency from the one that built the app?
Yes, this is common. The new provider usually starts with an audit to understand the code, recover access and identify risks. Make sure you own the source code, the app store accounts, the hosting and the domain names: that is what allows you to change provider without being locked in.
👉 Does your app need regular care or an upgrade? Discover our maintenance and evolution service, or book a call to review your situation.
