The Core Question
Before automating anything, ask: how many times does this task happen, and how long does it take each time? A task that takes 5 minutes and happens twice a month is not worth automating. A task that takes 20 minutes and happens 50 times a month is.
The rough math: if a task consumes more than 10 hours of staff time per month, it's worth exploring automation. Below that threshold, the setup and maintenance cost of automation often exceeds the time saved.
Where Automation Consistently Wins
Data entry and transfer — moving information between systems, filling spreadsheets from forms, updating CRMs from emails. These are high-repetition, low-judgment tasks where automation is reliable and the ROI is immediate.
Notifications and follow-ups — sending confirmation emails, reminders, status updates. Once set up, these run without oversight and eliminate an entire category of dropped balls.
Reporting and dashboards — pulling data from multiple sources and assembling a weekly or monthly report. Automating this frees up the person who was doing it manually and makes the report more consistent.
Where Automation Struggles
Anything requiring real judgment about edge cases. Automation handles the 80% well, but the 20% of exceptions will still land on a human. If there's no clear process for handling exceptions, automation creates confusion rather than efficiency.
Client-facing communication that needs a personal touch. Automated responses work fine for acknowledgments, but relationship-building still requires a person.
The Right Order
Document the process first. If you can't write down exactly what the steps are, you can't automate it reliably. Automation codifies a process — if the process is unclear, you'll automate the confusion.
Simplify before automating. Documenting a process often reveals that half the steps are unnecessary. Cut those first, then automate what remains.
Start with one process. Pick the highest-volume, lowest-judgment task and automate that. Once you see it working, expand from there.
Working With a Tech Partner
When scoping automation projects, the first step should always be mapping the current process in detail. Often that alone surfaces quick wins that don't require any code. The actual build starts only once you agree on what the optimized process looks like.