The Weekly Performance Review I Built Out of My Own Data

This week I listened to two AI voices spend fifteen minutes breaking down exactly how I’d spent the last seven days: where my energy got zapped, where it got charged, and whether I’m actually building the business I set out to build this year.

Then one of them called me out. And it had the receipts.

I’m a solo operator, which means no one hands me a performance review. No manager pulls me aside on a Friday to tell me I’d been hiding in the work I’m good at instead of the work that actually moves the business. So, newly and fully bought into the Claude Code cult, I built the thing that would.

No one makes you zoom out when you work for yourself

This is the trap of running your own thing that nobody warns you about.

When you’re on a team, the structure asks the hard questions for you. Reviews, one-on-ones, a boss who notices when you drift. Annoying in the moment, but they force a reckoning on a schedule.

Work for yourself and that scaffolding disappears. You’re at capacity, heads-down, shipping. No one forces you to stop and ask whether you’re doing the work you should be doing, or living the life you said you wanted. You can go weeks without asking. Months before you do anything about it.

The freedom is the whole point. It’s also the problem.

I gave it the receipts

So I wired up an outside advisor out of my own data.

My time tracking from Timeglass. My meeting recordings from Granola. My calendar. My Claude Code sessions. All of it bundled together, checked against the goals I set for the year, and turned into a private, fifteen-minute podcast in NotebookLM. A weekly deep dive on me, built entirely from what I actually did, not what I remember doing.

That last part is the whole game. Memory is generous. It rounds the week up, forgives the drift, tells you the story you want to hear. The data doesn’t. It knows where the hours went.

Then it called me out

It opened kind. It celebrated a clean forty-hour week and a weekend I spent completely unplugged, exactly the work/life balance I’ve been chasing this year. I’ll take it.

Then it turned.

I’d spent too much of the week buried in delivery work, the stuff I’m good at and the stuff that feels productive, instead of the strategic ops work that keeps an agency’s best accounts healthy and growing. And it wasn’t vague about it. It pointed straight at my own calendar and time logs and showed me. Not gonna lie: it was kind of painful to hear.

But painful from a machine reading my own receipts back to me is a very different thing from painful from a boss. There’s no politics in it, no ego. Just: here’s where your week actually went, and here’s the gap between that and what you told me you wanted.

The point isn’t the tooling. It’s the mirror.

It’s early, and I’m not going to pretend a NotebookLM podcast is about to run my business for me.

What excites me is smaller and more useful than that. When you work for yourself, the hardest thing isn’t doing the work. It’s noticing, in time, that you’re doing the wrong work. Most of us catch it a quarter too late.

The obvious objection is that I could open my own calendar on a Friday and skip the build entirely. I tried that for months. What I got back was the version I wanted to see, because I was the one deciding after the fact which meetings counted as strategy and which hours counted as deep work. Handing that call to something reading the logs instead of my memory is the part that actually works.

Build something that catches it on a Friday instead. Point it at your real data, let it hold up the mirror, and let it call you out while there’s still time to change the week ahead.

And wow, Claude Code is a hell of a drug.