The living edition

What’s changed

Everything added since the printed book, version 11.42, newest first.

Version 11.43

A chapter your copy does not have

Version 11.44

A chapter your copy does not have

Nine Rules From a Deal I Lost

Nine Rules From a Deal I Lost: new epigraph

A single quotation now opens the chapter, before the "New in the living edition" line: "Experience keeps a dear school, but fools will learn in no other." It is credited to Benjamin Franklin, Poor Richard Improved (1758). The rest of the opening is unchanged.

Why it matters. The chapter is nine rules taken from a deal that went wrong, and the quote tells you how to read them. These are lessons that cost something, not tips collected from the outside. It also sets the tone for the story that follows, where the prospect decides to build it himself and the loss is the teacher.

What to look at. How the quote lines up with the first paragraph: "I lost one recently." Then ask whether each of the nine rules reads as something the loss taught, or as advice that would have been true anyway. The rules that feel earned are the ones worth taking back to your own pricing and proposals.

Read it

Notes on Sources

Notes on Sources: two new entries, "One Mind, Not Many" and "Nine Rules From a Deal I Lost"

Two sources are added to the notes. "One Mind, Not Many" now cites Proverbs 4:7 in the King James Version. "Nine Rules From a Deal I Lost" cites Benjamin Franklin's preface to Poor Richard Improved (1758), which was later reprinted as "The Way to Wealth." They sit in book order, the first after Chapter 6 and the second after Chapter 9.

Why it matters. Until now the notes covered only the numbered chapters, so these two pieces had nothing behind them. Now both are cited the same way the chapters are. If a line in either one stuck with you, you can find where it came from instead of taking it on faith.

What to look at. The Franklin entry, which is the more involved one. It points to the 1758 preface under its original title and also names the later title most people know it by. It then gives the volume and page range in The Papers of Benjamin Franklin, so you can read the full text rather than a trimmed version.

Read it

Version 11.45

One Mind, Not Many

Chapter: One Mind, Not Many: three ways knowledge works, and a new section, Killing the drift

Two additions and a reworded closing. Early on, a short passage says there are now three ways work gets done: by hand, by rule, and by judgment. It says the replacement mindset uses judgment to build more rule-following, faster. After the story about the machine misjudging where your line runs, a new section, "Killing the drift," takes up what happens when one mind starts a new conversation with nothing. It compares minutes, checklists, and locks that stop the wrong thing from happening. The closing pattern now says to write down what the mind must remember and lock in what it must never get wrong.

Why it matters. The chapter used to argue that one mind with the whole picture avoids the drift that ten agents create. This version admits the catch: one mind only holds the picture while it is looking at it. The new section says the old business disciplines (minutes, checklists, audits, sign-offs) are what make the new mind trustworthy, and it separates reminding from locking. It also says the author's own conversations drifted apart, and that reminding them did not fix it. What fixed it was taking the choice away. The three-ways passage also gives a sharper reason the replacement mindset tops out at "the same thing, cheaper."

What to look at. The split between a record that reminds and a rule built so the wrong thing cannot happen, along with the pointer to Chapter 14 for the example of one rule given about fifty times. Also look at the last paragraph of the section: reading is not the same as following, so the things that matter most get locked in. The reworded pattern at the end carries the same advice in one line.

Read it

Version 11.46

Chapter 2: What Actually Got Cheap

Chapter 2: the structure list grows, with backups and a feedback channel

The list of what real, AI-built software needs underneath it now has two new items: automatic backups kept somewhere separate, and a built-in way for the people using the software to report problems and suggest improvements, with every report tracked until it's answered. Three existing items were sharpened too. The database now sits behind a secure login, the testing copy is where real people try the work before it goes live, and the security checks now include updates that close the weak spots they find. The closing paragraph gains two sentences to match.

Why it matters. The chapter's argument is that the structure is what makes AI-built work hold up, because it catches the mistakes the AI still makes. Before, the list covered catching errors before and after launch. The backups add protection against the loss that nothing else on the list can undo, so a bad day stays just a bad day. The feedback channel adds something no alarm can give you: the people using the software telling you what is wrong or missing. Together they widen "the structure" from keeping the build safe to keeping the software looked after once people depend on it.

What to look at. The two added sentences in the paragraph after the list: "The backups mean a bad day stays just a bad day, and the people using it tell you what no alarm can." Then check your own builds against the list. Ask whether your data is backed up somewhere separate, and whether the people using the software have an easy way to tell you what's wrong, with someone answering each report.

Read it

A Book That Isn't Finished

A Book That Isn't Finished: rewritten as a guide to the living edition

The chapter no longer asks you to scan a code and enter the printed version number to see what changed. It now speaks to someone already reading the living edition and lays out what that means in five points: it keeps changing, it keeps growing, it answers back, it comes in the length you want, and it was built by the thing it describes. Two things are new to the book. There is a fifteen-minute version with one page per chapter, written by John-Scott. And chapters with a letter in place of a number were written after the printing and exist only here. The "baby who just learned to roll over" passage stays, now under a "why go to the trouble" question, and a second reason follows it.

Why it matters. This is the chapter that tells you what kind of book you are holding, and the old version described a different arrangement. Your printed copy was a snapshot you checked against a code. Here, every page shows its version and whether it has changed since the printed edition, so you no longer need to look anything up. The summary version also changes how you can use the book. You can start with the short one and move to the full chapter, or the reverse. The new closing reason is the clearest statement of purpose in the book. The easy move with AI is a familiar book made faster. The question here is what a book can be when changing it costs almost nothing.

What to look at. The lettered chapters, which are the clearest sign of what the printed edition lacks. Look also at the fifteen-minute version, if you are the kind of reader who usually takes a summary. And look at the last two paragraphs, where the book says this is a first answer and that you will see the next one here before anywhere else.

Read it

Version 11.47

Chapter 2: What Actually Got Cheap

Chapter 2: first example line reworded in "A few ways to say it"

The first of the three sample lines for explaining the speed gain to a client has been rewritten. It used to read "We didn't make your old site faster. We stopped building on it." It now reads "We didn't tune up your old site. We rebuilt it without the platform that was slowing it down." The other two lines are unchanged.

Why it matters. The old line was clever but left the client to guess what "stopped building on it" meant. The new one says plainly what happened: the site was rebuilt, and the platform was the cause of the slowness. That is an easier thing for a client to repeat to someone else, and it frames the work as removing a problem rather than polishing around it.

What to look at. The new line makes a specific claim: the platform was what slowed the site down. Use it when that is true of the client's site, and reach for one of the other two lines when it is not. Check that the wording you have been using in pitches still fits.

Read it

Version 11.48

A Book That Isn't Finished

A Book That Isn't Finished: new paragraph, It lets you check me

A new paragraph in the list of what makes this book different, sitting between "It comes in the length you want" and "It was built by the thing it describes." It points back to the claim in Chapter 2 that you can't tell which of our sites were built by AI and which by hand, and it gives you a way to test that yourself: ten sites, one at a time, and you say which is which.

Why it matters. Chapter 2 asks you to believe something that sounds too convenient coming from an agency owner. This paragraph stops asking for belief. Your answers are added to everyone else's, and the running score is posted whichever way it comes out. That means the book can be shown wrong about its own claim, in public, and it says so up front. It fits the rest of this chapter's argument that a living book is the honest way to write about something moving this fast.

What to look at. The sentence about the score being posted "whichever way it comes out." That is the commitment. Also the last line: if you want to talk about what you saw, there is a way to do that, and it comes to me. Take the test with Chapter 2 fresh, then see whether your results agree with what I wrote.

Read it

Version 11.49

About the Author

You can reach John-Scott directly now

What changed. About the Author, at the back of the book, now carries a link to John-Scott's LinkedIn profile.

Why it matters. The printed edition ends with a bio and no way to answer it. Everything else in this book argues that the work is won by the person standing behind it, which is a strange thing to say on a page that gives a reader nowhere to go.

What to pay attention to. If something here maps onto what you are building, say so there. The arguments in this book have been changed by readers before, and the ones that changed it arrived as a message, not as agreement.

Read it