Think Build Implement Repeat
London, UK +44 7367 067226
WhatsApp FOLLOW f in X
Business Automation

Support and Maintenance After Launch

Last updated:

The failure that makes no noise

Automations rarely crash. They stop producing, or produce empty results, and nobody notices for weeks because the dashboard is green and no error was raised.

The most under-implemented alert in business automation is “this produced nothing today and it usually produces forty”. We build that one first.

What we monitor

  • Volume outside the expected range for that day of the week
  • Zero output where output is normal
  • Field completeness, so a format change upstream is caught the same day
  • Third-party integration health
  • Quarantine queue growth, with an owner who reviews it

Warranty, then maintenance

Ninety days of defect fixing after launch is included — behaviour that does not match what was agreed. After that, maintenance is optional and priced at 15–25% of build cost annually depending on how many third-party systems are involved.

Build costAnnual maintenanceWhat it covers
£10,000£1,500–£2,500Monitoring, dependency updates, defect fixes
£25,000£3,750–£6,250The above plus integration repairs
£50,000£7,500–£12,500The above plus a small change allowance

What counts as maintenance and what does not

Maintenance keeps it working as the world changes: security patches, dependency updates, repairs when a supplier alters their API. Development changes what it does.

We write the boundary into the agreement with examples, because almost every maintenance dispute in this industry comes down to that sentence being absent.

The annual review

  1. Does this still reflect how you actually work?
  2. Is the output still used by someone?
  3. Which exceptions are being handled manually that could now be automated?
  4. Has anything changed upstream that we have not accounted for?
  5. Should this still exist at all?

We have recommended switching automations off. A system that no longer serves a purpose still consumes maintenance and still occasionally fails.

Frequently asked questions

Do we have to take a maintenance contract?

No. For a simple self-contained automation, ad hoc support is often enough and we will say so. Anything with several integrations benefits from a standing arrangement.

Can our own team maintain it?

Yes, and the handover is built for that. Make sure someone owns dependency updates, which is the part most commonly neglected.

What response times do you offer?

Defined by severity and agreed in the contract, with what response means stated explicitly — acknowledgement, investigation started, or resolution.

What if we skip maintenance for a year?

Dependencies fall behind and catching up becomes a project rather than a routine task. Deferred maintenance is one of the reliable ways a working system becomes a rewrite.

Keep reading

Have automation running that nobody watches?

We review systems we did not build. A short check will tell you which could fail silently and what it would cost you.

Book a free 30-minute call Get a project estimate WhatsApp us

Related services

What we build for problems like this one

Business AutomationCustom Software Development