Removing the work, not relocating it
Business automation is removing repeated manual work from a business so it happens reliably without someone remembering to do it. The useful test is not whether a tool was installed. It is whether the number of things a person has to remember went down. A great deal of what gets sold as automation simply moves a task to a different screen.
By Jayden Forshee ·
Rank candidates on three properties and start at the top. High frequency, low judgement, high cost of failure.
| Task | Frequency | Judgement | Cost of missing it | Automate? |
|---|---|---|---|---|
| Responding to a new enquiry | Constant | Low | A lost job | First |
| Appointment reminders | Constant | None | A no-show | Yes |
| Review requests after a job | Constant | None | Compounding lost reputation | Yes |
| Follow-up on quiet leads | Constant | Low | Pipeline quietly dies | Yes |
| Quoting a complex job | Regular | High | Mispriced work | Assist, don't automate |
| Handling a complaint | Occasional | High | A lost customer, publicly | No |
Three questions. Does it run when nobody is watching — at 2am, on a Sunday, during your busiest week? Does it fail loudly, or does a failure look identical to success? And has anyone's task list actually got shorter?
That middle question is the one that catches the most expensive mistakes. A messaging system that cannot deliver still shows "sent". A form that stops posting produces no error — just a quiet week. Silent failure is the characteristic failure mode of automation, which is why anything installed should also be instrumented.
Less in software than in trust. A business that automates review requests and accidentally sends four to the same customer has spent real reputation on a configuration error. A follow-up sequence that keeps texting someone who asked it to stop is a compliance problem, not just an annoyance.
Which is why every install should define, before launch: what happens on failure, who is alerted, and what the customer sees in the worst case.
Custom Software — business automation and internal systems. Built when the off-the-shelf answer does not exist, and instrumented so failures are visible rather than silent.
Where the work is customer-facing rather than internal, it usually belongs in lead response automation or CRM automation instead.
Removing repeated manual work so it happens reliably without someone remembering to do it. The test is whether the number of things a person must remember went down — not whether a tool was installed.
Tasks that are high frequency, low judgement and expensive to miss: responding to new enquiries, appointment reminders, review requests and follow-up on quiet leads. Quoting and complaints need a person.
Silent failure. A messaging system that cannot deliver still reports "sent"; a form that stops posting produces no error, just a quiet week. Anything automated should also be instrumented so failure is visible.