Most owners automate the task that annoys them most. It’s almost never the one costing the business the most time.
The invoice chasing gets fixed because it’s loud. Two hours every Monday, obvious, irritating. Meanwhile the three hours a week of re-typing job details from emails into the scheduling system carries on. Nobody counts it as a task anymore. It’s just part of the job. The reminders save twenty minutes. The re-typing keeps burning.
Write the week down before you build anything
Spend one week noting every admin task you touch. A running note on your phone is enough. Every time you do something that isn’t serving a customer or making a decision, add a line.
By Friday you’ll have thirty or forty lines, and the list will surprise you. Copying details from one place to another. Answering the same question for the fifth time. Building a report by hand that nobody reads until the following week. The small stuff is where the hours go, and it’s small enough that it never makes it onto a to-do list.
Then do two things with the list. Estimate how long each task takes per week, honestly. And mark whether the task needs a real decision from you, or whether a clear set of rules could handle it. That second mark matters more than the first.
The real time sink hides inside normal work
Here’s the pattern we see most. A bookkeeping practice puts client onboarding paperwork at the top of the list, because it’s the job the owner dreads. Then she tracks the week. Onboarding takes about ninety minutes. Hunting through the inbox for documents that arrived but were never filed takes closer to four hours. It happens in five-minute bursts across every day, so it never felt like four hours.
Brokers have the same thing with the first hour of the morning. Trades have it with quote follow-up. The tasks that feel like part of the job are the ones worth looking at hardest, because you’ve stopped seeing them.
Rank by how often, and whether it needs you
Two questions sort the list.
How often does it happen? Daily tasks go first, even the tiny ones. Ten minutes a day is over forty hours a year, before you count the interruptions around it.
Does it actually need you? Most owners get stuck here. They assume the task needs their judgement when it needs information they happen to hold. If the steps are the same each time and the answer comes from a rule, it can be handed off. If it changes with the situation, it stays with a person for now.
The tasks that stay with you still get lighter. The decision is yours, but the prep around it doesn’t have to be. Pulling the file, drafting the reply, checking the numbers against last month: all of that can arrive done, with the call left to you. Most owners find the decision takes two minutes once the twenty minutes of gathering is gone.
The first candidate is the task that happens every day, runs the same way each time, and doesn’t need you to think. Start there, not with the one that irritates you.
Write the process out before the AI touches it
Before you automate anything, write the steps out as if you were briefing a new staff member with no context. If you can’t, you’re not ready to automate it, and the confusion gets baked into the system.
It’s tedious. It also shows you where the complexity lives. A task that felt simple usually has a couple of edge cases you’d been handling on instinct without realising.
This step is where the setup starts becoming yours. The written process is one of the documents that makes AI useful in a specific business: how you work. An AI that has it can do the lookups and the reminders the way you’d do them, because you told it how. An AI without it gives you the average answer for every business, which is the answer you’ve been getting from the chat window.
Own the setup, don’t rent it
Do this inside a subscription tool’s template and the process lives in someone else’s product. Change tools and you start again. Write the process yourself, in a plain document you keep, and it moves with you to whatever tool comes next. Your team can read it. You can change it on a Tuesday afternoon without a support ticket.
Automating one task saves twenty minutes a week. Owning the document behind it is something you build on for years.
Get the week of notes done first. If you want the documents built properly and the AI set up on your real work, set up your own AI Operating System is the starting point. Work with Brightwaters covers what it looks like when we do it with you.