Tropesmith
Playbook · Methodology

How to Read Trope Demand Data Before You Write

Updated 9 September 2026 · Source: Tropesmith reader-demand engine

Every trope hub page on this site shows the same four numbers: reader requests, underserved %, market state, and 14-day momentum. Here's what each one actually means, and — more importantly — what it doesn't.

Reader requests: volume, not validation

This is a raw count of individual reader asks pulled from BookTok, Reddit, Goodreads, StoryGraph and AO3 and classified against a trope. Found Family leads Tropesmith's whole corpus at 267,433 requests. That tells you the trope is wanted at scale — it says nothing about whether the specific angle you'd write is one of the ones being asked for. Read the underlying reader-ask summaries on a trope hub page, not just the headline count, before committing to a stack.

Underserved %: a gap, not a guarantee

Underserved is the share of tracked demand with no matching tagged supply in Tropesmith's registry. Historical Fiction in the romance corpus sits at 100% underserved with essentially zero tagged supply — Tropesmith calls this a "novel-gap" rather than merely "underserved," and the distinction matters: a novel-gap can mean nobody has shown up yet, or it can mean the demand is real but too diffuse for any single book to satisfy. Treat a novel-gap as a research lead, not a green light.

Market state: balanced, developing, underserved, novel-gap

This is Tropesmith's coverage-maturity label for a trope, built from the ratio of tagged supply to demand. "Balanced" doesn't mean stop looking — it means the opportunity is in a specific angle or pairing, not in the trope's bare existence. "Developing" and "underserved" mean thinner competition. "Novel-gap" means almost no tagged competition at all, which is the highest-variance signal of the four.

14-day momentum: direction, at small scale

The demand radar shows what share of a trope's all-time volume landed in just the last two weeks. It's the closest thing to a velocity read this dataset supports on a single trope, but it's still a short window — treat one strong 14-day reading as a thing to watch, not a trend to bet a book on. Watch it move over a few refresh cycles before treating it as a real signal, and prefer it on high-volume tropes, where a 14-day share is built on hundreds or thousands of requests rather than a handful.

The one-line version

Use request count to find scale, underserved % and market state to find the gap, and 14-day momentum to time it — then read the actual reader-ask summaries and rejection data on the trope hub page before you commit, because none of these four numbers tells you whether you can execute the specific angle readers are asking for.

Frequently asked questions

Does a high request count mean I should write that trope?

Not by itself. Found Family has 267,433 requests logged and is classified "balanced" — real demand, but real competing supply too. The number tells you the trope is wanted; it doesn't tell you the lane is open.

What does "underserved" actually measure?

The share of tracked demand for a trope that Tropesmith's registry has no matching tagged supply for. It's a gap measure, not a quality measure — a high underserved % says the shelf hasn't caught up to requests, not that any specific unmet request is easy or profitable to satisfy.

See where your book sits on this map

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 it applied: Found Family, Cozy Mystery, the romance roundup.

© 2026 Tropesmith · Romance tropes · Live market snapshots · Market intelligence