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. Tropesmith adds demand signals from reviews and BookTok comments, which have 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 tropes readers name and praise, and how many demand signals each one has. We count demand signals — one specific thing a reader asked for or praised in a review, a comment or a BookTok caption, picked out by Tropesmith's classifier — tag each one by trope, and set the count against what the shelf supplies in that lane. Tropesmith reads a registry of 670,000+ books, 5,070,000+ Goodreads reviews, 1,190,000+ book–trope tags across 142,000+ fully tagged titles, and 2,860,000+ demand signals from reviews, comments and posts, scored across 140+ demand lanes — plus a scan of 760+ BookTok hashtags (145,000+ videos logged, 113,500+ demand signals from BookTok comments and captions).
What Tropesmith is not. It is not a keyword tool: it will not give you Amazon search volumes or seven backend keyword strings. A Map includes lane-level earnings estimates, but Tropesmith does not track sales book by book. 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 demand signals |
| Cost model | Rocket: one-time · BookBeam: subscription | See pricing |
| Which story should I write next? | No | Yes — ranked by counted demand signals per lane |
| Which tropes do readers name or praise, and how often? | No | Yes — 2,860,000+ demand signals from reviews, comments and posts, each trope with the share tagged underserved or novel (this figure was counted 2026-11-05) |
| 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 — 760+ hashtags tracked, 145,000+ videos logged |
The demand signals figure was counted 2026-11-05 10:15 UTC. Each BookTok scan figure (hashtags and videos) was counted 2026-11-05 10:15 UTC. 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; the count dates are below.
Counted by direct query against the Tropesmith corpus. Each of the 2,860,000+ and 113,500+ floors was counted 2026-11-05 10:15 UTC; the 39% share is as of 2026-10-07 17:24 UTC. Each other floor above was counted 2026-11-05 10:15 UTC. A demand signal is one specific thing a reader asked for or praised in a review, comment or post, picked out by Tropesmith's classifier. One review can give several. Each signal gets a rarity tag (common, underserved or novel) from the text of that review or post alone; the classifier is never shown what is on the shelf. A tag points at where to look. It does not prove that no book answers the signal. Shares are the tagged signals divided by all signals in the same scope. Method: How we count · how we count demand signals · how a Map is built.
A Tropesmith Map scores your exact trope stack against demand and supply data — and shows where to look next.
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.
Both are anchored to published titles - keywords they rank for, charts they sit on, curves they trace. Tropesmith adds demand signals from reviews, comments and posts: 2,860,000+ of them across 140+ demand lanes, each trope carrying the share tagged underserved or novel by Tropesmith's classifier.
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, with the count dates shown above, and sourced from the demand-signal engine and book registry. Part of the market intelligence hub.