Key takeaways
  • Sixty minutes is enough to finish one small job you're sick of doing
  • Pick a chore you already do every month and can't stand, then give the hour to that
  • A month of content scheduled in one sitting is the most common first win, because you already wrote the material
  • The report you rebuild by hand every month is the second: same inputs, same shape, same questions
  • If the hour ends with nothing finished, the task was too big. Cut it in half and run it again next week

You're running the business, chasing invoices, covering the front desk, and writing the posts nobody else is going to write. So when someone tells you it's time to learn AI, of course the answer is that there's no hour spare. And if you dug one out, what good is a single hour?

More than you'd think. Sixty minutes is enough to get one job you're sick of off your plate for good.

"Learn AI" is the part that won't fit

The phrase has no finish line. You can't schedule it, so it sits on the someday list next to cleaning out the storage closet.

Pick one chore you already do every month and can't stand. Now the hour has edges, and you'll know before it's up whether it worked.

Pick the chore first

Three tests. A good first job passes all of them:

  1. It happens on a schedule. Weekly, monthly, every time a new client signs.
  2. What goes in looks the same every time. An export, a form, a statement.
  3. What comes out has a format you settled on ages ago. A spreadsheet tab, a summary email, a one-pager.

All three true means the work is mostly copying, and copying is the easiest thing to hand off. Miss one test, save it for later. Miss two and it's a project, and projects aren't week-one work.

Two chores come up more than any others.

Hour one: a month of content in one sitting

You have plenty to say and no moment to say it in, so posts get written the day they go out, or they don't go out. The material already exists. It just isn't queued.

  • 0 to 10 minutes. Gather the last few months of what you've published, emailed, or posted.
  • 10 to 20. Pick the ten pieces that actually got a response. A reply, a call, a booking.
  • 20 to 45. Feed them to ChatGPT (or Claude, or whichever assistant you've got open) one at a time. Ask for a short post from each, in your words, for the one platform you actually use.
  • 45 to 60. Read them, fix the two that sound off, load them into your scheduler, set the dates.

Four to six weeks queued, and you don't open the app again until it runs dry. Next month takes twenty minutes, because you only decide the shape once.

Hour two: the report you rebuild every month

You've almost certainly got a recurring report. A month-end summary, a client update, the same numbers from the same three places in the same layout. And every month somebody rebuilds it from scratch.

It makes a great first automation for one reason: you've already done it twenty times. You know what goes in, what comes out, and which parts need your read on them. That's the instruction manual, and writing the instruction manual is normally the expensive part.

  • 0 to 20 minutes. Write down your steps in order, including the obvious ones. Especially those.
  • 20 to 30. Show your AI tool one finished report you were happy with, and say "this is the target."
  • 30 to 45. Have it build the same thing from this month's numbers.
  • 45 to 60. Read it closely and correct what it got wrong.

It'll be wrong in a place or two. Correcting that is the work, and it's why month two takes ten minutes.

What one hour grows into

A bookkeeping practice I worked with sent every client a weekly update by hand: run the same reports, read the balances off the bank login, retype it all into that client's spreadsheet in a particular layout. Five to fifteen minutes each. Across a full roster, most of an hour every week.

Now the exports go in a folder, she double-clicks one thing, and the new week's tab comes back filled in. About two minutes.

What made it safe on real client work was a few small decisions:

  • It copies last week's tab and fills that in, so the layout and formulas carry forward. Nobody had to describe the spreadsheet to a computer.
  • It stops rather than guess. A missing figure means it refuses to finish. A tool that stops is a tool you can leave alone.
  • It writes a new copy alongside the original, so a bad run costs nothing.

The know-how stayed hers. Categorizing a transaction, checking whether a number is right, writing the part that needs someone who knows the client. She still reads it before it goes out. What came off her plate was the retyping.

One task, described precisely, that happened the same way every week. Between that first hour and this, all that changed is the description got precise enough to hand over for good.

What an hour won't do

It won't make you fluent, and it won't tell you which tool to use for what. That comes later, from having finished a few small things.

It also falls apart on a job you've never done by hand. If you can't describe the steps, AI can't follow them. Worth knowing. Different hour.

And if the hour ends with nothing finished, the task was too big. Cut it in half and run it again next week. Still faster than waiting for the quarter when everything calms down, which hasn't shown up yet for anyone I've asked.

Start this week

Open a free account with any AI assistant, sit down for your hour, and pick the one chore. Start with the boring repetitive one. Repetition is what makes handing it off possible at all.

If you want a head start, Business Brain loads your business into your AI: your voice, your customers, your offers, the way you do things. So it already knows, instead of you re-explaining yourself every time you open a chat window. It's $50, one time, and you can use it as often as you like. If you'd rather have a hand pointing it at your situation, reach out and we'll talk it through.