The Solopreneur's Automation Audit: How to Find 10 Hours Hiding in Your Week

Ask a solo operator where their week goes and you'll get a confident answer that's wrong. "Mostly client work." Then you track it, and client work turns out to be 22 hours. The other 25 went somewhere. Nobody budgeted for them. Nobody remembers spending them. They just left.

We run audits on solo businesses for a living, and the pattern holds almost every time: the operator is not overworked because the business demands it. They're overworked because a hundred small tasks never got looked at as a group. Individually, each one is four minutes. Nobody audits a four-minute task. That's the hiding spot.

Here's the audit we use. It takes one week of light tracking and about an hour of sorting. You can run it yourself this week.

Step 1: Track one real week

Not a calendar review. A log. For five working days, every time you switch tasks, write one line: what you did, roughly how long it took. A note on your phone works. A text file works. The bar is low on purpose — if the tracking takes effort, you'll quit by Wednesday.

Two rules. First, log the small stuff. "Replied to scheduling email, 3 min" goes in. The small stuff is the entire point. Second, pick a normal week. Not launch week, not vacation-adjacent. Boring and representative.

By Friday you'll have 60 to 100 lines. That's your raw material.

Step 2: Sort every line into make, sell, or run

Every task in a one-person business belongs to one of three buckets:

Make — producing the thing clients pay for. Design, code, coaching calls, writing, the deliverable itself.
Sell — anything that brings in the next dollar. Proposals, discovery calls, follow-ups, content that generates leads.
Run — everything else. Invoicing, scheduling, updating the spreadsheet, moving a file from one tool to another, answering "what's the status" emails.

Sort your log and total the hours per bucket. Most operators guess their split is 60/20/20. What we actually find is closer to 45/15/40. Run tasks routinely eat 15 to 20 hours a week in businesses where the owner swears "admin is maybe five hours."

Run tasks are also where automation pays off first, because clients don't care who — or what — does them.

Step 3: Score each run task for frequency and friction

Give every run task two scores from 1 to 3.

Frequency. 1 = monthly, 2 = weekly, 3 = daily or more.
Friction. 1 = you barely notice it, 2 = mildly annoying, 3 = you actively procrastinate on it or it breaks your focus.

Multiply. Anything scoring 6 or 9 goes on the shortlist. A daily task you dread (9) beats a monthly chore (1–3) every time, even if the monthly chore takes longer per instance. The math favors the drip, not the flood: a 5-minute daily task is 20+ hours a year. A painful quarterly one is maybe 4.

The three places hours actually hide

After enough of these audits, three categories show up so reliably we check for them first.

Context switching

The task log says "replied to email, 4 min." The damage is the 15 minutes it took to get back into the proposal you were writing. If your log shows more than 10 task switches per day, the switches themselves are likely your single biggest line item — and they never appear as a line item. Batching and automation both attack this: an agent that handles routine replies in one morning block removes both the task and the switch.

"Quick" replies

Scheduling back-and-forth. "Just confirming we're still on." "Can you resend that invoice?" "What's your availability?" Each is two minutes. A consultant we audited sent 41 of these in one week — nearly 90 minutes of typing sentences she had typed hundreds of times before. Almost all of them had exactly one correct answer that a system could have produced.

Manual data shuffling

Copying a form submission into the CRM. Retyping invoice details from an email into the accounting tool. Downloading a CSV from one place to upload it somewhere else. This is a computer doing a computer's job, with you as the middleware. It's also the easiest category to automate outright — deterministic, rule-based, no judgment required. (If you're unsure whether a task needs a simple automation or an actual agent, we wrote up the difference.)

What a finished audit gives you

At the end you have three things you didn't have on Monday.

A real number. Not "I feel busy" but "run tasks took 16.5 hours last week." Numbers you can act on. Feelings you can only complain about.

A ranked shortlist. The five to eight tasks scoring 6+, ordered by hours reclaimed. This is your build queue. You don't need to automate everything — the top three usually cover 60% of the recoverable time.

A decision you can defend. Whether you build the automations yourself, hand the list to someone who builds them for you, or decide a task isn't worth fixing yet — you're now choosing with data instead of vibes.

Ten hours a week is not a stretch goal. It's the median of what this audit surfaces for a solo operator who has never done one. The hours were always there. They were just filed under "that only takes a minute."