Saving an Hour Is a Refund
Everyone is getting time back from AI. Almost nobody is reinvesting it.
We did the second live episode of The Signal on Tuesday. Reuven and I promised no theory, just our actual playbooks: the day, the week, the month. This letter is the part worth keeping.
THE DIAGNOSIS
Most people use AI reactively. Rewrite this email. Build this deck. Summarize this document. All fine, and your inbox is still managing you. You wake up to thirty messages and spend the day reacting. The tool saves you an hour, and the hour disappears into more email and more meetings.
Saving an hour is a refund. Leverage is reinvesting it.
Reuven found his version of this the hard way. He connected an LLM to his email and calendar and asked it to be ruthlessly honest about how his time was being spent. The answer: ten to twelve hours a week on customer escalations, FYI meetings, and decisions that didn’t need him in the room. He wasn’t blind because he’s careless; he was blind because that pattern is invisible from inside the calendar. The audit made it visible. Then he built the triage plan and delegated the pattern, not the tasks.
Mine took longer. Eighteen months ago, I tried the scheduling fix everyone recommends: push all meetings to the end of the day and protect the morning. The day filled up anyway. Scheduling rules don’t fix a leverage problem. What fixed it was systemic: seven months ago we decided to become an actual AI-first company. Every week, every leader answers seven questions: what worked, what didn’t, how they used AI with a pre-built prompt so it takes minutes, not an evening. All of it, plus our call transcripts, email, CRM, and coding tools, feeds one knowledge base. The agents we build stand on that. The compounding showed up around month three. By month six it was the operating system.
The receipt: in January my calendar was wall-to-wall. Next week I have maybe five meetings, none longer than an hour. Same company. More customers than January. I used to call the old way management by walking around. Now it’s management by walking around, without the walking. The morning brief reads every system before I’m out of bed.
One warning, and Reuven said it best on the show: don’t outsource the thinking. The brain is a muscle, and if you hand the strategic work to the machine, it atrophies. Give it the menial layer. Keep the judgment.
THE NUMBER
40%.
Last October we hired our first AI engineer, and my big idea was to screen-record my own work, ship him the recordings, and have him figure out which parts could become agents. We spent weeks on it. The output was about 40% accurate. No lift. By any normal measure, a failed project.
It was the most useful benchmark we ran all year, because it told us exactly what to automate then and what to park. And here’s the part that matters if you’re sitting on your own failed pilot: the capability catches up faster than your roadmap. That was October. This week, the same job, turning a recording of my work into a working agent, took one evening. No engineer.
ONE THING WE SHIPPED
Claude released a screen-recorder skill: hit record, do the task, narrate if you want, and it turns what you did into a reusable skill. No engineering.
I pointed it at the task I was doing anyway, pulling together board materials. It watched me work, mapped the repetitive parts, and offered to build the skill. Monday night, after our actual board meeting, I ran it. The full board share-out came from a recording of what I actually do, the thing that took an engineer and me weeks to attempt at 40% last fall.
Reuven’s version is smaller and maybe better: he recorded himself fixing the fonts on every deck Claude produces, the tweaks he made by hand every single time, and turned it into a skill. Now the decks come out right the first time. That’s the shape to look for. Not the moonshot. The thing you repeat every morning: one instrument, not an orchestra.
That’s the week. If you missed the live, we’re back Tuesday at 9 a.m. Bring your skepticism; it’s the dress code down here.
Hit reply and tell me the workflow that’s costing you the most. The best replies become episodes.
— Chris
P.S. On the episode, we mentioned a Claude skill an executive-coach friend built. It runs your decisions through an Elon Musk lens and hands you a one-page “here’s what you should have considered.” I run most major company decisions through it now. Reuven says it punched him in the face. Reply if you want it, and we’ll send it over.