Blog What does a custom app cost after launch?
Your app is live. The build invoice is behind you, but the app still needs somewhere to run, people to look after it, and room to change as customers use it. What should you budget for?
There is no useful flat monthly price for every custom app. A simple internal tool and an app that handles payments, uploads, and thousands of customer accounts have different bills. You can still make a useful estimate by separating the costs that keep the current app running from the work you choose to add next.
Start with two budgets
The first budget is for running the app you already have: hosting, outside services, monitoring, backups, and maintenance. The second is for changing it: new features, design work, and improvements prompted by customer feedback. Mixing the two makes it hard to tell whether the app has become expensive to operate or you are choosing to invest more in the product.
Ask whoever builds the app to put both budgets in writing before launch. An estimate should name the services, expected usage, who pays each bill, and what work a support agreement covers.
What keeps the app running?
Most apps pay for some combination of a server or hosting platform, a database, file storage, a domain, backups, and error monitoring. Many also pay outside providers to send email or text messages, process payments, show maps, or call an AI model. Some services charge a fixed monthly amount. Others charge for each message, transaction, file, or request.
The service list matters more than a single hosting quote. A low server bill will not tell you what it costs to send appointment reminders or process a growing number of payments. List every provider and record what drives its bill. For payments, distinguish the provider's transaction fees from the cost of maintaining the checkout workflow.
Get access to the accounts your business depends on. You should be able to see the bills, usage, and alerts yourself, even if your development partner manages the day-to-day setup.
What does maintenance pay for?
A live app needs someone to notice failures and act on them. That may include checking errors, applying security and dependency updates, renewing certificates, testing backups, and fixing problems when a connected service changes. A mobile app may also need updates to keep working with new iOS and Android releases.
A support agreement should answer practical questions: Who receives an alert when signups stop working? When will they respond? Is a bug fix included? What happens outside business hours? How are larger changes estimated and approved? “Maintenance included” is hard to budget around until those answers are clear.
If your team will handle support, set aside staff time for it. A provider's automated backups and status page help, but someone still has to investigate an incident and make a decision.
Plan for usage to change the bill
Work out which actions cost money. For one product it might be each text reminder. For another it is an uploaded video or a report generated with an AI model. Estimate how often a customer will take that action, then repeat the calculation for a busier month. This gives you a better forecast than multiplying today's hosting bill by twelve.
Set spending alerts and sensible limits where a provider supports them. Check the first few invoices against the forecast. If a feature's usage grows faster than expected, you can change its design or price before the bill becomes a surprise.
Make a year-one estimate
Write down these amounts separately. The blanks are a prompt to get actual quotes and usage data for your app.
| Cost | What to ask |
|---|---|
| Base monthly services | What do we pay even in a quiet month? |
| Usage-based services | What does a normal month cost? What about a busy one? |
| Maintenance and support | What work is covered, and who responds to incidents? |
| Planned improvements | Which changes are already on the roadmap? |
For a first pass, multiply the three recurring monthly amounts by twelve, then add the work you plan to commission. Keep a reserve for unexpected fixes or a busier month. The right reserve depends on how important the app is to your business and how predictable its usage is. Revisit the estimate once you have real invoices and support history.
Questions to ask before you sign off on the build
- Which hosting and service accounts will our business own?
- What will each provider bill us for, and where can we see usage?
- What is the expected bill in a normal month and a busy month?
- Who monitors the app, responds to incidents, and tests recovery from backups?
- What does the support agreement include, and how do we approve extra work?
- If we change developers, what documentation and access will we receive?
A good launch plan answers these questions alongside the feature list. If you are still deciding whether an app is ready for customers, our guide to moving an AI-built app into production covers the reliability and security checks worth making before people depend on it.
Talk through your app's ongoing costs
At Bootpack Digital, we build and support custom web and mobile apps. We can review an existing app or scope a new one, list the services it needs, and explain the ongoing work before you commit to a build. Bring us what you know about your users and the tasks they will perform. We will turn that into a budget you can question and revise.