I’ve been trying to make a list of everything AI has made possible for me in the last three months. I keep losing count.

Here’s what I’ve got so far: I launched a startup. Built and shipped three apps — Momentum Maker, Hue Are You, Turf Genie – without a development team. Started a podcast from scratch. Marketed a rental property more aggressively than I ever had time to before. Built what I think of as a lights-out development factory. Replanned a vacation in real time when things went sideways. Tracked a full home remodeling project without letting a single thing fall through the cracks.

And I’m sure I’m forgetting something.

I’m not listing these to impress anyone. I’m listing them because every single one of those things existed on a whiteboard – or a back-of-napkin, or a “someday” conversation – before AI. They existed as ideas that ran into the same wall: not enough hours, not enough hands, not enough runway to do everything a project actually requires to get off the ground.

AI didn’t make me faster at the things I was already doing. It moved the threshold for what I could attempt at all.

That’s the thing the spreadsheet misses. Every AI ROI conversation I’ve been part of starts the same way: hours saved, FTEs redeployed, costs amortized. The model captures what AI replaces. It almost never captures what AI creates: the projects that didn’t exist before, the bets you couldn’t make, the ideas that stayed on the whiteboard because the execution was too expensive for one person with a full-time job and a life.

A recent HBR piece framed AI failures as a “last mile” problem – the gap between promising pilots and production value. That’s real. But I think there’s a prior question: what are you not even attempting because you don’t believe you have the capacity?

That’s where I’ve found the real leverage. Not in doing existing things faster, but in crossing the threshold into things I wouldn’t have tried. A solo founder can now do what used to require a team. One person with discipline and the right tools can run a development shop, a content operation, a marketing function, and a rental business in parallel — not perfectly, but for real.

The organizational version of this is what I think most transformation conversations miss. The question isn’t “how do we save 200 hours a month?” It’s “what are we not attempting because we assume we don’t have the capacity?” Those are different questions, and they lead to very different investments.

The hours-saved number shows up in the spreadsheet. The attempt that didn’t happen doesn’t show up anywhere. It’s just absence. And absence is very hard to build a business case around.

I keep losing count of what AI has made possible for me because the list keeps growing. I think the same thing is true for organizations that actually do this right – not the ones that automate a process and declare victory, but the ones that ask what they can now attempt that they couldn’t before.

The spreadsheet isn’t wrong. It’s just incomplete. And the part it’s missing is usually the most important part.

That’s what I’ve been building toward on CTO Unfiltered. I will tackle the organizational version of this question in the next episode. If you haven’t subscribed yet, now’s a good time.