Your First Automation: Start Here

Every owner I sit down with says some version of the same thing in the first five minutes.

“There’s so much broken, I don’t even know where to start.”

After running a lot of assessments, I’ve landed on one question that cuts through every time.

What’s the most painful 30 minutes of your team’s day?

Not the biggest problem. Not the most expensive one. The most painful. The thing that makes someone audibly sigh when they sit down at their desk.

Why pain beats size

Big problems matter. They’re also slow, risky, and political. Start there and you’re three months in before anyone on the team feels a difference. By then half of them have decided the project is going nowhere.

A painful task is the opposite. You can ship a fix in days. The stakes are low if you have to tweak it. And the team feels the change the next morning when the thing they hated is just gone.

That feeling is worth more than any ROI calculation. Once people experience automation actually removing something annoying from their day, they stop being skeptics. They become the ones bringing you the next idea.

The pattern we see

The “most painful 30 minutes” almost always lands in one of four buckets.

Copy-paste data entry. An email comes in, someone retypes it into the spreadsheet, then retypes it again into QuickBooks. The fix is connecting the systems so the data flows once and lands everywhere it needs to.

Status update chasing. “Did you finish that?” emails. Walking to the shop floor to ask if the order shipped. Checking three places to figure out where a project stands. The fix is a shared dashboard that updates itself when work moves.

Follow-up reminders. Someone is keeping a mental list of overdue invoices, unanswered proposals, and customers who haven’t called back. The fix is letting the data trigger the reminder. If the invoice is 7 days late, the nudge writes itself.

Report compilation. Pulling the same numbers from the same three places every Monday to build the same report for the same meeting. The fix is letting the report build itself from live data. You review it instead of building it.

Same four patterns in a Wabash County machine shop and a marketing agency in Indianapolis. The tools differ. The pain doesn’t.

How to pick your first one

Ask the question. Pick whichever answer you hear most often. Then check two things before you build.

First, is it actually repetitive? Daily or weekly counts. Once a quarter doesn’t.

Second, are the rules clear? If X, then Y. If the task requires reading the room, making a judgment call, or handling exceptions, it isn’t a good first automation. Save that for later.

Your first automation should be boring. Boring is reliable. Boring earns trust. Once people trust the boring one, they’ll bring you the interesting ones.

What happens after

The 30 minutes is not the win. The win is what happens the week after the first one ships.

People start sending me Slack messages without me asking. “Could we do the monthly inventory count next?” “What about the customer survey replies?” “Can we auto-generate the schedule?” That mindset shift is the whole point.

Start with the pain. The rest follows.

If you want help picking the right first one, that’s exactly what the assessment is for. The FAQ covers the questions I hear most. And if you want to see how this looks once it’s running day to day, take a walk through the Desk. That’s where the boring automations live and quietly do their job.