# Software maintenance cost for tools and AI-built apps

> What to budget each month to keep an internal tool, automation or AI-built app running, what drives the cost, and how SBD prices care plans.

- Author: Pranav Mahaveer, Founder, SBD
- Published: 2026-11-22
- Updated: 2026-11-22
- Canonical: https://smallbaydigital.com/blog/software-maintenance-cost/
- Contact: hello@smallbaydigital.com

<p data-region-keep>Most of the cost of keeping software running is set by two things: how much the business relies on it, and how fast you need a fix when it breaks. Platform fees are usually the smaller part. At SBD, care plans start at $50 a month for one or two automations, and the Automation team plan at $999 a month covers a steady stream of small changes. The first step for anything we did not build is a review, from $500. Your own budget should cover platform fees, a person or team on call, and a reserve for the occasional larger fix.</p>

This post is for owners and operations leads who have an internal tool, a set of automations or an app built with Lovable, Bolt, Cursor or similar, and want to know what it should cost to keep it working. It covers what you are paying for, what pushes the cost up, how we price it, and how to set a budget.

> **The short answer.** Add up three lines. Platform fees, which you can read off your invoices. Someone's time to watch alerts, fix failures and make small changes, which depends on how many moving parts there are and how quickly they must respond. A reserve for the bigger fix that comes when an API is retired or the business changes. For a few automations, the time line can be tens of dollars a month. For an app that customers or staff use all day, plan for hundreds to low thousands.

## What you are paying for

Maintenance covers the work that keeps a system doing what it did on launch day, plus the small changes that keep it matching how the business works. In our [software maintenance service](/services/software-maintenance/) that means:

- Monitoring and error alerts on each workflow, app and integration
- Bug fixes, dependency and security updates
- Changes made when a platform or API you depend on changes
- Small feature changes from a monthly allowance
- Adding and removing users as people join and leave
- Checking backups on a schedule and keeping documentation current
- A monthly report of what broke, what was fixed and what changed

None of this is visible when it goes well, which is why it is often left out of the budget. It shows up when a customer email stops sending or a monthly report comes out empty.

## What drives the cost up or down

**How much the business relies on it.** An automation that copies form entries into a spreadsheet can fail for a day without much harm. One that sends invoices, books jobs or handles payroll cannot. The more a failure costs, the more checking and testing each change needs.

**Response time.** Next business day is cheap. Within the hour, every day, needs more people on rota, and costs more.

**Number of moving parts.** Each outside app is something that can change. Ten automations touching three apps are easier to keep than four touching twelve.

**How it was built.** Custom code needs dependency and security updates that no-code tools handle for you. Apps from AI builders often arrive without tests or documentation, so the first months cost more while that gets written. We cover the common gaps in [Is my Bolt.new app secure?](/blog/is-my-bolt-app-secure/), [Your Lovable app is probably public](/blog/your-lovable-app-is-probably-public/) and the [Cursor app security review](/blog/cursor-app-security-review/).

**Rate of change in the business.** If the team asks for a new field, report or rule every week, that is feature work. It belongs in the budget, and it is usually the biggest variable.

## Rules of thumb, and our view of them

You will often see an annual maintenance budget quoted as a percentage of what the software cost to build, commonly somewhere around 15 to 20 percent. We have not found a primary study behind that range that fits small business tools, so treat it as folklore. It also breaks down for AI-built apps, where the build may have cost very little and the maintenance does not shrink to match.

Our view, from pricing maintenance for tools built by other people, is that it is better to budget from the work. Count the automations, apps and integrations, decide what response time you need for each, and estimate how many small changes the team will ask for in a month. That gives a number you can check against invoices after a quarter.

## How SBD prices maintenance

These are the prices on our [software maintenance page](/services/software-maintenance/):

- **Takeover review, from $500.** Custom code and AI-built apps go through the [vibe-coded app audit](/vibe-coded-app-audit/). Automations and no-code tools go through the [Automation Audit](/services/audit/). You get a written report of what exists, what is fragile and what each fix costs.
- **Care plans, from $50 a month.** The starting price covers one or two automations. Plans go up with how much the business relies on the system and how fast you need a response.
- **Automation team, $999 a month.** For teams with a steady stream of small requests, worked through one at a time.
- **Larger work, fixed price.** A new module or a rebuild is quoted as a project before we start.

Takeover takes one to two weeks, then the plan runs monthly. Accounts, code and data stay in your company's name, and you can cancel with 30 days' notice.

## Setting a budget

This is the method we use, and you can run it yourself.

1. **List every system.** Each automation, app, integration and scheduled job, with the platforms it runs on.
2. **Read the platform fees.** Take them from invoices. Note any that are close to a plan limit, because the next tier is often a big step.
3. **Rate each system.** For each one, write what a day of failure would cost and how fast it must be fixed. Group them into "can wait a day", "same day" and "within the hour".
4. **Estimate change requests.** Ask the team how many small changes they asked for last quarter. That is a fair guide to next quarter.
5. **Add a reserve.** Keep money aside for the larger fix that comes when an app retires an API or the business changes a process. A few months of the care plan fee is a sensible starting point.
6. **Review after a quarter.** Compare the budget with what you spent, and adjust.

If the list shows systems nobody uses, switch them off. It is the cheapest maintenance there is.

## When maintenance costs more than replacement

Sometimes a system costs more to keep than to rebuild. Signs include the same failure coming back every month, fixes that break something else, and nobody able to change it without fear. A review should say so plainly, with a price for each option. We would rather recommend a rebuild than keep billing for a tool that keeps falling over.

If an automation is failing now, start with [fix broken automation](/services/fix-broken-automation/). If the original builder has gone, read [what to do when your developer leaves](/blog/developer-left-software-handover/) first. For what to check each month on automation platforms, see [who maintains a Zapier, Make or n8n setup after launch](/blog/maintaining-zapier-make-n8n-after-launch/).

## Questions we get asked

**Why does maintenance cost anything if the software already works?**

Because the apps around it keep changing. Logins expire, APIs change and limits run out, and someone has to notice and fix it.

**Is $50 a month enough?**

For one or two automations that do not need an urgent response, usually yes. Anything customers or staff depend on all day needs a larger plan.

**Can I pay per fix instead of monthly?**

You can, but nobody is watching between fixes, so problems are found later and cost more. A monthly plan pays for the watching.

**Do you charge for the first review if we then sign a care plan?**

The review is priced separately and starts at $500. It tells both of us what we are taking on before we quote the plan.

## Sources and further reading

- [Software maintenance and support](/services/software-maintenance/), SBD: care plans, Automation team, takeover review and what each covers
- [Vibe-coded app audit](/vibe-coded-app-audit/), SBD: the $500 review for custom code and AI-built apps
- [Automation Audit](/services/audit/), SBD: the $500 review for automations and no-code tools
