The Shape of It So Far

If you chart what I got done week by week across these six months, it doesn’t look like a plan. It looks like a heartbeat. Two enormous spikes near the start, a long sag through the middle, one week completely flat, then a smaller, sharper rhythm at the end.

I didn’t design that shape. But I recognise it now, and it tells the honest story of what a solo build actually feels like. This is the second of my reports; the first was about what I did. This one is about the rhythm of doing it, and what the shape taught me that the running total never could.

It didn’t start with a build. It started with a conversation.

The first week, I didn’t write code. I didn’t really write the strategy either. I sat down and had it out with the AI: a proper back-and-forth about what I actually wanted. Not “what should I build this month,” but “what does the north star for my life look like, and how do I move towards it without ignoring this month’s bills?”

That conversation might be the single highest-leverage thing I did in the whole six months. I’ve paid consultants for less clarity than I got in an afternoon of being asked good questions and made to answer them.

So here’s the first lesson, and I keep relearning it: the best opening move with these tools isn’t automation, it’s thinking. Use the thing to get clear before you use it to get busy. Everything downstream is cheaper when you do.

Then two months of everything, all at once

March and April were relentless, in the good way. I built the toolkit first, then used it to stand up one of my businesses end to end: platform, brand, first piece of writing live inside a fortnight. One week I closed just shy of 200 separate tasks. The peak week went past 200. In a single pass through my CRM I deleted 4,223 junk company records that had been rotting in there for years.

The part that actually matters isn’t the volume, though. It’s that those weeks were survivable at all. And they were only survivable because I wasn’t carrying any of it in my head. Every idea, every loose end, every “must remember to” was out of my mind and sitting in a system I trusted. If you’ve ever lain awake mentally juggling forty open loops, you’ll know exactly how much that quiet is worth.

There’s a catch, and it’s the real lesson here. That only works while capture stays effortless. The moment logging a thing costs more than just doing the thing, you stop logging, the system rots, and the whole load slides straight back into your head. The win was never the AI being clever. It was frictionless offload, plus the discipline to keep the friction near zero.

The dip nobody writes about

May was the comedown. The pace came off, the work narrowed, and then came the quietest stretch of the lot, ending in a week where I closed precisely nothing. Zero. Not a holiday, not a planned rest. A flat week.

It’s staying in, on purpose. Every honest build has one, and almost every write-up deletes it, because a dead week ruins the story of relentless compounding progress. That deletion is the quiet lie that makes everyone reading feel like they’re the only one flagging. The flat week is the most reassuring data point I own. It’s proof this was real, and it’s permission for the next one.

The second wind

From mid-June the energy changed. Not foundation any more: reconnecting with people I’d let go quiet, then narrow, specific plumbing. Fewer grand new machines, more making the existing ones behave.

That shift, from starting things to finishing them, is the one that quietly tells you a build is maturing. Starting is easy and faintly addictive. Finishing is the less fun half, and it’s where the value actually lives. Watching my own chart cross from one to the other was the point this stopped being a hobby and started being a body of work.

So what’s the shape?

Not linear, not heroic. A sprint, a sag, a dead week, a steadier second act. Stare at the running total and you’d miss every bit of that.

Think first. Offload everything, but only while it stays effortless. And let the thing breathe, flat weeks and all. The chart isn’t a productivity flex. It’s a pulse, and a pulse is meant to rise and fall.

Posts in this series

Working Life