Every AI Book Tells You What to Think. This One Is About What Your Hands Do.
There is a whole shelf of AI books for leaders now. I read enough of them to know why I wrote a different kind.
There is a shelf now. If you are a senior leader trying to make sense of AI, you have probably bought most of it. The strategy book. The mindset book. The one with the four-quadrant framework. The one from the consultancy with eleven co-authors. They are not bad books. Several are good. I learned things from them.
But I noticed something after the fourth or fifth one. I would finish a chapter, nod, underline a sentence, and then sit there with my hands in exactly the same place they were before I started reading. The book had changed what I thought about AI. It had changed nothing about what I did with it on Monday.
That is the gap I wrote into.
The book changed what I thought about AI. It changed nothing about what I did with it on Monday.
The shelf has one shape
Read enough of these books and the shape repeats. They tell you what to think about AI. How to frame it for your boss/peers/board. Which mental model to adopt. Where it sits in your strategy. They are written from the altitude a leader is used to operating at, which is to say: above the work, directing it.
That altitude is the problem, not the solution. Someone reviewing the current best-seller in this category said it reads like a 2024 book explaining how the Internet will help your business. The line is unkind and basically right. Not because the author is wrong, but because the genre has a ceiling. You cannot write the operator's manual from the strategy altitude. The two are different books, and almost everyone is writing the first one.
I wanted to read the second one. Nobody had written it for the reader I had in mind, so I wrote it.
You cannot write the operator's manual from the strategy altitude.
What "what your hands do" actually means
"Leaders should build" is already a slogan, and slogans rot.
I don't mean you should learn to code. I mean something narrower. There is a class of tools now, Claude Code chief among them, that lets you direct a multi-agent system to produce real work inside your own domain. You describe intent, set boundaries, review what comes back, redirect, and ship. The interface happens to be a terminal; the skill is not programming. It is the same skill that got you to senior: defining the why, designing the handoffs, judging the output, catching the thing that looks right and is wrong.
You already do all of that. You do it with people. The book is about pointing those same instincts at a harness instead of a team, and what changes when you do.
The reason this matters is not productivity, though the productivity is real. The reason is calibration. Andrej Karpathy named it this spring in a line that landed with twenty thousand likes and a thousand replies: there are two groups talking past each other about AI, and the line between them is not skeptic versus believer. It is the people who have built something with these systems and the people who have read about them. Every confident claim you have heard about what AI can or cannot do was made from one side of that line. If you are reasoning about AI from the reading side, you are reasoning from the wrong data, and no amount of strategy reading moves you across. You move across by getting your hands on the controls one time and feeling where the real edge is.
Why I get to say this
What separates this book from the shelf is that I did not write it from the strategy altitude. I built and led an AI Center of Excellence at a Fortune 500 pharmaceutical company, and I now lead applied data and AI in R&D at an AI-driven biotech. I also run a deep personal practice on nights and weekends, eight autonomous agents and a homelab full of skills, because the day job and the obsession turned out to be the same skill. This book was itself produced through the harness it describes, end to end. About a month from kickoff to typeset manuscript, against the year the same book would have taken by hand, with thousands of hours of research, red-teaming, and editing behind it, most of it run in parallel by the system rather than typed by me. You can see the skills that drafted it.
I am not telling you to do something I read about. I am telling you what it was actually like, including the parts that are awkward and the parts that broke.
I am not telling you to do something I read about. I am telling you what it was actually like.
The part I won't oversell
At Sequoia's AI Ascent this spring, Karpathy declared "vibe coding" obsolete and named its successor "agentic engineering," a discipline with real rigor and real responsibility. He is right. He also drew a careful line: prototyping with AI raises the floor for everyone, but operating serious systems demands discipline you cannot wave away.
My book asks you to step over a line slightly further out than the one Karpathy draws for the general public. I am asking a senior, non-technical executive to personally operate, not just prototype. I think that is where the role is heading, and I think the leaders who learn it first will shape what their organizations become. But I am not going to pretend it is the consensus position. It is an argument. The book makes it, and gives you the controls and the guardrails to test it for yourself rather than take my word for it.
Who will not find this useful
If you want a framework to put on a slide for your board, the shelf has better options than mine, and I mean that. If you want reassurance that your current AI strategy is sound, this is the wrong book; it will probably make you uncomfortable. If you are looking for predictions about AGI timelines, I route around that debate on purpose.
This book is useful if you have read the think pieces, sponsored the center of excellence, watched the pilots, and still feel the quiet gap between knowing AI matters and knowing what you personally do about it. It is useful if you are willing to spend a few hours with your hands on something unfamiliar, on your own files, to find out where the edge actually is. It is a ladder. Three months to ship something real, six on the outside. The last page is a welcome from the people who were already on the other side when you started.
If that is you, the book is for you. It's out now: builder-leader.com, or buy it on Amazon.
Builder-Leader: The AI Exoskeleton That Crosses the Gap.