You automated the appointment reminders and it works. Fewer no-shows, nobody retypes anything, Monday morning is quieter. So the next idea arrives quickly: let's automate the quotes as well. Hold on a moment.

Automation is not free. Every rule you set up is a small piece of machinery that someone has to understand, maintain and switch off when the business changes. In our experience, the companies that get the most out of automation are not the ones with the most automations, but the ones that chose them well.

Automate the typing, not the deciding

Almost every office task is two things mixed together: moving information around, and judging what to do with it. Copying an order out of an email into your system is moving. Deciding whether this customer gets a discount is judging.

Software is excellent at the first and weak at the second. The trouble starts when a tool quietly does both. An automatic reply that attaches your price list is fine. An automatic reply that quotes a price is a promise you never read.

Four signs to leave it alone

It happens a few times a month

Five minutes, four times a month, is twenty minutes. The first time your supplier changes a form, repairing the rule will cost you more than the rule saves you that year. Volume is the first question, not irritation.

The exception is the job

If every case genuinely needs a look — every quote a different site visit, every invoice a different agreement — you are not automating a task, you are trying to write down your own judgement. That work never finishes.

A mistake stays invisible

A broken reminder is obvious: someone phones the same day. A rule that files invoices under the wrong category is silent for three months, and then it is your accountant's problem and yours. Tasks whose output you do not see daily deserve more caution.

Someone is upset, or money is late

A complaint, a message of condolence, a first payment reminder to a customer who has always paid on time — those are two minutes of attention that buy more than any workflow. Send those yourself.

Never automate a process you cannot write down

A simple test: describe the task in ten lines, step by step, including what happens when a field is empty. If you cannot, the computer cannot either. What you get instead is a faster version of the mess, and one that hides where it goes wrong.

The same applies to rules that change often. Seasonal prices, shifting surcharges, per-customer agreements: if the rule is different every two months, you pay for a change every two months. Wait until it settles.

The middle option: prepare, don't send

Most tasks that fail the tests above still have a half that automates beautifully. The system collects, fills in, sorts and attaches. A person looks at it and presses send.

Concretely: the quote is ready with the customer's details and last time's prices, you type in the figure. On Monday morning a short list waits with every invoice past thirty days, you choose who gets a call. Photos from the engineer's phone land in the right job folder, and a person writes the report.

That way you keep the minutes and drop the risk. It is almost always the cheapest thing to build, and the easiest to extend later if it turns out the final step can safely be automatic after all.

What to do this week

  • Take your list of things you wanted to automate and write next to each one how often it happens per month. Anything under five times goes to the bottom.
  • Pick one task from that list and try to write it out in ten lines. If you cannot manage it in fifteen minutes, the task is not ready to be automated.
  • Go through the automations you already have and ask of each: would I notice within a day if this quietly stopped? Where the answer is no, add a simple check, such as a weekly summary email.

At ITSysPro we usually start an automation conversation by asking which tasks you should deliberately leave alone. If you would like to go through your own list together, we are happy to talk it over.