My Real Workflow for Writing a Book with AI
I just published a short nonfiction book, and yes, I used AI to help write it. Not in the way most people think, and not in the way that’s flooding Amazon with empty books right now.
I didn’t prompt “write me a book” and hit publish. That approach produces clean, readable content that sounds right and delivers nothing. I’ve bought enough of those to recognize the pattern quickly, and that experience is the reason this project exists in the first place.
This started with a real idea. I’ve bought over 1,000 nonfiction books on Kindle, and after a while, the patterns become obvious. Some go deep and hold up. Others look solid on the surface and fall apart within a few pages. That gap became the core of the book, a fast filter to avoid wasting time on weak nonfiction, and it shaped how I approached the entire writing process.
I built the structure myself. Outline first, then chapters, then flow. Each section had a job and a clear connection to the next, so I always knew what the piece needed to do before I wrote a single paragraph. AI came in after that, not before, and I used it in controlled passes to expand rough notes into readable sections, tighten language, and check consistency across chapters. It helped me move faster, but it never made the decisions.
The real work was editing, and this is where most AI-assisted writing falls apart. AI produces smooth writing very quickly, which makes it easy to confuse flow with substance. I don’t trust that. I stop on every section and ask a direct question. Does this actually say anything? If a paragraph feels interchangeable, I cut it or rewrite it until it carries weight.
I also ran analysis passes using my own tools to flag repetition, weak verbs, and generic phrasing. That gave me clear targets, but the fixes were still manual or handled with very specific prompts. That combination matters more than the generation step, because it’s where the difference between usable and empty shows up.
The final book is short, about 7,000 words, but it’s tight. No filler, no padding, no stretched ideas. That’s a deliberate choice, and it reflects how I think about nonfiction now. I care more about signal than volume.
Here’s my takeaway after doing this. AI makes it easy to produce a book, but it does not make it easy to produce a good one. If anything, it raises the standard for editing because the baseline output already looks finished. I’ve seen what happens when people skip that step, and I’m not interested in publishing something that just looks complete.
So the decision is simple. Use AI as a structured collaborator and bring your own judgment, or accept that the output will be shallow, no matter how polished it looks. That’s the tradeoff.
If you want to see what that looks like in practice, I put the system into a short book called Stop Buying Bad Books: A 60-Second System for Finding Nonfiction That Actually Delivers. It’s $2.99, and if you read nonfiction regularly, it will save you more than that the first time you skip a bad buy.
