Daily work includes copying data, checking portals and updating documents. These tasks are necessary. They can also consume time from professionals who must calculate, review and decide. Measure the tasks before choosing what to automate.
Starting with too many processes makes results difficult to verify. Choosing the wrong first process can make a project unviable, even if the technology works. Technical problems, data and team adoption also matter.
The criterion: three questions per process
Before talking about tools, draw up a list of candidates and put each one through three filters:
- Frequency. How often does the process run each month? Multiply savings per run by the number of runs. Compare the result with build and maintenance costs. An infrequent process can still justify automation if each run is expensive.
- Clear rules. Can you describe inputs, rules and exceptions? That description supports a feasibility assessment, but does not guarantee feasibility. Decisions without sufficient rules need further definition or human review.
- The cost of an error. What happens if the result is wrong? Automation can reduce transcription errors. It can also repeat a design error at scale. Standards-based calculations and bids need tests, traceability and review proportionate to the risk.
Choose a focused first process with clear rules, measurable benefits and manageable risk. Candidates include the generation of repetitive documents, the calculations that live in legacy spreadsheets, reading and classifying incoming information (emails, orders, documentation) and moving data between the ERP and everything else. You’ll find how we approach them in process automation.
What not to automate yet
First clarify processes with unclear responsibilities, rules or inputs. Automation does not correct those gaps. Keep human review where a decision needs professional judgment. For example, software can prepare a bid or compare tenders. The responsible person must approve the bid or choose which tender to enter.
How to know whether it worked
Before building, measure monthly hours and process errors or rework. Record the workload and observation period. Repeat the measurement under comparable conditions. This helps distinguish an improvement from fewer orders or simpler tasks. Include review and maintenance time in the comparison.
The mistake of starting big
Start with a focused delivery and a before-and-after comparison. If the result justifies further work, assess the next process. Use what you learned, but review costs and risks again. At Sertoria, each phase has a fixed price before we start. We also agree the scope, timeline and acceptance criterion.