When an automation is quoted, attention goes to a single number: what the build costs. It is the figure you compare, and the wrong one to decide on: you keep paying for an automation while you use it, and the build is only the first instalment. This article explains what maintenance involves, how to estimate its costs before you sign, how to keep them down and who should take care of it.
Why does an automation need maintenance?
Because it depends on what never stands still: the online services it connects, the software it relies on and how your business works. Maintenance is the work of keeping it up to date and checking that it still does its job correctly.
It is tempting to see it as a machine you install and forget. In practice, the companies behind them revise their rules overnight, and apps release new versions that move a button, rename a field or alter a data format.
Your business evolves too: new rates, a new type of customer, another invoicing method. None of this comes with a warning.
A little out of line each month
Left alone, an automation drifts a little each month, until the day it gets something genuinely wrong. It is like a car that runs without servicing: fine, until it stops at the worst possible moment.
A typical example: an alert that stops arriving
Picture an online shop in Alicante with an automated workflow: each new order is logged in a spreadsheet and the owner gets an email alert. It works faultlessly for months. Then the email service it relies on adds a sign-in step for security. Nobody warns the shop: for everyone else, it is an improvement.
Orders keep landing in the spreadsheet, so everything looks fine. But the alerts have stopped, and the owner realises a fortnight later that no new order has been flagged since. Nothing actually broke: the world around it moved, and it stayed still.
The fix takes half an hour; the real cost is the two weeks nobody noticed. That is maintenance in one scene.
What does automation maintenance involve?
Automation maintenance covers six kinds of work: updates, monitoring, fixes, process adjustments, training, and security with backups. Part of it repairs what has broken; much of it checks that nothing is about to.
Where the work comes from
The work has three sources, and it helps to tell them apart:
- External changes: a connected service alters its terms, its sign-in method or its data format.
- Internal changes: a process, a rate or a form moves on, and the workflow no longer matches what your business needs.
- Cases nobody foresaw: the customer who types a phone number in the name field, the supplier who switches to a new invoice layout.
None of these sources disappears. They slow down once the system has bedded in, but they do not switch off.
The maintenance tasks, one by one
- Updates: when a tool or an integration between your systems gets a new version, the configuration has to follow.
- Monitoring: checking that each step runs and that every error alert reaches someone.
- Fixes: correcting errors and the odd cases that appear with use.
- Process adjustments: a new rate, form or service means editing the rules.
- Training: new staff need to understand what the automation does and what to do when it fails.
- Security and backups: reviewing who has access, changing passwords and keeping a copy of the configuration and the data.
Corrective and preventive maintenance
Corrective maintenance repairs what has failed; preventive maintenance stops it failing. A sensible plan combines both: a quick response when something breaks, and a regular check so that less goes wrong.
Going live is the start of upkeep, not the end of the work: monitoring and maintenance are the last of the steps of an automation project.
How to estimate maintenance costs before you sign
There is no standard range for upkeep, because the cost depends on your setup. You can still estimate it, and budget for it, from four facts you know before the project starts.
Four factors that set the cost
- How many pieces are involved: each connected system (your CRM, your invoicing software, your email) and each process in your company that depends on it is one more point that can change.
- How often your business moves: new rates, forms or services all mean editing the rules.
- How long a check takes: confirming that everything works, plus fixing whatever does not.
- Who does the work: you, your team or a provider. All three have a cost, even when nobody bills you.
Direct and indirect costs
Besides the initial investment, maintenance brings direct costs, such as the monthly subscription to each tool, and indirect costs, such as the management time you spend checking that everything is working. Upkeep is not a problem in itself; leaving it out of the calculation is.
These are the recurring costs to budget for:
| Recurring cost | What it covers | Paid in | What makes it grow |
|---|---|---|---|
| Subscriptions | Monthly plans for the automation platform, and for any connected app that only opens its integrations on a paid plan | Money | Usage, extra steps, more connected apps |
| Updates | Adapting the workflow when a connected tool releases a new version or alters its data format | Hours or fees | The number of connected apps |
| Monitoring | Checking that each run completes and that error alerts reach someone | Hours | How many workflows you have and how critical they are |
| Fixing time | Correcting errors and odd cases, and cleaning up the records they affected | Hours or fees | Messy data, unusual cases, rules nobody wrote down |
| Training | Showing new staff how the automation works and what to do if it fails | Hours | Turnover in the team |
| Security and backups | Reviewing logins, changing passwords, keeping a copy of the configuration and the data | Hours | How many people and accounts are involved |
Add these lines up over a year: that total, on top of the build, is the true automation cost. Compare it with the saving you expect: if upkeep eats the saving, the task is not worth automating. To put a figure on the saving, see our guide on how to calculate the cost of automating a process.
Pricing models for outside support
A provider can charge for support in different ways: a fixed monthly or yearly fee, an hourly rate or repair by repair. None of these pricing models is better in itself; what matters is a written scope: what is included, how quickly they respond and what counts as extra work. Request maintenance as a separate line on the quote.
Does upkeep depend on the technology?
Yes. A visual workflow, custom software and an AI step all need maintenance, but in different ways.
No-code platforms
Platforms such as Zapier, Make or Microsoft Power Automate connect your apps through ready-made integrations and a visual editor, with little or no programming. The vendor keeps the service running; the logic of your workflow is yours, and when a connected app updates its interface or its data format, a step can fail.
If you create these workflows yourself, our guide to automating without coding explains how far you can go alone.
Custom software
With custom development, a developer writes a program that connects your business systems directly. There are fewer subscriptions, but hosting, security updates and adjustments remain. The main risk is depending on a single person: make sure you receive the source code, the logins and brief documentation.
Automations that use AI
If the automation uses artificial intelligence (AI), maintenance involves one more step: reviewing what the AI produces. AI tools can change their behaviour when the provider updates the underlying model, and an AI step interprets its input, so it can be wrong in ways that look plausible: a reply to a customer message, a summary of documents, the category given to a request.
Decide who reviews the output, how often and what to do when the AI gets it wrong; it does not take a high technical level, just someone who knows the process and checks a sample regularly. If personal data is involved, remember that under the GDPR, which applies in Spain, you remain accountable for the data you send to the service.
The trap of small automations
Small tasks are where forgetting maintenance can hurt. An automation that saves you ten minutes a month seems a good idea, until you add the few minutes of checking it needs now and then. The net gain shrinks, and sometimes it vanishes.
The smaller the task, the more upkeep weighs on its balance, because upkeep costs do not fall in proportion to the value the automation brings to your business. It can be cheap to build and still cost more to keep than it saves. For those tasks, a simple checklist kept by hand can beat it. Before automating anything, decide which tasks to automate first.
The silent failure: the risk that gives no warning
There is a cost worse than regular upkeep: the failure that gives no warning. An automation that stops outright gets noticed. One that keeps going while getting things wrong can disrupt your daily operations for weeks, for example by:
- sending an invoice with the wrong amount;
- leaving out one customer in ten;
- chasing a payment that has already been made;
- creating duplicate records in your CRM.
Maintenance is therefore not only repairing what breaks: it is checking that what still works does so correctly. A well-built workflow should include a way of raising an alert when something goes wrong.
How to catch a silent failure early
- Send error alerts to someone by name, not to an inbox nobody reads.
- Compare totals now and then: orders received against alerts sent, invoices issued against payments recorded.
- Look at a sample of results every week or month.
- Run a test case after every update to a connected tool.
How to reduce maintenance costs
Much of tomorrow's upkeep is decided at the design stage. These decisions keep it low:
- Simplify the process before automating it: what you remove never has to be maintained.
- Start with one piece, and add another only when the first one works: a chain of many steps across several apps has more links that can fail.
- Choose proven tools, starting with your existing ones, and as few as you can: an off-the-shelf tool is updated by its vendor; custom code is yours to update.
- Write brief documentation: one page with the steps, the rules and whom to contact, so that nothing depends on anyone's memory.
- Test with real data before going live, odd cases included.
- Put a preventive review in the calendar: a short audit to check that everything still behaves as it should.
Who should look after it: you, your team or a provider?
Someone has to be in charge of it, whether an internal member of the team or an outside provider. Deciding who from the start matters as much as deciding what gets automated.
If you set it up yourself
If you built it yourself with a visual tool, the maintenance is yours too. Be honest about what that means: being available when something drifts, knowing where to look and fixing it without breaking something else.
For simple automations, it is perfectly manageable: keep a note of what each workflow does, and read the error notifications your tool sends.
If a provider did the build
If you outsourced the build, it makes sense to outsource support as well, with its scope in writing: what it covers, how quickly they respond, who receives the error alerts and what it costs per year. With custom development, also check that another developer could take over from the documentation.
The no man's land to avoid
The one thing that never works is the no man's land: an automation set up by someone who has left, that nobody maintains, and that keeps going until the day it fails with nobody to call.
Warning signs that it is time for a review
These signs call for a closer look:
- Alerts or automatic emails stop arriving.
- Duplicated, incomplete or oddly formatted data appears.
- The same error comes back week after week.
- Nobody can explain what the automation does or how to fix it.
- One of the connected tools has released a new version or revised its terms.
- The person who set it up has left or no longer replies.
If you recognise two or more, review it within days, before your customers notice.
What to ask before signing a quote
Before accepting any automation quote, find out what comes after go-live. A serious provider has a clear answer to each of these points; one who only talks about the build is selling you half the story.
- Who takes care of it once it is live?
- How much time or money does maintenance represent per year?
- What do you do the day a connected service revises its rules?
- What is in the scope of support, and how quickly do you respond?
- Who receives the error alerts, and where is the documentation kept?
Asking does not complicate the decision; it makes it honest, because it turns a quoted price into a real cost. Forgetting upkeep also features in our guide to automation mistakes worth avoiding.
Maintenance is not bad news: it is a reality better known before than after. An automation can still pay off for your business once upkeep is included in the starting calculation. That is what our free diagnostic is for: it puts a figure on a task in about two minutes, then, with six more answers, it works out the payback, taking into account what it will cost to keep running, not just to build, with the result on screen and no commitment.