Fictionary gives you a deep, scene-by-scene story edit of a single book, the kind of structural read a developmental editor does. StoryHelm checks something Fictionary does not reach: whether your world stays consistent across an entire series, every book measured against one Canon. If you write standalone novels, Fictionary may be all you need. If you write a multi-book series, the two tools answer different questions, and the gap between books is the one StoryHelm was built to close.
Fictionary StoryTeller is a structural editing tool for a single manuscript. You import a draft, it splits it into scenes, and then it walks you through 38 story elements scene by scene: the point-of-view character, what each scene reveals about character, plot, and setting, where the scene opens and closes, whether it moves the story forward. It draws a visual story arc and a manuscript map so you can see your structure at a glance, and it flags scenes that may not be pulling their weight. Authors and editors use it to turn a messy draft into a clear developmental edit without printing the whole thing and marking it up by hand.
Fictionary is not a prose generator and does not pretend to be. It reads what you wrote and helps you see the shape of your own story. For a writer wrestling a single novel into structural order, it earns its place.
The things Fictionary does well are the things a single-book edit should do well.
Every scene gets evaluated against the same checklist: entry hook, exit hook, the scene goal, the conflict, the change. When a scene in chapter 14 has no clear purpose, you see it next to the scenes around it, not buried in a 90,000-word file. This is the work that usually lives in an editor’s margin notes, made systematic.
Fictionary tracks which character holds the POV in each scene and surfaces where a viewpoint slips or where a named character vanishes for too long. Within the manuscript you imported, that visibility is useful and concrete.
The story-arc graph and manuscript map turn structure into something you can read at a glance: a sagging middle becomes a literal dip on the chart, a rushed climax a spike that arrives too early. Seeing the curve is often what makes a structural problem fixable.
For one book, Fictionary is a respectable substitute for, or a complement to, a developmental editor. It is built for authors and editors who care about craft, and it treats the draft seriously.
Fictionary reads one book deeply. The questions that hide in a series live between the books, where a single-manuscript edit cannot see them.
Fictionary evaluates a manuscript, one book at a time, which is exactly its scope. The contradictions that wreck a series almost never live inside a single book. They live in the seams between books, and they only become visible when you hold all of them against one source of truth.
Consider a five-book fantasy series. In book one, the harbor town of Aldreth sits two days’ ride east of the capital. By book four, a character makes the same trip in an afternoon, because the author moved the geography in their head somewhere around book three and never reconciled it. Read alone, book one is fine and so is book four. Fictionary, opening book four on its own, has no reason to know what book one said: it sees a perfectly functional travel scene. The error is not in either book. It is in the disagreement between them, and that disagreement is invisible to any tool that reads one manuscript at a time.
The same thing happens with people and promises: an eye color that drifts between books, a side character whose name shifts a letter from one volume to the next, a vow sworn in book one and set up to cost the protagonist everything that is then quietly forgotten and never paid off. None of these is inventable from inside one book; no single-book edit, however careful, can catch a fact it was never shown. Readers do, though, and they catch it after the book has shipped.
StoryHelm starts where a single-book story edit ends. It reads every book you give it against one shared Canon and checks whether the whole series still agrees with itself. You can write in the built-in Scene Editor or import finished books drafted elsewhere. Four things it adds on top of a scene-level edit:
As books come in, StoryHelm extracts characters, places, factions, items, and events into structured Canon, the single source of truth for the series. Aldreth’s distance from the capital is recorded once. Maren’s eye color is recorded once. Every later book is measured against it.
The Coherence Guardian reads across all the books and flags name drift, timeline conflicts, trait contradictions, and geography that moved, with the exact book and chapter on each side. The Aldreth travel time, the gray-to-green eyes, the Tomas-to-Thomas rename: each comes back as a severity-ranked finding that points to both passages, so you can see the conflict and fix it.
The Series Atlas holds the shared canon and continuity across the whole series in one place, so the things that span books, a faction’s allegiances, a character’s arc, the timeline of major events, stay legible as the series grows past the point any one person can hold in their head.
Plot DNA tracks intensity, stakes, and thread coverage, and the foreshadowing analysis follows promises forward. The vow sworn in book one that should have detonated in book four shows up as an open thread that never paid off, the kind of orphan a per-scene checklist on a single book cannot surface.
Import book one through book five, or write them in the built-in Scene Editor, and StoryHelm runs each manuscript through a multi-agent analysis powered by Claude. It extracts your Canon, then measures every book against it and hands back findings that name the exact book and chapter on each side of a conflict. You write every word; the system never touches your prose. See what an AI continuity check actually does for the full walkthrough.
Both read what you wrote rather than writing it for you. They differ on scope: one book, deeply, versus a whole series, against one Canon.
| StoryHelm | Fictionary | |
|---|---|---|
| Primary job | Series-wide continuity and craft analysis | Single-book structural story edit |
| Scene-by-scene story elements | Partial: per-scene Plot DNA tracking intensity, stakes, beats, and thread coverage | Yes: 38 story elements, scene by scene |
| Visual story arc for one book | Yes: per-scene tension and intensity curves with filler-ratio flags | Yes: story arc and manuscript map |
| Cross-book continuity analysis | Yes: Coherence Guardian + Series Atlas | No: built for one manuscript |
| One shared Canon across the series | Yes: extracted from every book | No: per-manuscript story bible |
| Foreshadowing payoff across books | Yes: open-thread tracking | No: scene-scoped to one book |
| Drafts / generates prose | No: never, by design | No: reads, does not write |
| Cost | From $14/mo · Series tier $59/mo · one-time $99 Manuscript Audit | Subscription, single-book focus |
StoryHelm offers a 14-day free trial with no card. The Series tier is $59/mo for unlimited books under one Canon, and a one-time $99 Manuscript Audit gives you a full read without a subscription commitment.
For most authors the right answer is one of these, not both, and which one comes down to whether your books stand alone or build on each other.
If you write standalone novels and want the deepest single-book edit short of hiring a developmental editor, Fictionary is a strong, fair choice. If you write a series, the moment you publish book two you inherit a problem no single-manuscript edit can see: keeping book two honest to book one, and book five honest to all four before it. That is the problem StoryHelm was built for.
No. Fictionary does a scene-level story edit of one book very well. StoryHelm checks consistency across a whole series against one Canon, which a single-manuscript tool is not built to do. Some authors will use one, some the other, and a few will use both at different stages.
It does per-scene work through Plot DNA, intensity, stakes, beats, and thread coverage, but that is not its headline. Fictionary’s 38-element scene checklist is more exhaustive for a single book. StoryHelm’s edge is the cross-book layer that sits on top of per-scene data.
If your books are a connected series, yes, because Fictionary edited each one in isolation. The contradictions between book one and book four were never in its scope. StoryHelm reads all of them against one Canon and catches what only shows up when the books are compared.
Never. StoryHelm reads and analyzes; it does not draft, rewrite, or generate the author’s prose. You write every word. The AI checks the world, the timeline, and the threads, and hands you findings, not sentences.
A 14-day free trial with no card. Plans start at $14/mo, the Series tier is $59/mo for unlimited books under one Canon, and a one-time $99 Manuscript Audit gives you a full read with no subscription.
A fair field guide to the tools that catch cross-book contradictions, and how to tell a story edit from a continuity check.
ReadA side-by-side hub of the tools series authors actually evaluate, organized by the job each one is built to do.
ReadA scene-level edit reads each book alone, so it cannot see the harbor that moved, the eye color that drifted, or the vow that never paid off. StoryHelm holds every book against one Canon and points to the exact book and chapter on both sides of the conflict, before a reader spots it in book four and leaves the review that follows your box set everywhere.
Request a founding seat