How Many Reviews Do You Actually Need Before Launch?
This is our opinion, based on patterns we've seen across the authors and events we work with. It's not a universal rule, and you're not obliged to agree with it — take what's useful and leave what isn't.
"Get some reviews before launch" is advice almost every indie author has heard. It's also frustratingly vague. Some? How many is some? Does five count? Does fifty? Here's a more useful way to think about it, broken down by what reviews are actually doing for you at each stage.
Reviews aren't one thing — they do three different jobs
Before talking numbers, it helps to separate what a review is actually accomplishing, because the "right" number depends on which job you're trying to get done.
Trust signal for a browsing reader. A stranger landing on your book page needs some indication it's not a scam or a mess. This job kicks in fast — even a handful of honest reviews clears this bar.
Retailer visibility signal. Amazon and other retailers use review count and velocity (how fast reviews come in) as one of many inputs into how much organic exposure your book gets. This job needs more volume and needs it concentrated around launch, not trickled out over months.
Conversion booster once you already have traffic. Once ads or promo are sending people to your page, review count and star rating affect how many of those visitors actually buy. This job scales — more (good) reviews generally keeps helping, though with diminishing returns.
A book can clear job one with almost nothing. Jobs two and three are where "how many" actually starts to matter.
Rough thresholds, and why they're rough
Treat these as directional, not gospel — retailer algorithms change, genres behave differently, and nobody outside the platforms knows the exact mechanics. But as general reference points:
Under 10 reviews: You're still in "prove you're not a scam" territory. Enough to stop a reader from bouncing immediately, not enough to move an algorithm.
10–25 reviews at launch: This is a realistic, achievable target for a debut author running an ARC campaign. It's usually enough to clear the basic trust bar and give a retailer's early-visibility systems something to work with.
25–50 reviews: Meaningfully better. This is where you start seeing the "readers also bought" and recommendation-style visibility kick in more reliably for a lot of authors.
50+ reviews: Now you're competing more seriously in a crowded category. This tends to be where established authors and backlist titles sit, built up over multiple releases, not manufactured before a single launch.
The mistake to avoid is treating any of these as a hard gate — "I only have 8 reviews so I'm not ready to launch" isn't the right takeaway. The mistake to also avoid is treating review count as irrelevant — "reviews don't matter, I'll just launch and see" ignores a lever that's fully within your control before launch day.
Velocity matters as much as total count
A retailer's launch-window signal isn't just "how many reviews does this book have," it's "how fast are reviews coming in relative to when the book went live." Twenty reviews that land in the first week reads very differently to an algorithm than twenty reviews trickling in over four months.
This is the actual reason ARC campaigns are timed the way they are: you want your ARC readers finishing the book and posting reviews in the days immediately around launch, not whenever they happen to get to it. A review that posts three months after launch does far less algorithmic work than the same review posting on day one.
Practical implication: when you're recruiting ARC readers, be explicit about the review-live date you're aiming for, and follow up as that date approaches. A vague "review whenever you can" ask produces a slow trickle. A specific date, communicated clearly, produces a cluster — which is what you actually want.
What this looks like for a genuinely zero-platform debut
If you're starting with nothing, here's a realistic target rather than an aspirational one:
Aim for 15–30 ARC readers — send more than you need, since not everyone finishes or reviews
Expect a 40–60% conversion from ARC reader to actual posted review, if you follow up well
That puts a realistic launch-week review count somewhere in the 10–20 range for a genuine debut with no existing audience
That's not a huge number, and it's not meant to be. It's meant to be achievable without a platform, while still doing real work: clearing the trust bar, giving the algorithm something at launch instead of nothing, and giving future preorder pushes (on this book or the next one) something to point to.
The number matters less than the habit
The specific thresholds above will drift as retailers change how they weight things. What won't change is the underlying logic: reviews concentrated around launch do more than the same reviews spread out, and some reviews at launch beats zero every time. If you take one thing from this — don't let "how many is enough" become a reason to delay building any review base at all. Fifteen honest ARC reviews landing in your launch week will outperform fifty scattered across the following year, almost every time.