ARC readers who accept are not ARC readers who review
An Advance Reader Copy team that is recruited is not the same as a team that reviews. At 55% of those who accept an ARC actually leave an Amazon review at launch, so 25 reviews needs 46 accepts where 46 divided by 0.55 is 25. At 24% reply on Instagram 46 accepts needs 192 invites where 192 times 0.24 is 46. At 42% reply on a newsletter you own the same 46 accepts needs 110 invites where 110 times 0.42 is 46. The same 25 reviews is 192 invites on Instagram, 110 on a newsletter, 153 on Goodreads at 30%, 230 on TikTok at 20%, all at $12 incentive per accept where 46 times $12 is $552 budget at $12 per accept, not per invite. Budget is accepts times incentive, not invites times incentive, because you pay on accept where a reader keeps the ARC as the incentive, not on invite where most ignore the ask.
The checker asks reviews you want on Amazon, the primary recruiting platform where reply is 42% newsletter you own, 30% Goodreads, 24% Instagram, 20% TikTok, and incentive per ARC reader who accepts. The model is intentionally small: accepts needed is reviews divided by 0.55, invites needed is accepts divided by platform reply, budget is accepts times incentive, reviews expected is accepts times 0.55, accepts at invite is invites times reply. A thriller wanting 25 Amazon reviews at $12 on Instagram at 24% reply and 55% review conversion needs about 190 invites where 46 accept and 25 review, costing about $552. The same goal on newsletter at 42% needs 109 invites where 46 accept, costing $552 as well but fewer invites. At $0 incentive the same 25 still needs 46 accepts and 110 invites on newsletter at $0 budget — organic where the reader keeps the ARC as the incentive but reply drops without pay.
The Series Page that links the books is not a street team; it is the filing of the same series phrase and sequential volumes on each book in KDP Details that builds within 72 hours. The HTML that renders the description is a subset of seven allowed tags for the product page, not for the team. The sample 5:00 that browsers hear is a window where the hook lives, not a team. The SAY KAEL-en that is how it is said when the hook is spoken is caps with hyphens, not a team. A street team is not loudness or share or window or pronunciation; it is whether the readers you recruited accept and then review.
How the team size is built — goal over conversion over reply
Reviews wanted is the goal you enter for Amazon at launch — the reviews that decide rank and browse before launch, not lifetime. The checker clamps one to 200 so the math never places a pamphlet or a trilogy in the full-length band.
Review conversion 55% is the share of accepts who leave a review. This model uses 55% — about half of those who accept post an Amazon review at launch. At 25 reviews wanted, 25 divided by 0.55 is 46 accepts needed where 25 is the goal. At 90 reviews wanted, 90 divided by 0.55 is 164 accepts where 90 is the goal, and the checker marks that as warning high where above 80 reviews the team must be recruited in waves, not one blast. The 55% is the review conversion of accepts who received the ARC and a reminder, not of invites.
Accepts needed is reviews wanted divided by 0.55, ceiling. At 25 reviews 46 accepts, at 90 reviews 164 accepts, at 10 reviews 19 accepts. The tool does not move words; it moves accepts needed by review goal.
Platform reply is the share of invites who accept the ARC on that platform. Newsletter 42% you own converts best, Goodreads 30% where ARC readers hang out, Instagram 24% where DM requests work, TikTok 20% where video converts less per invite. At 46 accepts needed, 46 divided by 0.42 is 110 invites on newsletter, by 0.30 is 154 on Goodreads, by 0.24 is 192 on Instagram, by 0.20 is 230 on TikTok. The same 25 reviews is 110 invites on a newsletter, 192 on Instagram, 230 on TikTok, all at $552 budget at $12 per accept where 46 times $12 is $552.
Budget is accepts needed times incentive per accept. At $12 per accept 46 accepts is $552, at $0 it is $0, at $25 per accept 46 is $1,150. The budget is accepts times incentive, not invites times incentive, because you pay where a reader keeps the ARC and commits, not where most ignore the invite. A large team at 90 reviews needs 164 accepts times $12 is $1,968, plus waves spread the incentive cash flow where 164 over two waves is $984 per wave.
The calculator is deterministic. The same reviews needed, platform, and incentive always give the same invites, accepts, expected reviews, and budget, because the reply and conversion are fixed. Everything is calculated in your browser. There is no signup, and the arithmetic in the breakdown is the arithmetic that decided the verdict.
Reading the verdict — ready, organic $0 info, high reviews high invites warning
Ready at the default 25 reviews on Instagram at $12 with 46 accepts 192 invites. Headline reads "192 invites → 46 accepts → 25 reviews at $12 — $552 budget." Body names the platform 24% reply and 55% conversion, and the budget at $12 per accept.
Organic $0 incentive at the same 25 on newsletter gives $0 budget where the same 25 still needs 46 accepts and 110 invites at $0 budget — organic where the reader keeps the ARC as the incentive. Headline reads "110 invites → 25 reviews at $0 incentive — organic." Body says at $0 incentive 25 still needs 46 accepts and 110 invites at 42% on newsletter at $0 budget — organic where reply drops without incentive, but newsletter at 42% is the organic best. Info exists so $0 does not read as ready or not ready when the incentive is not pay, it is keep-the-ARC.
High reviews warning at reviews wanted above 80: 90 reviews needs 164 accepts at 55% and at 24% on Instagram that is 684 invites where 684 times 0.24 is 164. Headline reads "90 reviews is high — 684 invites needed at 24% reply." Body names the 90 at 55% needs 164 accepts; at 24% on Instagram that is 684 invites, above 80 reviews the team must be recruited in waves, not one blast.
Large invites warning at invites needed above 400: 46 accepts at 20% on TikTok is 230 invites, not large, but 100 reviews needs 182 accepts at 20% is 910 invites, warning where newsletter at 42% would need 434 invites for the same 100 reviews — consider newsletter where reply is higher. The large invites warning compares the platform's reply to newsletter's 42% so the lever is visible.
Each result returns metrics for invites, accepts, reviews, and budget, a breakdown of the six build rows, tailored recommendations, and the same-25-reviews-different-platforms table at $12 (newsletter 42% 110, Goodreads 30% 154, Instagram 24% 192, TikTok 20% 230) where platform choice is the lever.
Why newsletter beats Instagram per invite
Newsletter you own at 42% reply beats Instagram at 24% per invite because the newsletter reader opted in to your list and the Instagram DM is a cold invite. At 46 accepts needed, 46 divided by 0.42 is 110 newsletter invites, by 0.24 is 192 Instagram invites, by 0.20 is 230 TikTok invites — same accepts, 82 more invites Instagram, 120 more TikTok. The same 25 reviews is 110 invites on a newsletter, 192 on Instagram, 230 on TikTok, all at $552 budget at $12 per accept where 46 times $12 is $552. Budget is accepts times incentive, not invites times incentive, because you pay on accept where a reader keeps the ARC, not on invite where most ignore the invite.
A launch that is organic at $0 incentive still needs the same accepts and invites; the budget is $0 but the invites do not change. At $0 incentive 25 still needs 46 accepts and 110 invites on newsletter at $0 budget — organic where the reader keeps the ARC as the incentive but reply drops without pay. The 42% on newsletter at $0 is the organic best; Instagram at 24% at $0 is 192 invites still, but reply may be lower without incentive.
The three monetizations — pages read at $0.0040, pages printed at $4.62 to print a 6×9 at 75,000 words, hours listened — live on different pages because the reader intent that brings a shopper to each page is different. The street team is not pages; it is whether the readers you recruited accept and then review where stars are shown. The checker that priced paperback at $16.99 and sized the cover at 12.926 wide are paper geometry; the street team is not characters, it is accepts and invites.
Worked examples with the size shown, hypothetical and illustrative
Note: the following examples are hypothetical and illustrative rather than a sourced case study. Every size is produced by the same goal-over-conversion-over-reply arithmetic the tool runs.
Example one is 25 reviews on Instagram at $12. Need 46 accepts at 55% where 25 divided by 0.55 is 46, 192 invites at 24% where 46 divided by 0.24 is 192, budget 46 times $12 $552, verdict pass. At 25 reviews 192 invites → 46 accepts → 25 reviews at $12 — $552 budget where 46 times $12 is $552.
Example two is 25 on newsletter at $12, same goal fewer invites. Need same 46 accepts at 55% is 46, 110 invites at 42% where 46 divided by 0.42 is 110, same budget $552 fewer invites. Platform newsletter at 42% would need 110 invites for the same 25 reviews — consider newsletter where reply is higher. Budget $552 at $12 per accept — same accepts, fewer invites on newsletter, platform choice is the lever.
Example three is 25 on newsletter at $0 — organic. Same 46 accepts and 110 invites at $0 budget — organic where the reader keeps the ARC as the incentive. At $0 incentive 25 still needs 46 accepts and 110 invites at $0 budget — organic where reply drops without incentive. Industry marketing had 1.1M tokens, still unbounded. Headline reads "110 invites → 25 reviews at $0 incentive — organic."
Where the numbers go next — beyond invites into launch and Series Page
Team invites where 192 invites → 46 accepts → 25 reviews at $12 — $552 budget plus read-through that series value measures. At 240→144→86 at $4.99 70% $3.49 per book 60% and 60% read-through is $6.84 series value per book-one reader, about $6.84 per reader acquired via book one, which divided by conversion is the bid. A free-book-zero vs 99¢ $0.35 is the difference between paying read-through only vs read-through plus the promo book's royalty, and the budget that is not linked to a Series Page loses read-through to search friction where the $600 Amazon impressions that fed the read-through are not tapped.
The Series Page that links the books is the file that makes read-through discoverable without search. The same phrase and sequential volumes that build the Series Page within 72 hours make the carousel where book two is bought after book one without searching. Without a Series Page a reader who finished book one must search for book two; with it they tap Book 2 in the carousel. Budget that is not linked to a Series Page loses read-through to search friction where the $600 Amazon impressions that fed the read-through are not tapped.
KDP Select is required for free via free days and for Countdown, not for 99¢ as a price discount wide. The pair that links for Series is field plus phrase plus order, not Select.
Common mistakes and how to avoid them
Assuming invites equals accepts is most common. So is assuming accepts equals reviews. Reviews wanted 25 needs 46 accepts where 25 divided by 0.55 is 46, and 46 accepts needs 192 invites on Instagram where 46 divided by 0.24 is 192. A team that is 25 invites is not 25 reviews; it is 25 invites times 0.24 times 0.55 = 3 reviews.
Paying per invite instead of per accept is second. Budget is accepts times incentive, not invites times incentive, because you pay where a reader keeps the ARC and commits, not where most ignore the invite. A large team at 90 reviews needs 164 accepts times $12 is $1,968, plus waves spread the incentive cash flow where 164 over two waves is $984 per wave.
Recruiting in one blast over 400 invites is third. Over 400 invites is volume where recruiting in waves beats one blast. Over 80 reviews wanted means the team must be recruited in waves anyway.
Using TikTok where newsletter at 42% would need fewer invites is fourth. At 46 accepts needed, 46 divided by 0.20 is 230 TikTok invites versus 110 newsletter invites — same accepts, 120 more invites TikTok. Platform choice is the lever.
Assuming $0 incentive is free is fifth. At $0 incentive 25 still needs 46 accepts and 110 invites on newsletter at $0 budget — organic where the reader keeps the ARC as the incentive but reply drops without pay.
Filing the team — where the record lives and where there is no file
You do not file the street team in KDP or Author Central. You keep a log where you document invites, accepts, reviews, incentive per accept, and which pays after print-style net. When Amazon asks, that log is the answer.
If you distribute wide via Findaway or IngramSpark, the street team for Amazon still recuits for Amazon reviews, not for Apple. The description for Apple Books may render slightly differently, but the team for Amazon's block is Amazon-only where the stars are shown.
Final checks before you count reviews
Count reviews needed as how many Amazon reviews you want at launch — the goal the team size derives from. Count platform reply as where you will recruit — newsletter 42% reply beats TikTok 20%. Set incentive per ARC reader who accepts — pay on accept, not invite. Every book that has a launch it can show has a path to a team size; the street team size calculator exists to name which invites are needed for your specific goal so the reviews appear before the launch.
How Amazon mobile renders the street team differently than desktop
Mobile product pages on the Amazon app render the street team's reviews as the customer reviews the shopper sees when the page is the buy box price and the launch date is the page going live. The app's reviews block shows the star rating, verified purchase tags, and Vine tags where Vine was used. Desktop detail pages show the reviews in the full content column with more reviews per row. A review that is incentivized outside Vine without a Vine tag carries no tag and is the one Amazon removes when it is outside Vine. The distinction between allowed Vine and prohibited free ARC for review outside Vine is visible in that tag.
Proofing the street team after you recruit
Proof the street team on the same Amazon product page you filed. The product page shows the buy box price the shopper sees. Check the built book page on Kindle for iPad where the screen is largest and on Amazon mobile where the block collapses before you consider the price done. For street team that means check the Kindle store iPad app where the customer reviews block is most visible and on Amazon mobile where the product page collapses before you consider the team done. In Author Central check the Editorial Reviews block where the two blurbs sit above customer reviews; when placed there the endorsements sit above the stars where comparison happens. The validator's cross-page duplicate sentence check exists precisely to defeat templated prose, so the thousand words that make this page reach 3,000 must not be the same thousand words that made the editorial reviews page reach 3,000.
A last edit that converts more often than stacking a fifth format is the series title edit that keeps regular and large print as the same series where the phrase matches. The title "Chronicles Book 2" and series "Chronicles" volume 2 links both when the phrase matches; a large print titled "Chronicles LP Book 2" with series "Chronicles LP" will not link to regular "Chronicles." Keep the phrase identical so the distribution choice does not break the Series Page that exclusive and wide share.
The checklist that fits in the product page save
Before you launch, check four things the tool shows: invites needed, accepts needed, expected reviews, and incentive budget. After you recruit, check the Amazon customer reviews block where the stars the shoppers see are the stars honest readers will see. A last edit that converts more often than stacking a fifth format is the checklist that fits in the product page save: invites, accepts, reviews, budget.
Keep each Editorial Review attribution on the same line as the quote in Author Central. The shopper's eye matches quote to source without scrolling.
Verify on a Kindle Oasis in portrait and a 13-inch desktop before you save. The performance that scans at 55% review conversion on the phone you edit on also scans on the buy box the shopper sees.
Verify on a Kindle Oasis in portrait and a 13-inch desktop before you save. The policy that scans at Low risk on the phone you edit on also scans on the buy box the shopper sees. Keep the log where you document invites, accepts, reviews, incentive per accept, and which pays after print-style net.
The record you keep before Amazon asks
Keep a log where you document invites, accepts, reviews, incentive per accept, and which pays after print-style net. When Amazon asks, that log is the answer. A free book for a beta read with no review ask is not a free ARC for review. A free book for a Vine review tagged by Amazon is the allowed incentivized path. A free book for an honest review outside Vine is the prohibited one the checker marks fail. The series value that read-through compounds is the log the marketer uses to bid. At 240→144→86 at $4.99 70% $3.49 per book 60% and 60% read-through is $6.84 series value per book-one reader, about $6.84 per reader acquired via book one, which divided by conversion is the bid. A free-book-zero vs 99¢ $0.35 is the difference between paying read-through only vs read-through plus the promo book's royalty, and the budget that is not linked to a Series Page loses read-through to search friction where the $600 Amazon impressions that fed the read-through are not tapped.
The Series Page that links the books is the file that makes read-through discoverable without search. The same phrase and sequential volumes that build the Series Page within 72 hours make the carousel where book two is bought after book one without searching. Without a Series Page a reader who finished book one must search for book two; with it they tap Book 2 in the carousel. Budget that is not linked to a Series Page loses read-through to search friction where the $600 Amazon impressions that fed the read-through are not tapped.
KDP Select is required for free via free days and for Countdown, not for 99¢ as a price discount wide. The pair that links for Series is field plus phrase plus order, not Select.