Sales charts tell you what readers bought last month. Demand signals tell you what they're reaching for next — the requests, obsessions, and complaints readers broadcast in public, every day, before the books they're describing exist. Learning to read those signals is the closest thing publishing has to seeing around a corner, and it's the layer of market research most authors never touch.
This guide covers what the signals are, where each one lives, how to weigh them against each other, and how to do the reading yourself — plus how Tropesmith automates it at scale.
When a trope, aesthetic, or title catches on BookTok, the play counts are enormous and the effect on sales is real — entire subgenres have been lifted by it. The signal to read isn't just which books are going viral but which promises: the tropes and feelings named in captions and comments. BookTok is the loudest and fastest-moving of the demand signals, which is why Tropesmith's engine weights it highest.
Reddit's romance communities are full of request threads: “I want a book where…”, “looking for something like X but with Y…”. This is demand in its purest form — a reader explicitly describing a book they cannot find. When the same ask recurs across threads, you're looking at a gap on the shelf, described by the people who'd buy the book that fills it.
The shelves readers create are a folksonomy of how readers actually categorise books — the exact vocabulary they use, which is worth more to your blurb and keywords than any thesaurus. Reviews add the verdict layer: what readers of a book loved, and what they wished it had done. A recurring “I wish…” in a subgenre's reviews is a quieter, more considered cousin of the Reddit ask.
Strictly, Amazon shows supply and its performance — but it's the indispensable cross-check. Demand without a supply check can send you chasing something the market already delivered; a signal is only an opportunity when the shelf hasn't caught up. This demand-vs-supply cross-referencing is the mechanism behind every Tropesmith verdict.
The sources disagree constantly, so you need a hierarchy. Tropesmith's engine uses this one: BookTok signals weigh most — a viral video carrying millions of plays is the strongest social proof in the corpus — then direct Reddit asks (explicit, unambiguous requests), then Goodreads reviews (single-reader praise or complaint). Whatever survives that weighing gets cross-referenced against Amazon supply to see whether the market has already answered it. You can apply the same hierarchy by hand: a trope that's viral on BookTok, requested on Reddit, and thin on the bestseller shelf is the strongest signal an author can find.
Weigh repetition over volume. One viral video is an event; the same craving surfacing across BookTok comments, Reddit asks, and Goodreads reviews is a market.
Pick the BookTok hashtags for your subgenre and skim weekly. Read comments, not just videos — comments are where readers say what they want next.
Search romance book-recommendation communities for your lane's keywords, sorted by new. Save every ask that matches your territory; recurring phrasings are the finds.
Newest reviews of comparable titles (see finding comps) tell you where current readers are delighted and where they're still hungry.
Half an hour a week keeps you conversant; genuinely mapping demand for a lane — reading it across all sources, weighing it, checking supply — is a job measured in days. That's the layer Tropesmith industrialises: the engine reads BookTok virality, Goodreads shelves and reviews, and Reddit asks continuously, weighs them, and cross-references Amazon supply. You can see the live output free on Trending and Reader Demand, and in every lane snapshot's fastest-rising trope. A Map turns that corpus into a verdict for your exact book — and the gaps it names come backed with the reader quotes that revealed them. Demand data is one input to the larger question of what to write; for the full decision, start at what romance subgenres sell.
Public evidence of what readers want before sales data can show it: BookTok virality around tropes and aesthetics, direct requests in Reddit romance communities, and the shelves and reviews readers create on Goodreads. Read together and checked against Amazon supply, they reveal gaps between what readers are asking for and what the shelf delivers.
Tropesmith's engine weights BookTok highest — a viral video carrying millions of plays is the strongest social-proof signal in the corpus — followed by explicit Reddit asks, then Goodreads reviews, always cross-referenced against what's over-supplied on Amazon. Repetition across sources beats volume in any single one.
Yes: follow your lane's BookTok hashtags, search romance recommendation threads weekly, and read fresh reviews of your comp titles. Tropesmith's free Trending, Reader Demand, and lane snapshot pages surface the engine's live readings at no cost; the paid Map applies the full corpus to your specific book.
A Tropesmith Map weighs BookTok, Reddit and Goodreads demand against Amazon supply for your exact lane — with the gap named.
Build my Map — $15 → See a real sample Map first →Live data referenced on this page: Tropesmith market snapshots — refreshed as the market moves. Guides are part of the romance market intelligence hub.