/michael abella
Back to all writing

Which business workflows should you automate first?

Choose automations that save time without creating brittle operational dependencies.

Start with operational friction

Look for work that happens often, follows a stable rule, consumes attention, and has a clear owner when something fails. Lead routing, reporting, invoice reminders, and cross-system updates are often better starts than an autonomous agent.

Score the opportunity

Estimate frequency, minutes per run, error cost, implementation effort, and exception rate. A boring five-minute task repeated 200 times monthly may beat a sophisticated workflow used twice.

  • Define the trigger and outcome.
  • Document exceptions before building.
  • Keep an audit trail.
  • Retry without creating duplicates.
  • Provide a manual fallback.

Add AI where judgment helps

Models are useful for classification, extraction, summarization, and drafting. Keep approvals around high-impact external actions and validate structured outputs before updating systems.

Measure after launch

Track time saved, failure rate, exception volume, and downstream outcomes. Operational visibility is part of the deliverable.