Guide

How to make an AI-written book not sound like AI

Readers no longer need a detector; they can feel it in a paragraph. We counted the tells on a real book, changed the pipeline, and counted again. Here is what moved the numbers.

Neubook Write · 3 September 2026

The tells, as of 2026

The clichés have shifted. Em dashes and "delve" are weak signals now; the strong ones are structural. The Economist's widely shared analysis found cadence uniformity, sentence after sentence of the same length and shape, to be the most persistent tell. The others, in rough order of how fast a reader notices them:

• The reversal. "It isn't about doing less. It's about doing what matters." Once a chapter, fine. Seventeen times in a short book, a fingerprint.
• Second person on repeat. "You've seen the pictures. You already know the feeling. You've got the list."
• Chapters that summarise themselves. An ending that restates the chapter, often beginning "You now have…".
• Bold takeaways inside paragraphs. Blog formatting, not book prose.
• Tidy tricolons. "Fast, reliable, and affordable." Lists of three whether or not there are three things.
• Rhetorical questions that the next sentence answers with a slogan.
• No specifics. No street, no price, no Tuesday, no name.

What we measured

We ran one brief, a meal-prep guide for parents of picky eaters, through a plain one-prompt pipeline and through Neubook Write, then counted the patterns per thousand words.

The seven changes, in the order they matter

1. Interview the author before planning

Nothing makes prose human like details a model could not invent: the forty containers that never got used, the daughter who ate only beige food for a winter, the $210-a-week shop that became $160. Four to six questions written for the brief, and each answer assigned to one chapter, not sprinkled everywhere.

2. Plan first, and let the author edit the plan

A book written chapter by chapter with the whole plan in view does not repeat its introductions or contradict itself. Showing the plan to the author before writing catches the wrong book early and costs nothing.

3. Give every chapter its own opening and closing move

A scene, a number, a confession, a line of dialogue, an object, a plain claim. Never the same opening twice in a row, never any opening more than twice in a book. Endings: an image, one instruction, a line of dialogue, a return to the opening. Never a recap.

4. Write a house style and hand it to the writer

A short, blunt rulebook: no reversals, no fragment stacks, no bold in body text, a list of banned phrases, at most two em dashes a chapter, vary paragraph length on purpose, prefer a brand and a day of the week to an abstraction, never invent a statistic or a quotation.

5. Then hand the same rulebook to an editor

A second, cheaper model rewrites each draft against the rules, keeping meaning, facts and length within ten percent. This is where most of the numbers above moved. It costs about a fifth more in tokens.

6. Strip what slips through

A deterministic pass removes bold from body paragraphs and flags anything the editor missed. Models are inconsistent; code is not.

7. Give the book a front and a back

A dedication written from the interview, an introduction that refers to real chapters, a conclusion that is not a summary, an about-the-author that invents nothing. Readers judge a book by whether it looks like one.

What still needs a human

All of this produces a strong first draft that reads like a person. It does not produce your book until you read it and cut what you would not say. That pass takes an evening, and it is the difference between a book and a product.