The short answer: the real difference is snapshot versus tracking. Publisher Rocket is typically a one-time purchase that answers keyword and category questions when you sit down with it. BookBeam is a subscription whose distinguishing feature is watching books and categories over time. Research once per book and never look again: Rocket. Running launches and ads and needing to see movement: BookBeam. Pricing for both is on their own sites and we do not track it. Both describe published books — which is the thing neither is built to see past.
Keyword research with competition scoring, category research at a granularity Amazon's browse tree hides, ads keyword lists. You buy it once and use it per book. There is no ongoing cost and no ongoing signal.
Rank curves over time, competitor launches as they unfold, review movement, your own title's decay after a promo. This is information a snapshot structurally cannot give you, and it is the reason to pay a subscription rather than buy once.
Both are anchored to books that exist. One photographs the shelf, the other films it. Neither can show you the book that is missing from it — the premise readers describe in reviews and BookTok comments and then never find, which has no rank to track and no keyword to score.
Here is the distinction that matters, and it is not a slight on anyone's tool. Keyword and category research answers how do I get this book found. It assumes the book exists. Tropesmith answers a question that comes earlier and that no keyword tool attempts: which story do readers keep asking for and not getting. We count individual reader requests — a real person, in a review or a comment or a BookTok video, describing a book they want and cannot find — classify each one by trope, and score it against what the shelf actually supplies in that lane. Tropesmith reads a registry of 231,291 books, 2,679,139 Goodreads reviews, 67,499 book–trope tags across 11,575 fully tagged titles, and 721,971 classified reader requests, scored across 138 demand lanes — plus an hourly scan of 554 BookTok hashtags (72,641 videos logged, 27,618 reader requests read from BookTok).
What Tropesmith is not. It is not a keyword tool: it will not give you Amazon search volumes or seven backend keyword strings. It does not estimate anyone's sales or revenue. It does not build or bid your ads. If those are the jobs in front of you, the tool on this page does them and Tropesmith does not replace it. Plenty of authors run both, and that is the honest recommendation.
| The question you are asking | Publisher Rocket / BookBeam | Tropesmith |
|---|---|---|
| Keyword and category research | Rocket: deep · BookBeam: yes | No |
| Tracking over time | Rocket: no · BookBeam: yes | No |
| Review monitoring | Rocket: no · BookBeam: yes | Reads reviews, but to extract reader requests |
| Cost model | Rocket: one-time · BookBeam: subscription | See pricing |
| Which story should I write next? | No | Yes — ranked by counted reader requests per lane |
| What are readers asking for and not getting? | No | Yes — 721,971 classified requests, with an underserved share per trope |
| How does my trope stack score against the shelf? | No | Yes — that is what a Map is |
| Is BookTok demand in the data? | No | Yes — 554 hashtags scanned hourly, 72,641 videos logged |
Tropesmith figures counted 2026-08-21. Rival capabilities are described from their published feature sets; we do not track anyone's pricing and deliberately quote none — check the vendor, and see our pricing page for ours.
The corpus behind every Tropesmith number on this page, counted on 21 August 2026.
Counted 2026-08-21 18:49 UTC by direct query against the Tropesmith corpus. Method: how we read reader demand · how a Map is built.
A Tropesmith Map scores your exact trope stack on live demand versus supply — and names the gap you can own.
Build my Map → See a real sample Map first → See pricing →Rocket if your research is a one-off per book and you want depth on keywords and categories without an ongoing bill. BookBeam if you are running launches or ads and need to see rank and reviews move over time, which a snapshot tool cannot show you at all.
Not better, different. BookBeam's tracking is something Rocket does not do; Rocket's keyword competition depth and one-time cost are things BookBeam's subscription does not match. Pick on whether your question is 'what should this listing say' or 'what is happening over time'.
Most authors do not. The overlap on keyword and category research is substantial; the non-overlap is tracking, which you either need or do not.
The book that is not there. Both are anchored to published titles - keywords they rank for, charts they sit on, curves they trace. Tropesmith counts what readers asked for and did not get: 721,971 classified reader requests across 138 demand lanes, each trope carrying the share our engine flags as unmet.
Yes, and that is the sensible setup. Tropesmith decides what to write and which trope stack to build on; Rocket or BookBeam handle the listing and the tracking once it exists.
Every Tropesmith figure on this page is counted, dated 2026-08-21, and sourced from the reader-demand engine and book registry. Part of the market intelligence hub.