Most automation advice starts with clean processes, documented workflows, and structured data. Many companies have none of those things when the conversation begins.
At one company, information lived in inboxes and supplier data was scattered across files that did not agree with each other. Purchase orders were created, logged, and filed manually. File names depended on whoever happened to upload the document. When an experienced employee left, part of the process left with them.
The written procedure did not explain how the work got done. The invoice process was a better example: someone received a PDF, typed its data into a spreadsheet, saved the document in a shared folder, and hoped another person could find it later. There was no reliable naming standard, duplicate check, or audit trail.
That description sounds basic, but it gives you what a business case needs. How many hours does the task consume each week? What do errors cost to correct? What stops when the only person who understands the process is unavailable? Those questions are easier to defend than a broad promise about digital transformation.
The awkward part is data. Automation needs cleaner inputs, cleaning the inputs needs time, and time needs a budget. Waiting for a perfect data foundation can keep the project stuck forever.
I prefer to start with one process that has predictable inputs and visible pain. It does not need to be the most important process. It needs to be narrow enough to fix and common enough for people to notice.
The first tool I built in that environment was a PO Automator. Supplier offers varied in layout but contained a familiar set of fields. The tool read the offer, extracted those fields, and prepared a structured form for review. The first version made mistakes. Users pointed them out, and the extraction rules improved.
Within a few months, purchase-order creation fell from about 15 minutes to about 3 minutes. That result was easier to discuss than a forecast. The people doing the work could compare the old process with the new one.
Only then did the wider problem become worth solving. Supplier records had to remain consistent across purchasing, invoice processing, and reporting. Documents needed the same naming rules regardless of which tool created them. Those connections took longer than the first automation because they crossed team and system boundaries.
There is no clean sequence where the company fixes every process and then begins automating. The foundation and the tools develop together. Start small, measure the result, and use what you learn to decide whether the next process deserves the same treatment.