Plan the book here.
Write the draft there.

Scrivener is the specialist, and it earns it: The binder lets you hold a book as hundreds of small documents instead of one enormous file, so moving chapter twelve is a drag rather than a surgical operation. Compile turns that pile into a manuscript, an ebook, or a print-ready file. It is sold as a one-off licence rather than a subscription, which is why so many writers own it a decade later. If you are drafting a long book, this is the serious answer.

Word and Google Docs still write most published books: This is not nostalgia. Track changes is the industry standard for editing, agents and publishers ask for .docx, and Google Docs handles comments and co-writing better than almost anything. If you write in Docs and hand your editor a Word file, you are doing what most published authors do.

Distraction-free apps suit some writers and not others: Ulysses, iA Writer, and the rest strip everything away so there is nothing but the sentence. For writers who fiddle with formatting instead of writing, that is transformative. For writers who need to check chapter four while drafting chapter nine, the same emptiness is friction. Know which one you are before you buy.

Storyflow is not on this list, on purpose: There is a document editor and you can draft a scene or a section in it beside the board. But it has no binder, no compile, no manuscript formats, and no ambition to have them. Anyone who has written a book will spot a canvas claiming to replace Scrivener in about four seconds, so we are not going to make the claim.

You can see the whole book at once: A binder shows you a list of chapters. A canvas shows you the book laid out in space, with the long chapters visibly long, the thin section visibly thin, and the gap in the middle visibly a gap. Structural problems are spatial, and they only surface when the whole thing is in front of you.

Reordering is free: Trying a different chapter order in a manuscript is expensive enough that most writers do not test the idea. On a board it is a drag, so you actually try the three arrangements you were arguing with yourself about and keep the one that works.

Threads run as parallel tracks: Put each subplot, character arc, or recurring argument on its own horizontal track under the chapter spine. An empty stretch in a track is the thread your reader will forget about, and it is invisible in a list and obvious on a canvas.

Everything the book needs sits together: Research, source notes, character material, timelines, maps, and visual references live on the same surface as the plan, one scroll from the chapter that uses them. No folder archaeology at the exact moment you had momentum.

Chapter logic, not character arcs: A non-fiction book works when each chapter earns the next one. Lay the chapters out and read only the claims, in order, and you find out quickly whether the argument builds or just accumulates. That reading is nearly impossible inside a two hundred page draft.

Source management beside the claim it supports: Pin each source, quote, interview, or dataset next to the specific claim it backs. When a chapter has a claim with nothing pinned to it, you have found the paragraph a reviewer will challenge, months before a reviewer sees it.

Threads that recur across chapters: Case studies, running examples, and framework terms behave exactly like subplots. Give each one a track and you can see where it is introduced, where it returns, and where you quietly dropped it.

Reference management is still a separate job: Storyflow holds sources as material you can see and arrange, not as a citation database. If you need formatted bibliographies and BibTeX, Zotero remains the right tool and the two work fine side by side.

It structures, it does not ghostwrite: The AI lays out chapter structures, suggests what might sit between two sections, drafts beats for an act or arguments for a chapter, and flags where a thread goes quiet. It is not here to produce prose you did not write, because a book written by a model reads like one.

Your whole canvas is the context: Because it can see the board, suggestions fit the book you are actually writing rather than a generic one. Ask what is missing before the midpoint, or which chapter is carrying too much, and you get an answer about your material.

Iterate without losing work: Re-prompt as often as you need. Cards you have written and placed stay exactly where they are while the AI builds around them.

No software has ever finished a book: Worth saying plainly, since half the market implies otherwise. Every tool on this page, ours included, removes friction from a job that is still done by a person sitting down for a very long time. Choose the one that gets out of your way and then go and write.