Chapter by chapter
Twenty years, a thousand-plus stages, a new presentation every time — and why this book is a letter to the people who will inherit what we build.
The framework it became: Move First
-
→
Write down the technology bets you're currently NOT making, and what waiting costs (the Waiting Tax).
-
→
Pick the one capability that feels optional today and will be table stakes in three years.
Go deeper: The Bet I Made in 2008
The wager on the future that shaped everything after it — conviction placed before consensus.
The framework it became: Move First
-
→
Size one early bet so a miss doesn't kill you — then place it.
-
→
Set kill criteria in writing before you start, so early investment never becomes sunk-cost theater.
Go deeper: The Bet I Made in 2008
Platform shifts feel obvious in retrospect and invisible in the moment — and waiting has a cost the spreadsheet never shows.
The framework it became: The Waiting Tax
-
→
Price the do-nothing option honestly: lost compounding, lost talent, a market that moved.
-
→
Name the fear out loud — being scared and all in at the same time is what being awake feels like.
Go deeper: Scared and All In: Both Can Be True
The hypothesis, the build, the three questions, the hard conversations — rebuilding the company around the future instead of defending it against it.
The framework it became: The Intelligence Layer
-
→
Sequence it: infrastructure first, intelligence second, agents third — the org finds its true size on the other side.
-
→
Tell your people the truth before the market does; give everyone an honest chance to evolve with the rebuild.
Go deeper: From 320 People to 38 (the outcome)
The industry's advisors sold an expired playbook — WordPress sites, a blog post a month, 2018 SEO — while PE, retailers, and utilities changed the game.
The framework it became: The Agency Reckoning
-
→
Make every advisor show you what they've automated in their own business — production, not slides.
-
→
Demand the buyer's standard: no lock-in contracts, own your assets, visible components instead of invisible retainers.
Go deeper: The Course They Were Told to Stay
Compounding rates of change, superficial knowledge, rookies with the wrong tools, and a selection problem — the stuckness is structural, not technological.
The framework it became: The Intelligence Layer (vs. the chat tab)
-
→
Stop asking 'which AI tool' — ask 'can our systems see each other, and who owns our architecture?'
-
→
Run the audit before the automation: a broken process automated is broken outcomes at machine speed.
Go deeper: It's 2026 and AI Still Isn't ChatGPT
Real operators — Lemonseed, Contractor in Charge, OnePath AI, Trade Rated — proving that the technology story and the human story are the same story.
The framework it became: Systems & Soul
-
→
Apply the side-of-the-glass test to every system: does it genuinely help the customer, or just cut your costs?
-
→
Hold both scoreboards at once: the economics of tokens and the obligations to people.
Go deeper: Your P&L Still Bills Hours
One shift seen from six seats — the labs, the platforms, the consumers, marketing, operations, and the employee — so no single vantage point fools you.
The framework it became: The SME Inversion (the employee view, completed)
-
→
Ask your best person: would you rather be replaced by a system, or be the one who builds and runs it?
-
→
Make encoding what you know a promotion — system ownership, output-based pay, steward seniority.
Go deeper: The SME Inversion
Voice becomes the assistant, the customer becomes the agent, attribution collapses, you manage agents instead of people, the website becomes the avatar.
The framework it became: The Prediction Ledger + The Entity Brand
-
→
Build the entity layer now — machines can't recommend what they can't verify (start at /entity.md, yours to copy).
-
→
Score the chapter: every one of these calls is on the record with a review date in the Ledger.
Go deeper: The Prediction Ledger, Entry 001
What AI could have done — the human stakes of the systems we build, told through one person.
The framework it became: The Kitchen-Table Standard
-
→
Build every system as if someone you love depends on it — because somewhere, someone does.
Go deeper: The Client-First Inversion