After I read @Ry Mac post about the advice he gave his dad โ record him talking about his life, let Claude turn it into chapters. I recognized every step of it. I had been running that exact loop for months; it just wasn't the whole story yet. For most people, a "team of AI workers" sounds like an org chart somebody whiteboarded before touching a keyboard โ one for content, one for design, one for ops, planned end to end, then built to spec. Mine didn't happen that way. Every worker in it got built only after the work already in front of me hit a wall without one. Here's the actual order, because it's more useful than the summary version: โข A transcriber, first. Spoken audio to clean text, nothing else. โข A content editor, right after. Takes that text and shapes it into something a chapter can be built from. โข A designer, once the finished book needed a cover. โข A builder, once it needed somewhere to live. โข Someone for marketing, once it needed people to actually find it. Five workers. None of them existed until the step before them stalled. What started all of it wasn't a strategy. It was a stuck book โ one of several, half-written, going nowhere on their own. The method behind the first two came from Jake Van Clief ICM method: one worker, one job, never one assistant doing everything passably. The loop those first two ran was simple โ a writing-workshop technique for answering a book's questions out loud instead of staring at a blank page, dictate the answer, let the transcriber convert it, let the editor refine it. Five books came out of the actual sequence above, in forty-five days. The org chart, if you want to call it that, got drawn after the fact, never before it โ the same order everyone assumes runs backward. I also got inspired by the idea of building skills, so I had my team get to work, since that was what we did and I set out to make this so others could have a start: a Book-Ghostwriting Consultant, built the same way as everything above it.