A good first automation starts with a repeated operational problem, a clear trigger and a result your team can measure. It rarely starts with a tool. Teams that pick the software first often end up automating a process nobody would have designed on purpose.
Here is the approach we use when a business asks where to begin.
Find repeated effort
Ask where information is copied between systems, or where routine handoffs slow the team down. Typical examples:
- An enquiry arrives by email and someone retypes it into a spreadsheet or CRM.
- An invoice is created by hand from details that already exist in a project record.
- A weekly report is assembled by exporting data from three places and pasting it together.
Before automating, simplify. If a step exists only because "we have always done it", remove it first. Automating an unnecessary step makes it harder to remove later.
Choose a manageable pilot
Not every repeated task is a good first candidate. Compare a few options against these questions:
- Frequency: how often does it happen? Daily work pays back faster than a quarterly task.
- Hands-on time: how long does each run take a person?
- Stable rules: can you describe the decision in a few sentences, or does it change every week?
- System access: do the tools involved have reliable APIs or exports?
- Impact of mistakes: if the automation gets one run wrong, can you notice and fix it easily?
Begin with a workflow whose failures can be recovered. Sending an internal notification to the wrong channel is an inconvenience. Sending a customer the wrong invoice is a problem.
Map the whole journey
Write down the workflow from trigger to result, including the uncomfortable parts:
- What information is required, and what happens when it is missing?
- How are duplicates handled if the same enquiry arrives twice?
- Who owns the workflow when something goes wrong?
- Where do exceptions go? Every automation needs a queue for the cases it cannot handle.
Failed integrations should stay visible and be safe to retry. A workflow that fails silently is worse than no workflow, because people stop checking.
Keep important decisions explicit
Use plain rules for predictable actions: "if the form says UK and the budget is above a threshold, assign it to this person". Rules are easy to test and easy to explain.
Where AI helps with unstructured information, such as summarising an email or extracting details from a document, test its outputs on real examples before relying on it. Keep human review for consequential commitments: prices, contracts, refunds and anything a customer will treat as a promise.
Plan for failures
Give the workflow:
- An owner who is told when it breaks.
- Activity records that show what ran, when and with what result.
- Alerts for failures, not just a log nobody reads.
- Appropriate access, using a dedicated account with only the permissions it needs.
- A manual fallback, so the team knows how to do the job by hand if the automation is switched off.
Measure and improve
Agree before you start what "better" means. Usually it is some combination of time saved, fewer errors, less waiting and the effort needed to keep the automation running.
Review those numbers with the people using the workflow after a few weeks. If it works, extend it carefully. If it does not, the pilot was small enough that you have learned something without much cost.
If you have a process in mind and want a second opinion on whether it is a good first candidate, send us a short description.