B/BBUILT BY BLAKEStart a conversation

A PRACTICAL GUIDE / SMALL BUSINESS AUTOMATION

What should a small business automate first?

If you keep pulling the same report or chasing the same follow-up, start there. Here's how I decide whether a task is worth automating.

By Blake Hamilton · Written

THE SHORT ANSWER

Start with the work that keeps coming back.

Start with a task your team repeats every week, with clear inputs and someone responsible for the result. Reporting, customer follow-up, and team handoffs are good places to look. Choose the one that costs you time or lets work slip, then simplify the process before you automate it.

See three places to start

FIND THE REPEATED WORK

Three places to look first.

These are the kinds of systems I've built in businesses I help run. Look for the one that sounds familiar.

Recurring reporting

You copy numbers between accounts to make the same report each week.

A FIRST IMPROVEMENT

Bring the numbers into one view, check them against the source, and show what needs attention.

See the Pulse reporting dashboard

Customer follow-up

An inquiry, review, or promised follow-up gets lost in the inbox.

A FIRST IMPROVEMENT

Track the next action in one place and prepare a reply for someone to review.

See the ReadyCrate follow-up workflow

Team handoffs

Staff re-enter a request or chase someone for its status.

A FIRST IMPROVEMENT

Collect the details once, send them to the right person, and make the status visible.

See the vendor operations portal

NARROW IT DOWN

Choose one task you can explain.

Start with work that repeats often and is easy to check. If a mistake could be costly, keep a person's approval in the process. Work through these questions before buying anything.

  • Does it happen often?

    Start with work that returns every week. A task you do twice a year may be easier to leave alone.

  • Can you explain the steps?

    You should know what starts the task, what information it needs, and what a finished result looks like.

  • Who handles the exceptions?

    Name the person who reviews uncertain results and takes over when the system can't finish the job.

  • What would improve?

    Count the time spent, missed follow-ups, or avoidable mistakes. Compare that with the build and ongoing costs.

SIMPLIFY BEFORE YOU BUILD

Some steps should disappear.

Check whether the report is needed at all. If a request gets entered three times, collect it once. If every job follows a different process, agree on the usual steps and the exceptions first.

Automation works better when the process already makes sense. I check what can be removed and what your existing software can handle before I recommend a build.

CHECK WHETHER IT'S WORTH IT

Know what a better week looks like.

For one normal week, record how often the task happens, how long it takes, and what goes wrong. Choose one result to compare after the build: less reporting time, fewer missed follow-ups, or fewer requests needing a status check.

A SIMPLE TIME CHECK / ILLUSTRATIVE EXAMPLE

That's the starting point. After the build, count review time and maintenance too. The difference is the time you actually reclaimed.

Time spent isn't guaranteed savings. A short task can still matter if mistakes or missed follow-ups are costly.

Include the build price, software subscriptions, and ongoing support in the decision. If the improvement doesn't justify those costs, simplify the task and leave it there. See how I price a first workflow build.

BEFORE YOU BUY A TOOL

A few common questions.

Does my first automation need AI?

No. Moving information, assigning a task, or sending a reminder can follow straightforward rules. AI can help read a message, summarize information, or draft a reply. I use it when the task needs that ability, with a person's review where mistakes would matter.

Should I buy new software first?

I would check what your existing tools can do first. You may already have forms, reminders, reports, or connections you aren't using. If those don't cover the job, we can compare a connection between tools with a custom build.

Should customer messages send automatically?

For a first build, I usually recommend preparing drafts and letting someone review them. Complaints, sensitive details, and unusual requests need judgment. Routine messages can be considered separately once the rules, permissions, and exceptions are clear.

START WITH ONE TASK

What keeps coming back to your desk?

Bring the report, the follow-up, or the handoff that keeps getting stuck. We'll talk for 20 minutes, free, and decide whether the $999 Business Systems Audit is the right next step.

Talk through one task

Free · 20 minutes · Kansas City + remote