Online operations · Digital entrepreneurship

What Should a Small Business Automate First?

Automate work only after the inputs, owner, exception path, and desired result are clear enough to test.

Originally published
September 5, 2026 by Matt Herrera
Reviewed and updated
September 5, 2026 by Matt Herrera

Start with stable, observable work

Good early candidates are repetitive, rules-based, and easy to verify. Copying approved form data into a tracking system may fit. Handling a disputed refund or interpreting a contract usually needs judgment and a clear human owner.

Measure the current process before automating it. Record volume, time, error types, delay, and the cost of a wrong result.

Score each candidate

Give preference to work that happens often, follows stable rules, produces a visible record, and can be reversed. Reduce the score when the process uses sensitive data, sends external messages, moves money, changes access, or has unclear exceptions.

  • What event starts the process?
  • Which system is the source of truth?
  • Who approves a consequential result?
  • How is a duplicate prevented?
  • What happens when a provider or input fails?
  • How can the action be audited and reversed?

Keep a human gate where representation matters

Drafting, classifying, and routing can save time without letting software make every decision. External publishing, customer promises, payments, account changes, and regulated advice need controls proportionate to their consequences.

Run the automation in a test environment, compare its output with the manual process, and define a shutoff path before enabling it on live work.

Sources and further reading