How to prioritise business automation opportunities
A practical method for finding repetitive business processes worth automating before selecting a platform, workflow tool or AI solution.
· Practical guide · ZeroFoldThe best automation candidate is rarely the task people complain about most. It is the process where repeated effort, delay and error combine with enough stability to make automation dependable.
Build an opportunity list from observed work.
Ask teams where information is copied, reconciled, chased, reformatted or re-entered. Look for recurring approvals, document handling, notifications, customer handoffs and reporting. Capture the real path—including exceptions—not the policy version of the process.
Record the systems involved, volume, average effort, waiting time, error rate, rework and consequence of failure. These measures turn a vague “we should automate this” into a comparable opportunity.
Score candidates on value and readiness.
Frequency
How often does the work occur and how many people touch it?
Friction
How much effort, waiting, rework and customer frustration does it create?
Stability
Are the rules and inputs understood, or does every case require new judgement?
Consequence
What happens when the automation is wrong, late or unavailable?
High-value, high-readiness candidates should enter the first wave. High-value but unstable processes need redesign or better data first. Low-value work should not be automated merely because a tool makes it possible.
Choose the lightest reliable intervention.
| Intervention | Use it when | Example |
|---|---|---|
| Remove | The step exists by habit and no longer protects a real decision. | Duplicate approval with no distinct authority. |
| Standardise | The process varies because inputs and ownership are unclear. | One intake form and a defined triage owner. |
| Configure | An existing platform already contains the required workflow. | CRM stages, permissions and notifications. |
| Integrate | Systems work but information does not move between them. | Approved sale creates finance and delivery records. |
| Build | The workflow is important and cannot be supported cleanly by the stack. | A controlled operational case-management system. |
Define success before selecting the technology.
- Name the process owner and the people affected.
- Set a baseline for time, delay, error, cost or throughput.
- List common exceptions and the cases that must stop for human review.
- Confirm source-of-truth systems, permissions and audit requirements.
- Start with a controlled workflow and measure the result before expanding.
Use AI where inputs are unstructured or classification and drafting create value, but place evaluation, confidence thresholds and human review around consequential decisions. A deterministic workflow is often the better tool for known rules.