What to automate first: a ranking method for small teams
Automation pays back fastest when you start in the right place. A simple way to rank the candidates, and the three automations that come first for almost everyone.
Ask a team what takes their time and they will name the hard problems. Watch the same team for a week and you will see something else entirely: chasing, reminding, re-typing, reconciling, reporting. The work between the work. It is invisible because everyone does a little of it, and enormous because everyone does a little of it every day.
That is what automation is for. Not the judgement calls, which stay with people, but the routine that surrounds them. The question is where to start, because the first automation sets the tone: if it saves real hours in the first month, the team asks for the next one; if it is a clever thing nobody needed, they go back to the spreadsheet.
The ranking
For each candidate, score three things:
How often it happens. Daily beats weekly beats monthly. A five-minute task done fifty times a week is four hours.
How many people do it. A task that every person on the team does a little of is worth more than one that a single person does a lot of, because you are removing a habit, not a job.
How little judgement it needs. If the task is “look at this and decide”, it is not an automation candidate yet. If it is “when this happens, do that”, it is.
Multiply them, roughly. The top of the list is almost never the most interesting item. It is the reminder, the report, or the hand-off. Build that first.
The three that come first for almost everyone
Reminders and confirmations. Payment due, appointment tomorrow, document missing, renewal coming. Someone is sending these by hand, usually from a spreadsheet, usually late. Sent automatically from the system through the channel the customer actually reads, they stop being a task and start being reliable. This is the single fastest payback we see.
The Monday report. Somebody spends a morning assembling numbers from three or four places into a report that leadership reads for five minutes. Produced automatically and sent before anyone asks, it saves the morning and, more importantly, it is the same every week, which means people start trusting it.
The hand-off between two tools. A customer added in one place typed into another. An order confirmed becoming an invoice raised. A payment received marked against the invoice. Each of these is a minute and a chance for the two systems to disagree. Connect them once and the minute and the disagreement both disappear.
What to leave for later
Anything that needs a decision. Automate around the decision, not through it. Gather the information, present it clearly, hand it to a person, record what they chose. Then, once you have seen a few hundred decisions, you may find that eighty percent of them follow a rule, and that rule can be automated with the rest still going to a person.
Anything that happens rarely. The annual process is not worth automating until the weekly ones are done, and by then it may have changed.
Anything the team is still arguing about. If two people do the task differently and both think they are right, an automation will freeze one of them into policy. Settle the process first.
The rules that keep automation trustworthy
Every automation we build has three things: a log a person can read, a switch that pauses it, and a hand-off for the cases it is not sure about. Automation that hides its exceptions turns small problems into big ones a month later. Automation that shows its work gets trusted, and trusted automation gets extended.
Do you need AI for this?
Usually not. Rules, schedules and integrations do the job reliably and cheaply. AI earns its place where the input is messy: reading a voice note, a photo of a form, a rambling chat message. Use it there, with a person confirming anything that matters, and use rules everywhere else. Starting with AI is how automation projects become expensive demos.
How to begin
Map a typical week. Who does what, where the same information is touched twice, what gets chased. Rank the candidates with the three questions above. Build the top one and measure the hours that come back. Then build the next.
If you would like a second pair of eyes on the ranking, write to us. It is the kind of conversation we enjoy, and it is usually short.