OneAIAgency Book a 15-minute call

Notes · Automation · 3 min read

Signs a task is worth automating (and signs it isn't)

Repetition is the obvious signal, but it's not enough on its own. Here's what we look for.

Good candidates:

  • It happens every week, not once a quarter.
  • It follows rules someone could write down.
  • It moves information from one system to another.
  • Mistakes in it cost money, like work that never gets billed.
  • The person doing it would happily never do it again.

Poor candidates:

  • It needs judgement that changes case by case.
  • Nobody agrees on how it should be done yet. Automating an undefined process just makes the confusion faster.
  • It happens a few times a year. The build will cost more than the time it saves.
  • The real problem is a habit, like time that never gets logged. Software can make the habit easier, but it can't create it.

The last one comes up more than you'd expect. When an audit finds a habit problem, the readout says so plainly, and the recommendation is usually a small process change first, with a build only if the change sticks.

Written by Alex Ibrahim, who runs every audit and writes every build.

Book a 15-minute call