The best automation candidates aren't the most painful processes. They're the most boring ones.
Teams usually want to automate the workflow they hate most — which is often complex, exception-riddled and political. The better strategy is to start where automation pays back fastest: work that is high-frequency, rule-based, and low-stakes per instance. Across our client work, five workflows meet that bar almost everywhere.
1. Intake: forms that file themselves
Every request that arrives by email — IT issues, leave requests, client enquiries, maintenance jobs — costs someone the work of reading it, extracting the details and re-typing them somewhere. Replace each intake stream with a structured form feeding a sheet or tracker, and the triage work largely disappears. This is almost always the first automation we build, because everything else stacks on top of clean intake data.
2. Chasing: reminders that send themselves
Somewhere in your organisation, chasing is somebody's job: overdue returns, unsigned documents, unpaid invoices, pending approvals. Chasing is pure rule-following — if overdue and not returned, remind; if still overdue, escalate — which makes it perfect automation material. It's also the automation staff are most grateful for, because chasing is universally disliked from both ends.
3. Document generation: stop hand-assembling the same document
Certificates, letters, quotes, reports, contracts — if your team builds documents by copying last time's version and swapping the details, you're paying twice: once in labour, once in the errors that copy-paste guarantees. Generating documents from structured data produces them in seconds, formats them identically every time, and removes the wrong-name-in-the-letter class of embarrassment entirely.
4. Status reporting: the report that writes itself
The weekly or monthly report someone assembles from three spreadsheets is a strong signal of automation debt. If the underlying data is captured cleanly (see workflow 1), a live dashboard replaces the assembly work completely — and upgrades reporting from "how things looked when someone last compiled it" to "how things are now".
5. Onboarding and offboarding: the checklist that runs itself
New starter and leaver processes touch accounts, equipment, access and training — many steps, many owners, high cost of a missed step (especially on offboarding, where forgotten access is a security incident waiting patiently). Turning the checklist into a triggered workflow with owners and deadlines makes the process reliable independent of who's running it that week.
The one sign a workflow isn't ready
If nobody can describe the process the same way twice, it isn't ready for automation — it's ready for a conversation. Automating an undefined process just produces undefined results faster. The fix is a one-hour process-mapping session with the people who do the work; the automation follows naturally from the map.
Where to start on Monday
Pick the workflow from this list that runs most often in your organisation. Estimate, roughly, the minutes it consumes per week across everyone involved — the number is usually a surprise. That number is your business case, and for most small teams, workflow one or two pays for its own automation within the first quarter.