The book

Builder-Leader

The AI Exoskeleton That Crosses the Gap

An operator's manual for the senior executive who already knows AI matters and does not yet know what to personally do about it on Monday morning. Short enough to finish over a week of commutes. Sharp enough to quote in a board meeting. Honest enough to argue against two popular positions at once: that AI is just a chatbot, and that AI is an imminent superintelligence.

By the end of the book the reader has installed Claude Code, shipped something through their own harness, and knows why their existing leadership capital compounds with the new practice rather than getting replaced by it.

Reserve your copy → Read the preface Vote on the cover

Builder-Leader

The AI Exoskeleton That Crosses the Gap

Justin Johnson

Who this book is for

Senior executives who don't code, have read the AI think pieces, and still need a practical first move.

The reader qualifier is surface area times daily-decision density, not title. Core reader: F500 ED / VP / SVP; mid-cap C-minus-1 and up; founders and senior execs at startups. F500 CEO / CFO / COO tier is explicitly outside scope — at that altitude, augmented leadership is the correct frame. The book engages that counter-position fairly in Chapter 9.

The book draws heavily from a coherent intellectual tradition: Karpathy, Mollick, Fowler, Anthropic's research posts, the operator community on X and HN. Counter-traditions are engaged where they make load-bearing arguments.

Table of contents

A three-act ladder.

Front matter

Preface — Welcome from the other side

Opens on a specific weekend in April 2026 where the author shipped five artifacts in two days, none of them by typing code himself. Names the institutional friction that pigeonholes builder-leaders, and the identity undercurrent that runs through the rest of the book.

Part One — The Gap

Two Groups Speaking Past Each Other

Diagnoses the build gap between two populations of AI users. Karpathy's two-groups thread as opener. Routes around the AGI camp. Honors the skeptic case where it is partially right.

What You See From the Other Side

What builder-leaders see that other leaders do not. Karpathy autoresearch as an operating pattern. Mollick three-tier (model, app, harness). Group 3 inside Group 2. Three sourced failure modes: prompt doom loop, pilot purgatory, silent failure.

Why Your Org Can't Cross Institutionally

The pilot-to-production ratio. Why centers of excellence struggle. Why AI literacy training under-delivers. Governance-first counter engaged on its own terms. You cannot lead what you have never worn.

Part Two — The Exoskeleton

The Harness and What's In It

The moat argument: harness, not model. Six components — skills, memory, agents, hooks, MCP servers, sensors-and-gates. Harness eating SaaS. A non-coder-friendly tour of what an operator actually runs.

The Builder Inside

What the human inside the exoskeleton actually does. Against AI-as-autopilot and AI-as-junior-employee. Six builder practices. The five leadership primitives you already use, transferred to a multi-agent harness.

Part Three — The Crossing

Start With Claude Code

Weeks 1-2. The on-ramp. Why Claude Code specifically. The first two weeks. The minimum viable practice. The trap of trying to build the perfect setup before doing any real work.

Building Your Personal Harness

Weeks 2-6. What to add and when. How to discover skills by noticing what you do twice. Memory without overengineering. When to spawn an agent. By the end, the reader has shipped something real.

From One Operator to a Team

Weeks 6-10. What changes when the second person joins you. Shared rigs, shared memory, five new failure modes. Why most orgs skip this step and go straight to platform, and why that fails.

Leading From the Other Side

Month 3 and beyond. Builder-leader as permanent role. Augmented-leadership counter engaged. Scope concession (ED / VP / SVP, C-minus-1, founders — not F500 CEO). Identity resolution. Archetype transfer audit.

Back matter

Epilogue — Welcome

A short closing. The reader is welcomed to the existing community of operators who were already on the other side when they started. Not a summary. The posture comes through in the voice.

Reading sample

The preface, in full.

Roughly 1,800 words. The setup of the book in the author's voice, with the central claim and the friction the reader will run into named directly. Read it before you decide whether the book is for you.

Read on GitHub → Download PDF

"Two years ago, my kids showed me a website called 11:11 Make a Wish. You typed a wish at 11:11 and the site would hold it for you. They loved it. I loved that they loved it. So I decided to make my own version for the App Store. I called it 11:11 Make a Fish. A fish, because fish were funnier than wishes to an eight-year-old. It took me the better part of two weeks."

"This weekend, in April 2026, I did five things. I started writing this book. I wrote a blog post explaining a machine learning system we built for estimating which genetic variants cause cancer in patients. I produced the complete DNA sequence analysis pipeline that blog post describes, not as a demo but as the real thing. I shipped a commercial domain discovery tool called Nymio, built across a multi-model backend, one weekend from nothing to a working product. And I built a multi-agent portfolio system that would previously have been a multi-month engineering effort."

"I did not write any of the code."

From the preface of Builder-Leader: The AI Exoskeleton That Crosses the Gap.

Reserve your copy

Hardcover ships in 2026.

Drop your email and we will tell you the moment it ships, on Amazon, Bookshop, Apple Books, or directly. The audiobook is narrated by the author. No newsletter, no spam.

Reserve your copy →