A custom web app is not “done” the day it launches. Industry-standard planning puts ongoing maintenance at 15–25% of the build cost each year — a $200,000 app needs $30,000–$50,000 a year to stay secure and current (kavara.dev, 2026). Most SMBs discover this only after launch. Here’s how to plan, price, and contract it before you build.
Key Takeaways
- Budget 15–25% of the build cost per year for ongoing maintenance (kavara.dev, 2026).
- A retainer contract (fixed monthly) beats time-and-materials for actively maintained apps.
- Maintenance = bug fixes, security patches, dependency updates, monitoring, backups, and upgrades — not new features.
- Review the maintenance clause before you sign the build contract; it’s a hidden carrier of the total cost of ownership.
In this article
The Real Cost: It’s a Subscription, Not a One-Time Buy
The cheapest custom app is the one you never need to change. That rarely exists. Software decays: browsers update, libraries go end-of-life, security holes appear, and client needs shift. That’s the maintenance burden.
Here is what the planning rule looks like across project sizes:
The percentage is consistent because the underlying work scales with the code you maintain. For the build-cost bands these map to, see our custom web app development cost guide.
What Maintenance Actually Covers
A maintenance retainer is not “fix it when it breaks.” A good one includes:
- Security patching — applying upgrades for vulnerabilities in libraries, frameworks, and the server.
- Dependency and platform updates — keeping the tech stack current so it doesn’t hit end-of-life.
- Bug fixes — defects reported by real users, prioritized by severity.
- Monitoring and uptime — alerting when the app goes down or degrades, plus a response.
- Backups and recovery — verified, restorable copies of data and code.
- Small enhancements — minor changes under an agreed threshold (big features are quoted separately).
Retainer vs. Time-and-Materials: Which Contract?
Two models dominate, and they suit different situations:
| Contract | Best for | Pros | Cons |
|---|---|---|---|
| Monthly retainer | Actively used, mission-critical app | Predictable cost, priority support, proactive maintenance | You pay even in light months |
| Time-and-materials (T&M) | Occasional, well-scoped fixes | Pay only for work done | No proactive care, slower response |
For the first 1–2 years after launch — when bugs surface and features evolve fastest — a retainer is almost always the right call. It converts support from a surprise bill into a predictable line item.
The Hidden Carrier: The Maintenance Clause in Your Build Contract
The single most common SMB mistake is ignoring maintenance at signing. You chase the build quote and miss that the real total cost of ownership lives in the years after launch. Before you sign:
- Ask for the maintenance percentage in writing in the first proposal (not discovered later).
- Confirm what’s included vs. billed extra (new features are usually extra).
- Agree on the SLA: response time, uptime target, and severity levels.
- Understand who owns the code and whether you can switch support providers.
For the full vetting checklist, see how to choose a custom web app development company.
Wrap Maintenance Into Your Budget From Day One
Model it honestly before you green-light the build. A maintenance-contract provider will also often protect your investment better than an in-house hire can on a per-project basis. When you’re ready to scope, the SMB buyer’s decision guide walks through total cost of ownership end to end.
Frequently Asked Questions about Web App Maintenance & Support
How much does web app maintenance cost?
Plan on 15–25% of the build cost per year. A $200,000 app needs roughly $30,000–$50,000 a year to stay secure and updated (kavara.dev, 2026).
What does a web app maintenance contract include?
A solid retainer covers bug fixes, security patching, dependency and platform updates, monitoring, backups, uptime response, and a defined SLA. Feature development is usually quoted separately.
Retainer or time-and-materials for maintenance?
A monthly retainer gives predictable cost and priority support for actively maintained apps; time-and-materials suits occasional scoped fixes. Retainers fit most SMB apps in the first 1–2 years after launch.
Can I skip maintenance to save money?
You can, but the risk compounds — unpatched security holes and end-of-life dependencies eventually force a costly, unplanned rebuild. Budgeted maintenance is cheaper than a reactive rescue.
