Publisher research pilots
Reader Lab shows how real genre readers respond now, before your decision is locked. Put concepts, excerpts, covers, titles, and blurbs in front of them, then see what they actually do.
The problem
Sales data tells you what already worked. Reviews arrive after a book is acquired, packaged, and released. The hard questions come earlier.
The Reader Lab difference
Traditional research tells you what readers say they might read. Reader Lab shows what they choose when they are simply deciding what to read next.
Why this signal exists
Readers on StoryForge already discover stories, start them, keep reading or stop, and return to the ones that hold them. Reader Lab measures that behavior against your question.
Live demand
Before you test anything, Reader Lab can show the genres, themes, and tropes drawing real readers inside StoryForge today. A directional read on live demand, ahead of sales data.
What you can test
Each pilot is built around one decision, one primary question, and a clear interpretation framework.
Put a concept or excerpt in front of genre readers before acquisition.
Compare package directions against the same story or sample.
Hold the work constant and test which framing pulls readers in.
See which category a project actually reads as.
Surface titles newly aligned with current genre, trope, or mood.
How a pilot works
Reader Lab answers one publisher-defined question with enough structure to support a real decision.
Acquisition, packaging, positioning, backlist relaunch, or audience fit.
One primary question, clear variants, agreed metrics, and a sample target.
The work is surfaced inside the StoryForge reading experience.
Behavior, segment patterns, caveats, and recommended interpretation.
Acquire, pass, reposition, retest, or find a better audience.
What you receive
Reader Lab does not promise that a book will sell. It reduces the guessing before you make the call, in a form you can take into an editorial, marketing, or acquisitions conversation.
Download the full sample report (PDF) →
Decision, question, variants, and sample target, set before launch.
Click-through, starts, depth, completion, time, and returns.
Which package, framing, or concept performed better, and where.
Genre and trope response, where sample size supports it.
Practical caveats, sample limits, and interpretation boundaries.
A clear read on what the data suggests, and what it does not prove.
Choose your path
Start where the decision in front of you sits, and move up when you are ready.
A live read on the genres, themes, and tropes drawing real readers inside StoryForge. Built for small publishers, agents, and bookstores who want a feel for live demand.
Float a premise, test a cover, validate a title, or resurface a backlist book, and watch what real readers do. A focused behavioral test with a decision-ready answer in days.
Pulse and Pilot together. Watch what is moving across the community, then run your own experiments against that live signal.
Boundaries
The value of the signal depends on being clear about what it can and cannot answer.
It adds reader behavior to the decision. It does not make the decision alone.
The report supports earlier decisions. It cannot promise a market outcome.
Real reader behavior inside the platform, not generated personas or a trained focus group.
Test material is used only within the agreed pilot structure and permissions.
Publisher questions
Concepts, opening chapters, excerpts, titles, blurbs, cover directions, positioning statements, and selected backlist samples. The best test asset depends on the decision you need to make.
One decision, two or three clear variants, a genre where StoryForge can reasonably surface readers, and an agreed interpretation plan before launch.
It supports the decision by showing reader behavior, audience response, and caveats. Use it alongside editorial, commercial, author-platform, comp-title, and list-fit judgment.
Next step
Bring us the decision. We will help design the test.
Already know what you want to test? Request a pilot.