Issue No. 08 - July 28, 2026

I sat down last week to calculate how much time AI actually saves me each day.

I couldn't do it.

I've been using AI tools almost every day for months. I should have a number. But the honest answer is more complicated than I expected.

When I started, I assumed the math would be obvious. Do something with AI, do the same thing without AI, count the minutes. The problem is it doesn't work that way in practice.
​

Some things genuinely take less time now. Writing a first draft used to mean staring at a blank page for longer than the actual writing took. Now I get a rough version I can react to, and reacting is faster than originating. That's the honest part. I've also used AI to research things I used to either delegate or skip entirely because the time cost of figuring them out myself wasn't worth it. Both of those are real.

AI also created work I didn't have before.

I'm publishing this weekly newsletter now. Writing the associated blog posts. Working on AEO for The Operator's Notebook. And at JB Sales, where I still have my full role, I'm also running AEO strategy, doing audits on a 552-post blog, fixing technical issues on the website I would have handed off before, and making sure GA4 is configured correctly as it keeps changing. None of that existed in my workload before I started using AI tools. Not because AI pushed me to. Because it made it possible without a team. So did AI save me time? Or did it expand what I was capable of doing, and I filled that capacity with more work?

There's another part nobody talks about. When you finish something with AI's help, the next step surfaces on its own. You complete the audit, and the logical next thing appears. You do that, and another one follows. Manual work has natural stopping points. You run out of time, energy, or information. AI-assisted work keeps generating the next task. It doesn't stop. I saw a post this week from Rachel Woods asking what non-technical skill people were focusing on right now. My answer was time-blocking. Not because I'm particularly disciplined, but because it's the only thing that actually closes the loop. You have to decide in advance when you're done, or AI will keep finding the next thing for you.

I think for most people using AI day-to-day, it's the second one. The time savings are real but they get absorbed immediately into the new things AI makes possible. You don't end up with extra hours at the end of the week. You end up with a bigger scope of work and a slightly smaller sense of what you can't do alone.

There's one place where I've seen genuine, uncaptured time savings: tasks I used to dread and put off. Things that weren't hard, exactly, just annoying enough that I'd let them sit. AI lowers the activation energy on those tasks to the point where I actually do them. That's not time savings in the stopwatch sense. But it's real.

The question I'd ask instead of "how much time does AI save?" is: what can you do now that you couldn't do before? That's the better question. And the answer is usually more interesting than a number.

Where this lands in the three buckets

Immediately actionable: Start time-blocking your AI work sessions. Decide in advance when you're done with a task and its adjacent ideas. If you don't set that boundary, AI will keep surfacing the next thing, and you'll keep following it.

Start thinking about: Whether the value you're getting from AI is really about time, or about capability. If AI is letting you do things you couldn't do before, rather than just doing existing things faster, that changes how you should think about where to use it next. Timing a task with and without AI is a good place to start.

Next phase: Building repeatable systems around the AI tasks that save you the most. Saved prompts, templates, workflows you can run without starting from scratch. That's where the compounding actually happens.

Meghan Brenner is COO at JB Sales and founder of The Operator's Notebook. The Muddy Middle publishes every Tuesday.