Operations

What your automation costs to run

Automated things fail quietly, and metered things grow quietly. Both are invisible until someone counts.

Anything that takes orders or moves money is a revenue-carrying system, and it inherits the obligations of one. Three questions decide whether you actually have it: does it stay up, can you get it back, and what does it cost to run. Most small firms answer the first, assume the second, and never ask the third.

Failure is quiet

When a person forgets a task, something visibly does not happen. When an automated routine stops, everything looks normal — the output is missing, but nobody is standing where the output used to be.

The most common version of this is a job that is monitored for the wrong thing: the check confirms it started, not that it finished. A routine can be dead for days under a green light. Two rules cover most of it — confirm completion, never initiation, and make the failure loud, arriving somewhere a human already looks.

An untested backup is a belief

The second question is the one people answer with confidence they have not earned. A backup you have never restored from is not a copy; it is an assumption. Restore one, once, on purpose. It is a bad afternoon at a time you choose, instead of a catastrophic one at a time you do not.

Put a ceiling on anything metered

Then do the arithmetic once for the whole system: what a month costs to host, to back up, and to run. A revenue system with a known running cost is an asset you can reason about. One without is a liability you have not met yet.