Think Build Implement Repeat
London, UK +44 7367 067226
WhatsApp FOLLOW f in X
  1. Home
  2. Blog
  3. What Makes an Automation Last
Business Automation

What Makes an Automation Last

Keeping business automation working for years: a named owner, monitoring for silent failure, configuration over hard-coded rules and usable documentation.

Updated 2 min readBy SpiderHunts Technologies

Free estimateNo obligation

Get a free estimate

Tell us what you need. A senior engineer reads every enquiry.

Takes under a minute. We never share your details.

  • Free consultation
  • No commitment
  • NDA on request

Prefer to talk? Book a free 30-minute call →

Quick answer — TL;DR

Longevity comes from four things: an owner in the business, monitoring that catches silent failure, configuration rather than hard-coded rules, and documentation good enough for someone else. None of them are technically difficult and all four are commonly skipped.

Systems do not fail, they drift

Automations rarely stop working outright. The business changes around them, a supplier alters a format, thresholds set two years ago stop matching reality, and gradually people work around the system instead of through it.

The tell is a parallel spreadsheet appearing. That is the leading indicator of abandonment.

1. An owner in the business

Not who maintains the code — who owns the outcome. Someone who notices when it drifts, decides on changes and answers questions about what it should do.

Unowned automations run for years after they stopped being useful, or stop being useful without anybody deciding. Naming the owner before the build is the cheapest longevity measure available.

2. Monitoring for absence

Alert when volume falls outside the expected range, when output is zero and normally is not, when field completeness drops, when a run finishes suspiciously quickly.

Errors get noticed. Silence does not, and silence is the failure mode that costs weeks.

3. Configuration over code

  • Thresholds and tolerances editable by your team
  • Routing and approval chains changed without a deployment
  • New categories, sites and product types added without us
  • Business rules that are likely to move kept out of code

The test at design time: which of these will you plausibly want to change in two years? Those go in configuration.

4. Documentation someone will use

Not a manual. A one-page architecture sketch, the deployment process tested by someone following it, the dependency list, and the decision records explaining why it is like that.

Decision records are the highest-value documentation a project produces and the cheapest to write — a paragraph at the time, ten minutes, and it prevents the same argument recurring every four months.

The annual review

Once a year: does this match how you work now, is the output still used, what manual exceptions could now be automated, has anything changed upstream, and should this still exist.

Two hours. It is the difference between a system that compounds and one that quietly becomes a liability.

FAQ

Frequently asked questions

The questions readers ask us after this guide.

Still have a question?

Ask us directly — a senior engineer will get back to you.

Ask about your project

How often do automations need attention?

Ones connecting to third-party systems, a few times a year. Self-contained ones can run untouched for years. The number of integrations is the best predictor.

What if the person who built it leaves?

That is what the documentation and the named business owner protect against. Without them, the first failure becomes an investigation rather than a fix.

Should we rebuild old automations?

Only if they are failing frequently or blocking something. Working automation that is unfashionable is still working automation.

What does the annual review cost?

It is included in maintenance agreements. Without one, it is a couple of hours of our time and worth considerably more than that.

Keep reading

More on Business Automation

Start here

Have automation running that nobody owns?

That is the strongest predictor of it quietly dying. Happy to review what you have and what it needs.

  1. You tell us what you needTwo minutes on the form, or a message on WhatsApp.
  2. A senior engineer reviews itAnd comes back with questions, a realistic range and an honest view on fit.
  3. Free 30-minute scoping callWe talk through scope, options and a realistic estimate — with no obligation.
Free estimateNo obligation

Talk to someone who builds this

Send a short brief and we will come back with an honest view and a realistic range.

Takes under a minute. We never share your details.

  • Free consultation
  • No commitment
  • NDA on request

Prefer to talk? Book a free 30-minute call →