The useful question is not whether to use a model. It is which parts of making a book are the parts a reader is paying for, and those are not evenly distributed. Nobody buys a book for its chapter ordering. They buy it for the two hundred specific things the author knows, and a model does not know any of yours.
What it is good at, and what it is not
| Task | Worth handing over | Why |
|---|---|---|
| Outlining and re-ordering | Yes | Structure is a solved shape, and a second opinion on it is cheap |
| Summarising your own notes | Yes | You supplied the material; it is doing arrangement |
| Drafting a passage you have already thought through | Mostly | Faster than a blank page, and you know what it should say |
| Tightening prose you wrote | Yes | Cutting is where models are genuinely strong |
| Chapter summaries, blurbs, index terms | Yes | Derivative by nature, and tedious by hand |
| The argument of the book | No | This is the thing being sold |
| Anecdotes and examples | No | It will invent plausible ones, and they read as invented |
| Facts, figures, citations | No | It will produce confident, wrong, well-formatted ones |
| Your voice | No | Averaged prose is what the reader recognises and closes |
How model prose gives itself away
Readers may not be able to name it, but they can feel it, and reviewers name it immediately. These are the specific tells, and every one of them is fixable in an editing pass.
- Uniform paragraph length. Four sentences, every time, for nine pages. Real writing varies because real thoughts do.
- The hedge before the point. "It's important to note that", "While there are many approaches". Delete the run-up and start at the point.
- Threes. Three adjectives, three examples, three items in every list, whether or not the world came in threes.
- Abstraction where a detail belongs. "Businesses often struggle with communication" instead of the meeting in March where nobody had read the brief.
- Summary paragraphs that restate the section they are at the end of, adding nothing.
- Confident specifics with no source. A percentage, a year, a study. These are the dangerous ones, because they look like the good parts.
The last is worth separating out. Everything else on the list makes a book boring. That one makes it wrong, and your name is the one on the cover when a reader checks.
A workflow that produces something publishable
- Write the outline yourself, then ask for holes in it. Its criticism of your structure is more useful than its structure.
- Dump your raw material into a file — notes, transcripts, the emails where you already explained this to somebody. This is the part that is actually yours.
- Draft chapter by chapter, from your material. A whole book in one request is how you get nine chapters that each restate the same three ideas.
- Rewrite every passage in your own words at least once. Not editing — rewriting. This is where the voice comes from, and it is not optional.
- Add the specifics only you have. The number, the client, the mistake, the thing that failed. One per section is enough to change the whole register.
- Check every factual claim against a source you can name. Anything you cannot verify comes out; there is no third option.
- Read it aloud. Averaged prose survives silent reading and falls apart in the mouth.
- Then format it, which is the one step where the machine's output happens to be in exactly the right shape.
The convenient accident: it writes Markdown
Ask a model for a chapter and you get headings marked with #, emphasis in asterisks, lists as hyphens. That is Markdown, and it means the draft is already structured text rather than a wall of Word formatting somebody applied by hand at three in the morning.
The practical consequence: paste it into one .md file per chapter, keep the heading levels consistent, and the manuscript is ready to typeset without a conversion step. Combining Markdown files into one book covers the assembly, and headings as book structure covers the one rule that matters — # for chapters, ## for sections, no exceptions, because that hierarchy becomes the contents and the EPUB navigation.
Two things to strip as you go: the smart quotes and dashes will be inconsistent, which smart quotes and dashes fixes in one pass, and the em-dash habit is worth noticing before a reviewer does.
What the stores and the law require
This part is not stylistic, and it changes, so treat it as the shape of the rules rather than legal advice — check current terms before you upload.
- Amazon KDP asks you to declare AI-generated content when you publish, and distinguishes content that was generated from content that was AI-assisted — where you wrote it and used a tool to edit or refine. The declaration is not published on the listing, but answering it dishonestly is a terms violation.
- Purely AI-generated material is not copyrightable in the US. Human authorship is the requirement; the human contribution in a mixed work can be protected, the machine-generated portions are not. A book you rewrote and shaped is a different case from a book you prompted.
- Some stores and services cap volume, and there are limits on how many titles an account can upload in a day. These exist because of exactly the behaviour you should not be copying.
- AI-generated cover art carries its own questions, separately from the text. If in doubt, commission or license the cover — it is the cheapest part of the book to get unambiguously right.
What is still entirely yours
None of the above touches the parts of publishing that decide whether the book sells, and a model is no help with any of them because they all require knowing your reader.
- The description. The single highest-leverage page of copy you will write — how to write a book description.
- The cover, which is judged at 100 pixels wide next to forty others — ebook cover dimensions.
- Categories and keywords, chosen against the competition you can actually place against — book metadata.
- The price, and what it says about the book — how to price an ebook.
- Where you sell it, and what each channel takes — where to sell your ebook.
Then export it like a real book
A draft written faster still has to arrive as a finished object. The Markdown becomes a typeset PDF and a reflowable EPUB with the front matter in place, the type set once, and the page breaks where you put them: Markdown to PDF and Markdown to EPUB are the two exports, and front and back matter is the furniture readers only notice when it is missing.
The uncomfortable summary is that a model removes the slowest part of writing a book and none of the hard parts. It will get you a complete draft in a fortnight, and the fortnight after that — the rewriting, the checking, the specifics — is what separates a book from the several hundred thousand that were uploaded without it.