Short answer: after launch, a custom web app needs four things — a place to live (hosting), occasional updates, the odd small fix, and new features when your business grows. For a small business app, that usually means tens of dollars a month in hosting plus support terms you can actually read. And because you own the code, you're never trapped with one developer.
This is the question buyers rarely ask out loud: what if it breaks and the developer disappears? It's a fair fear — the industry earned it. So here's the honest picture of life after launch, including the parts that protect you.
What maintenance actually involves
For a custom web app, "maintenance" is four small jobs, not one mysterious big one:
- Hosting. Server rent — the app has to run somewhere. For a small business app this is cheap and boring, the way rent should be.
- Updates. The building blocks under your app (frameworks, libraries) get security patches. Applying them is an hour here and there, not a project.
- Small fixes. The button that misbehaves on one person's phone, the report that formats oddly. Minutes to hours of work, occasionally.
- Feature additions. The good kind: the app is earning its keep, so you want it to do more. This is growth wearing a maintenance costume.
Worth saying plainly: software doesn't rust. A small app nobody changes can run quietly for years. Most "maintenance" spending is really evolution — the business changed, so the software should too.
What it costs, realistically
Hosting for a typical small business app runs tens of dollars a month, often under $50 — you're serving a team and your customers, not the population of Europe. Anyone quoting hundreds a month for a small app should be able to explain exactly why.
Support should come in plain English, and usually one of two shapes: pay-as-you-go (you call when something needs attention, you pay for that work) or a modest monthly agreement when the app is critical enough to want guaranteed response times. What you shouldn't accept is a fat retainer for vague promises. We put maintenance expectations in the quote up front — that's part of the point of fixed-price development — and our cost guide covers the build side.
The escape hatch: you own the code
Here's the part that dissolves the disappearing-developer fear. When a project is done right, you own the code, the data, and the hosting accounts — in your name, not the developer's. The app is built on standard, boring technology on purpose, so any competent developer can pick it up, read it, and carry on. If we got hit by a meteor tomorrow, your software wouldn't notice.
That ownership is your leverage, and a developer who's confident in their work hands it over gladly. It's also one of the first things to verify before hiring anyone — it sits near the top of our questions to ask a software developer.
Red flags in maintenance contracts
- Per-seat fees on your own software. You paid to build it; paying again for every employee who logs in is a subscription with extra steps.
- Hostage hosting. Only they can host it, and you can't have the code or account access. Hosting should be portable — you should be able to move it like you'd change landlords.
- You license instead of own. If the contract says "license" where it should say "own," ask why. Then keep asking.
- Vague retainers. A monthly "maintenance" fee that never itemizes what was maintained. Stable months should cost you almost nothing.
None of these are normal or necessary. They're business models built on lock-in, and the fix is simple: don't sign them.
Frequently asked questions
How much does it cost to maintain a custom web app?
For a typical small business app, hosting usually runs under $50 a month, and support is either pay-as-you-go or a small monthly agreement. Budget a few hundred dollars a year for a stable app that isn't changing — more only when you're actively adding features.
What happens if my developer disappears?
If you own the code — and you should — another developer takes over. That's why ownership and standard technology matter more than any contract clause: the code, the data, and the hosting accounts should all be in your name from day one.
Do I need a monthly maintenance contract?
Not necessarily. A small, stable app can run for months without needing attention, so pay-as-you-go support is often enough. A monthly agreement makes sense once the app is critical to daily operations and you want guaranteed response times.