The three workflows every business should automate first
Most automation projects fail because the starting point is wrong. Here are the three workflows that almost always justify the effort — and how to pick which one to tackle first.
Most automation projects don't fail because the technology is wrong; they fail because the starting point is wrong. Founders pick something complex, interesting, or strategically important, and spend three months building something fragile that half the team doesn't trust.
The workflows worth automating first share three characteristics: they're repetitive, they follow consistent rules, and they happen often enough to justify the setup cost. That description fits most businesses' document processing, approval chains, and reporting routines. Start there.
Document processing
If your team is manually typing invoice details into a system, keying purchase order numbers, or transcribing information from PDFs into spreadsheets, that work can be automated. Tools like Dext and Hubdoc handle most document processing accurately enough that human review becomes the exception, not the rule.
The business case is simple: every invoice that goes through a person's hands instead of a system is a small tax on your operation, paid repeatedly, forever.
Approvals
Expense approvals, leave requests, purchase sign-offs, content reviews: these live in email inboxes, get lost, and create bottlenecks that slow everything downstream. Chasing them manually is a symptom of a missing process, not a workload problem.
An automated approval workflow routes the request to the right person, reminds them if they haven't acted, escalates if the deadline passes, and records the decision. None of that requires a developer; it requires a day or two of setup in a tool your business probably already pays for. Make, Zapier, or Power Automate can handle most of it out of the box.
Reporting
Most weekly and monthly reports are assembled by hand from data that already exists in your systems. Someone pulls numbers from the CRM, copies them into a spreadsheet, adds the finance figures, and formats the whole thing. That work is pure assembly — and assembly is what automation is for.
A report that runs itself and lands in inboxes on schedule is not a luxury; it's the correct use of the tools you're already paying for.
Where to start
Pick one. Not the most interesting one, the most painful one. The process that takes the most time, happens most often, and creates the most frustration when it falls behind. Automate that first, learn what works, and use that confidence to tackle the next one.
Three months from now, you'll have one workflow running automatically that used to require a person. That's more valuable than a half-finished automation strategy that covers everything in theory.
Automating the right things takes a bit of analysis before it takes any technology. Start with a conversation.
Robin Carswell
More on
What AI-native actually means for a business that doesn't write code
Most businesses calling themselves AI-native are at level one of four. The gap between levels is the difference between accumulating tools and building something that compounds.
Why ChatGPT is not a strategy
Using AI everywhere isn't a strategy any more than not using it is. The businesses getting it right know exactly where variability lives — and how quickly they can move downstream into something predictable.
AI doesn't know what day it is
AI will tell you the answer whether it knows it or not. Understanding the structural blind spots — the things it genuinely can't know — is the difference between using AI well and being misled by it.