Workflow Automation: Which Business Process Should You Automate First?

Workflow Automation: Which Business Process Should You Automate First?

Automate first the process that happens often, follows the same rules every time, starts from data that is already digital and is cheap to correct when something goes wrong. For most small and mid-sized businesses that means moving data between systems – enquiries into the CRM, paid orders into invoices, orders into courier waybills – plus reminders and routine reports. Leave for later the processes that are still changing, depend on judgment, or where a mistake is expensive or affects people's rights. And fix the process before you automate it: an automated mess is just a faster mess.

What makes a process a good first candidate

Google's Site Reliability Engineering book has a useful name for the kind of work worth automating: "toil". It defines toil as work that tends to be manual, repetitive, automatable and tactical, that has no enduring value, and that scales linearly as a service grows. Translated into business terms, look for tasks that:

  • are repeated – the same steps many times a week;
  • a machine could do just as well – they need rules, not judgment;
  • leave nothing improved – when the task is done, the business is in the same state as before, the data just sits in one more place;
  • grow with the business – twice the orders means twice the copying.

The same book is careful to say that toil is not always bad: it is fine in small doses and becomes a problem in large quantities. A task that takes five minutes twice a month is rarely the place to start.

Score your candidates

List the routine tasks in the business and rate each one on a few simple questions. The table below is an illustration – your own list will look different:

ProcessHow oftenRules stable?Cost of a mistakeVerdict
Copying website enquiries into the CRMDailyYesLow – easy to spot and fixGood first candidate
Creating invoices for paid online ordersDailyYesMedium – VAT and numbering must be rightGood candidate, with a check
Creating courier waybillsDailyMostlyMedium – a wrong address costs a deliveryGood candidate
Monthly sales reportMonthlyYesLowWorth it if it takes hours
Approving special discountsWeeklyNo – depends on the customerHighKeep a person; automate only the request
Answering complaintsVariesNoHighAutomate the routing, not the answer

The best first projects usually sit at the top of a table like this: frequent, stable and forgiving.

Do the arithmetic – but not only the arithmetic

A rough calculation helps: how many times a month the task happens, how many minutes it takes, and how long you expect to keep doing it. Compare that with the cost of building the automation, running it, and adjusting it when the connected systems change. If a task takes two minutes a week, almost any automation will cost more than it saves.

Time is not the only benefit, though. The Google SRE book lists consistency (a person doing a task hundreds of times will not do it the same way every time), faster reaction, and "decoupling operator from operation" – once something is automated, anyone can run it, not just the one person who knows how. It also admits that engineers often waver over whether a particular piece of automation is worth writing. For a small business, consistency and not depending on one person can matter as much as the minutes saved: an invoice that is never forgotten, an enquiry that never sits unanswered in someone's inbox.

Fix the process before automating it

  1. Write down the steps as they really happen, not as they are supposed to happen. Ask the people who do the work.
  2. List the exceptions. "Except for companies", "except orders above a certain amount", "except when the customer pays on delivery". Each exception is either a rule the automation must handle or a reason to keep a person involved.
  3. Remove steps that don't need to exist. Sometimes the best automation is deleting a step: a report nobody reads, an approval nobody ever refuses.
  4. Standardise the input. A form with required fields can be automated; free-text emails mostly cannot.
  5. Name an owner for the automated process – someone has to notice when it stops working.

Keep a person in the loop where it matters

Automation repeats mistakes as reliably as it repeats correct work. The Google SRE book warns that doing automation thoughtlessly can create as many problems as it solves, and describes a case where a bug in an automated disk-erasing tool wiped the disks of all machines in Google's own content delivery network. Your invoicing script will not be that dramatic, but the lesson scales down: build in limits ("if more than 50 records would change, stop and ask"), log what was done, and make actions reversible wherever possible.

There is also a legal side when decisions affect people. Article 22 of the GDPR gives people the right not to be subject to a decision based solely on automated processing, including profiling, which produces legal effects concerning them or similarly significantly affects them. Where one of the exceptions applies, the organisation must still provide at least the right to obtain human intervention, to express their point of view and to contest the decision. If you plan to automate decisions such as approving applications or credit, get legal advice first.

Three patterns that keep people in control:

  • The system prepares, a person approves. A draft invoice or a draft reply waits for one click.
  • Normal cases run automatically, exceptions go to a queue. A person sees only what the rules could not handle.
  • A daily summary of what the automation did, so problems are noticed within a day rather than at the end of the quarter.

Good first candidates for most businesses

  • Website enquiries going straight into the CRM, with the source page and an automatic acknowledgement to the customer.
  • Paid orders creating invoices – or invoice drafts – in the accounting software.
  • Orders creating courier waybills, with the tracking number sent to the customer.
  • Reminders: unpaid invoices, contract renewals, appointments, expiring documents.
  • Recurring reports built from data the systems already hold.
  • Importing supplier price lists and stock from files or feeds. Our product search engine gega.bg brings in around 2.7 million products from the feeds of affiliate networks such as ProfitShare and CJ; at that scale, doing it by hand is simply not an option.

If much of this currently lives in spreadsheets, read when has your business outgrown spreadsheets; many of these automations become far easier once the data sits in one system.

Usually not the place to start

  • Processes that still change every few weeks – you would be rebuilding the automation each time.
  • Rare tasks, unless they are error-prone and the errors are costly.
  • Work that depends on judgment, negotiation or tact.
  • Actions that are expensive or impossible to undo: payments, deletions, messages to all customers.
  • A chain across five systems at once. Connect two, prove that it works, then add the next.

Built-in features, integration platforms or custom code

Check first what the software you already pay for can do: many CRM, shop and accounting systems include rules, notifications and imports that cover simple cases. Integration platforms that connect popular services without programming suit simple, low-volume flows. Custom code makes sense when the process is central to the business, the volume is high, the systems have no ready connectors, or you need full control over errors and data. The trade-offs between building and subscribing are covered in custom software vs SaaS: comparing total costs over three years.

After launch: measure and watch

  • Note how long the task took before, so you can see whether the automation actually helped.
  • Keep a log and an error list, and name the person who checks them.
  • Review the exceptions every month – if the same exception keeps appearing, it may deserve its own rule.
  • Revisit the automation when the business changes: new products, prices, payment methods or partners can quietly make an old rule wrong.

Not sure which process to start with? We can go through your routine tasks with you, estimate which automations are worth building and connect the systems involved as part of our web-based software development work. Contact us with a short description of the process that takes up most of your team's time.

Sources

← All articles

Have an idea for a website, app or system?

Tell us briefly what you need – we will get back to you for a short call and a clear quote.