← Back to Blog

The Week I Tracked Every Manual Task (And What It Cost Me)

I spent a week writing down every manual task I did. Every repeated action, every system-to-system copy-paste, every unnecessary chase. By Friday I had six pages. Here's what it revealed, and what I did about it.

By · · blog

The Week I Tracked Every Manual Task (And What It Cost Me)

The Week I Tracked Every Manual Task (And What It Cost Me)

I did something uncomfortable a while back.

I spent one week writing down every manual task I did. Every time I typed something I'd typed before. Every time I logged into a tool to copy something into another tool. Every time I chased something that should have been automatic.

I was not prepared for what I found.

It started as curiosity. I'd been building automated systems for other businesses for years. Telling clients their manual processes were bleeding them dry. Writing blog posts about it. I figured my own house was sorted.

Reader, my house was not sorted.

The Notebook Exercise

Monday morning. Notebook open. Every task, I wrote it down. Category, time spent, whether it was something I'd done before.

By Wednesday lunchtime I had two pages.

By Friday afternoon I had six.

Not because I was working longer hours than usual. Just because I was actually paying attention to what I was spending those hours on.

The categories that kept appearing:

  • Responding to the same type of enquiry with a slightly different version of the same answer
  • Copying information from one system into another because they didn't talk to each other
  • Chasing people for things they should have been automatically reminded about
  • Re-finding documents and files I'd found before but not organised properly
  • Writing emails that were 80% the same as emails I'd sent last week
  • Manually pulling together reports that could have been automated

By the end of the week I tallied it up.

Roughly 14 hours. Out of a 50-hour week. More than a full working day and a half. Just on stuff I'd done before.

The Numbers Are Universal

Here's the thing: I wasn't an outlier.

Research from Time etc puts the average entrepreneur's admin burden at 16 hours a week, which is 36% of a typical workweek. A Sage study published in May 2025 found UK small businesses are effectively working 13 months for 12 months of pay, because two days every month disappear into financial admin alone. A NerdWallet UK survey of 500 business owners found admin and operational tasks consume 7.3 hours a week in leadership time alone, costing the average business close to £19,000 per year.

And that's the stuff people admit to. The hidden layer, the context switching, the re-doing things you already did, the searching for files you know you saved somewhere, that's on top.

IDC data shows 20 to 30% of annual revenue disappears through re-keying, duplicated effort, and lost approvals in businesses that haven't automated their core workflows. That's not 20 to 30% of your admin budget. That's 20 to 30% of the whole revenue number.

Think about that for a moment.

What I Actually Did About It

After my week with the notebook, I went through every item on the list and sorted them into three buckets.

Bucket One: Automate it completely. Things that happened on a predictable trigger. Client submits a form, a sequence kicks off. Invoice goes out, a follow-up is scheduled. Appointment booked, confirmation and reminder goes out automatically. These didn't need me at all.

Bucket Two: Templatise and speed up. Things that needed a human in the loop but not a human starting from scratch each time. Enquiry responses, proposal structures, onboarding emails. I built templates and made them easy to find. Probably got these down to 20% of the time they used to take.

Bucket Three: Stop doing them entirely. Turns out, some tasks I was doing every week were tasks nobody actually needed. Reports I was writing that nobody was reading. Check-ins I was scheduling that could have been an asynchronous update. A whole afternoon back just from cutting the performative busy work.

The Inbox

Let's talk about email for a second, because it's where most people get swallowed.

The average knowledge worker spends somewhere between four and eight hours a week on email. Not doing things the email asks them to do. Actually reading, sorting, triaging, and replying to the email itself.

Most of that is: someone asking a question I've already answered, a notification from a tool I could have set up better, something that needed my attention once and now pings me every time anything happens.

I did three things. Turned off notifications from anything that wasn't a human. Set up a rule that auto-sorted anything from a known newsletter or tool into a folder I check once a week. Built a template library for the 12 enquiry types I get most often, so my replies take 90 seconds instead of 10 minutes.

My inbox went from a daily stressor to something I look at twice a day and handle in under 30 minutes total.

The Follow-Up Tax

If you're in any kind of service business, you know the follow-up tax.

You send a proposal. You wait. You think, should I follow up? You mentally track where everything is. You send a gentle nudge. You wonder if it was too soon or too late.

This is completely unnecessary work in 2026.

A properly configured CRM can handle every touchpoint in that sequence. Proposal sent, day three follow-up goes automatically. No reply by day seven, different message. Client comes back and books, the sequence stops and onboarding kicks in.

I have not manually followed up a proposal in a long time. The system does it. More consistently than I ever did, actually, because it doesn't forget and it doesn't get embarrassed about following up twice.

Result: conversion rate went up. Not because I wrote better follow-up emails. Because I was actually sending them, every time, at the right intervals.

The Reporting Hole

Every business owner I talk to spends time creating reports they then send to themselves.

Weekly summaries. Monthly overviews. Pipeline reports. Revenue snapshots. The actual looking-at-the-numbers bit takes five minutes. The pulling-it-together-from-four-different-places bit takes two hours.

My morning briefing now gets written by my AI system before I wake up. It pulls the key numbers from where they live, formats them the way I want to see them, and drops them into my workflow. By the time I sit down in the morning, I know where everything is.

That sounds fancy. It genuinely is not. It's a few integrations and a scheduled task. But it means I start every day in context instead of spending the first 45 minutes of the morning getting into context.

The Autonomy Dividend

Here's what none of the statistics really capture.

When you stop spending 14 hours a week on tasks you've done before, you get two things. You get the 14 hours back, obviously. But you also get your brain back.

Context switching is expensive in a way that's hard to quantify. Every time you break off from something that needs thinking to do something administrative, you pay a tax. Getting back to the thinking costs you time and mental energy you don't immediately see on a spreadsheet.

When the admin runs itself, you're not just getting hours back. You're getting the cognitive space to actually use those hours well.

I build systems for other businesses for a living. The Autonomous Business isn't a concept I sell. It's how I operate. Everything that can run without me, does. And I'm available for the things that actually need me.

The week with the notebook taught me that there was more in the "runs without me" column than I'd admitted to myself.

It might do the same for you.

What to Actually Do With This

If you want to try the notebook exercise, here's how to make it useful:

  1. For one week, write down every recurring manual task. Don't judge. Just log.
  2. At the end, sort everything into: automate completely, templatise and speed up, or stop entirely.
  3. Pick the single task that appears most often and takes the most time. Fix that one thing first.
  4. Don't try to automate your entire business in a weekend. One fix, properly done, compounds.

The businesses that build autonomous operations don't do it in one go. They identify the highest-cost manual task, remove it, then find the next one. Six months later they've handed back 15 to 20 hours a week and they haven't had to completely overhaul anything.

It starts with the notebook.

---

If you want to talk this through with people who are actually doing it, come join us in The Autonomous Business on Facebook. No gurus, no fluff, just real conversations with business owners building systems that run themselves.

---

About Steven Tann: Steven helps business owners build systems that run themselves using AI. After 10+ years helping 7,000+ businesses and building his own autonomous operations, he's the bloke who actually does it, not just talks about it. Find out more at steventann.com.

Tags: Small Business Automation, AI for Small Business, Practical AI, AI Ops, Business Systems, Autonomous Business, Workflow Automation