ContactBook a call

Costs

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.

Cover for “Software maintenance cost for tools and AI-built apps”, with the line: Budget by how much the business relies on the system, and how fast you need it fixed.
Budget by how much the business relies on the system, and how fast you need it fixed. Image: SBD.

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.

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 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?, Your Lovable app is probably public and the 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:

  • Takeover review, from $500. Custom code and AI-built apps go through the vibe-coded app audit. Automations and no-code tools go through the Automation 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. If the original builder has gone, read what to do when your developer leaves first. For what to check each month on automation platforms, see who maintains a Zapier, Make or n8n setup 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
  • Pricing
  • Vibe coding

Keep reading

Cover for “What to do when your developer leaves”, with the line: Get the accounts into your company’s name first, then work out how the system runs.

Operations

What to do when your developer leaves

Your developer or agency has gone and the software still runs the business. How to get access back, move accounts into your name and hand the system over.

Cover for “Who maintains a Zapier, Make or n8n setup after launch”, with the line: Automations rarely fail loudly, so someone has to be told when they stop.

Operations

Who maintains a Zapier, Make or n8n setup after launch

Automations break after launch when apps change their APIs, logins expire or task limits run out. What to check each month, and who should own it.

Cover for “Cursor app security review: what to check”, with the line: Review the app, the packages it pulled in, and the files that tell the editor what to do.

Security

Cursor app security review: what to check

Reviewing an app built with Cursor: secrets in the repo, auth on API routes, hallucinated packages, rules file and MCP injection, and the 2025 Cursor CVEs.

Find out what is worth automating

About 95% of AI pilots never reach the profit line. We start with the work your team still does by hand and measure each build by the hours it saves.

See how we work

Cookie preferences

Choose what this site may use on your device. You can change this at any time from “Cookie settings” in the footer.

Strictly necessary

Keep the site working and remember the choices you make here. These cannot be switched off, and none of them track you.

Always on
What this includes (4)
NameProvider PurposeDuration
sbd-consentThis site Remembers your cookie choices12 months
Vercel Web AnalyticsVercel Inc. Counts page views in aggregate. Sets no cookie and stores nothing on your deviceNone
ticker-dismissed, sbd-note-offThis site Remembers that you closed a notice or language tipUntil the tab closes
sbd-voice-resume, sbd-voice-prefillThis site Carries a voice conversation across pages, only if you start oneUntil the tab closes

Analytics

Tell us which pages are read and where visitors leave, so we can improve them. IP addresses are anonymised and nothing is used for advertising.

What this includes (2)
NameProvider PurposeDuration
_gaGoogle Analytics (Google LLC) Distinguishes visitors with a random ID13 months
_ga_FPXDMQPRV1Google Analytics (Google LLC) Keeps the session state for this site13 months

Functional

Embedded services that set their own cookies. Without them the site still works; you get a link to open the service instead.

What this includes (1)
NameProvider PurposeDuration
Booking calendarCal.com Inc. Shows live availability and books the call on the booking pageSet by Cal.com

Advertising

Not used. This site has no advertising, retargeting or social media tracking, and we never sell data.

Not used

Questions about your data: hello@smallbaydigital.com