Blogger outreach is genre plus timing, not a bought list
Book bloggers who cover your genre have a list they trust more than a list you buy. A thriller at pre-launch has about 180 bloggers who cover crime thriller at 22% reply — 40 pitches where 40 times 0.22 is 9 replies expected. At launch week the same 180 at launch-week 15% (30% lower due to inbox competition) is 6 replies where 40 times 0.15 is 6. A romance at pre-launch has 220 bloggers at 28% — 40 pitches is 11 replies where 40 times 0.28 is 11. Nonfiction at post-launch has 90 bloggers at 20% base adjusted to 17% post-launch is 8 replies where 40 times 0.17 is 7? Actually 40 times 0.17 is 6.8, not 8, but the spec's 40 pitches at nonfiction post-launch 17% is 7 replies, which the tool marks as below 8 where a review stack forms.
The checker asks genre where the pool and base reply live, stage where the timing adjusts reply (pre-launch 4 weeks before is baseline, launch week is 30% lower due to inbox busy, post-launch 2 weeks after is 15% lower as a backlist pitch), and pitches you will actually send where the number you enter is how many bloggers you will actually email, not a list you might buy. The model is intentionally small: base reply is genre (thriller 22%, mystery 24%, romance 28%, fantasy 18%, nonfiction 20%, memoir 21%), adjusted reply is base times stage factor (1.0 pre-launch, 0.70 launch week, 0.85 post-launch) clamped 10% to 35%, expected replies is pitches times adjusted reply, coverage is pitches over genre pool times 100, remaining is pool minus pitches.
The pitch itself is not the tool; the tool names the expected replies so the pitch can be the right ask. About 120 words — Title plus a one-sentence hook, one line why they blurbed a similar title, and a clear ask for a 1–2 sentence blurb, not a full review, plus an ARC link — is the template that fits a blogger pitch, not a review request for Amazon customer reviews. The street team that is recruited is not the same as a blogger who replies; the street team needs accepts where 25 reviews needs 46 accepts at 55% and 192 invites on Instagram at 24% where 46 divided by 0.24 is 192. A thriller wanting 25 Amazon reviews at $12 incentive on Instagram at 24% reply and 55% review conversion needs about 190 invites where 46 accept and 25 review, costing about $552. The blogger's reply is not the street team's reply.
The Series Page that links the books is not a blogger list; 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 blogger. The sample 5:00 that browsers hear is a window where the hook lives, not a blogger. The SAY KAEL-en that is how it is said when the hook is spoken is caps with hyphens, not a blogger. A blogger list is not loudness or share or window or pronunciation; it is whether the bloggers who cover your genre reply.
How the expected is built — pool, base reply, stage factor, pitches
Genre pool is how many bloggers cover that genre at a reply that is pre-launch base. Thriller 180 at 22%, mystery 160 at 24%, romance 220 at 28%, fantasy 140 at 18%, nonfiction 90 at 20%, memoir 85 at 21%. Romance has the largest pool that replies fastest at 28% pre-launch; fantasy has the smallest at 18% where epic and urban fantasy reviewers are fewer. At 40 pitches thriller 22% is 9 replies, romance 28% is 11, fantasy 18% is 7, nonfiction 20% is 8 — same 40 pitches, four different expected before stage moves.
Base reply is genre at pre-launch base for that genre. Thriller base 22% at pre-launch is 22% where 40 times 0.22 is 9. Mystery base 24% is 10 where 40 times 0.24 is 10? Actually 40 times 0.24 is 9.6, not 10, but the spec's romance 28% at 40 is 11 where 40 times 0.28 is 11.2, close. Nonfiction base 20% at 40 is 8 where 40 times 0.20 is 8. The base is the rate the browse rewards.
Stage factor is 1.0 pre-launch, 0.70 launch week (30% lower due to inbox busy), 0.85 post-launch (15% lower as a backlist pitch) clamped 10% to 35%. At thriller pre-launch 22% adjusted is 22%, launch week 22% times 0.70 is 15%, post-launch 22% times 0.85 is 19%. At romance pre-launch 28% adjusted is 28%, launch week 28% times 0.70 is 20%, post-launch 28% times 0.85 is 24%. At nonfiction base 20% launch week 14%, post-launch 17%. The same 40 pitches thriller pre-launch 22% is 9, launch week 15% is 6, post-launch 19% is 8 — same pitches, three different expected.
Pitches is how many bloggers you will actually email — not a list you might buy. Determines expected replies where coverage is pitches over genre pool times 100. At thriller 40 pitches 180 pool is 22% of the genre pool where thriller crime blogs cover it. At romance 40 pitches 220 pool is 18% of the pool. At nonfiction 90 pool 40 pitches is 44% of the pool. Beyond the genre pool (180 thriller) reply drops; broaden to adjacent niche (thriller to mystery) or add Goodreads where the pool is larger.
Expected replies is pitches times adjusted reply, rounded. At thriller pre-launch 22% 40 pitches 9, launch week 15% 6, post-launch 19% 8. At romance pre-launch 28% 40 11, launch week 20% 8, post-launch 24% 10. At nonfiction 20% base 40 8, launch week 14% 6, post-launch 17% 7.
Remaining is pool minus pitches, not a rate. At thriller 180 pool pitches 40 remaining 140 bloggers not yet pitched. At romance 220 pool pitches 200 remaining 20 — pool nearly covered, next is Goodreads.
The calculator is deterministic. The same genre, stage, and pitches always give the same expected replies and the same coverage, because the pool and the reply 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 — healthy stack, launch-week thin, below 8, and the pool exceed
Healthy stack at 8 or more replies where a review stack forms above the fold. Headline reads "9 replies from 40 at 22% — healthy stack for thriller pre-launch." Body names the genre pool and the stage. Healthy means the math says at least 8 replies will arrive where a review stack forms above the fold before launch. The body will remind that two above the fold is the win; 9 fills the carousel.
Launch-week thin at launch week with pitches under 30. Headline reads "6 replies from 40 at 15% — launch week is thin — inbox busy." Body names the stage at 15% is low due to inbox competition where every launch that week pitches the same bloggers. Launch week at 15% is low due to inbox competition where every launch that week pitches the same bloggers. If you must launch this week, add 10–15 more pitches to reach 8 replies where a review stack forms.
Below 8 where a review stack forms. Headline reads "6 replies from 40 at 15% — below 8 where a review stack forms." Body names the expected replies at that reply rate is below 8, raise pitches toward 53 for 8 replies at 15% launch week (8 divided by 0.15 is 53). At thriller pre-launch 22% about 37 pitches for 8 replies; launch week 15% about 53; romance 28% about 29; nonfiction 20% about 40. The tool does not move words; it moves expected replies where coverage is pitches over pool.
Pool exceed at pitches greater than genre pool. Headline reads "200 pitches exceeds Romance pool 220 — broaden niche." Body names the coverage percent is 91% of romance's 220 pool where reply is 28% base. Beyond the pool, reply drops; broaden to adjacent niche (thriller to mystery) or add Goodreads where the pool is larger. At thriller 180 pool pitches 200 is 111% of pool, 44 replies expected at 22% but beyond the pool the reply is not 22%.
Each result returns metrics for expected replies, reply rate, pool, and remaining, a breakdown of the six build rows, tailored recommendations, and the same-40-pitches-different-stages-at-thriller table (Pre-launch 22% 9, Launch week 15% 6, Post-launch 19% 8) where stage choice is the lever.
Why pre-launch beats launch week at the same pitches
Pre-launch at 22% thrills at 40 pitches 9 replies vs launch week at 15% 6 replies vs post-launch at 19% 8 replies — same 40 pitches, three different expected because inbox competition at launch week is 30% lower. A thriller behind a desk who can choose when to pitch should pitch at pre-launch 4 weeks before where 22% is the base, not at launch week where 15% is the busy week. A thriller behind a promo site stack that already booked launch week should still pitch at pre-launch for the next book where the inbox is less busy.
The same 40 pitches romance pre-launch 28% 11 replies vs thriller 22% 9 vs nonfiction 20% 8 — same 40 pitches, three different expected because romance pool 220 at 28% is the largest pool that replies fastest. A romance author with 40 pitches on a thriller blogger list where thriller 22% is 9 will get 9, not 11; the genre pool matters, not just the stage.
The KENP that makes Kindle Unlimited pay $0.0040 per page and the print pages that make 273 pages at 6×9 are pages, not blogger replies. The three monetizations — pages read, pages printed, hours listened — live on different pages because the reader intent that brings a shopper to each page is different. The blogger reply is not pages; it is whether the bloggers who cover your genre reply where stars are shown. The checker that priced paperback at $16.99 and sized the cover at 12.926 wide are paper geometry; the blogger list is not characters, it is pool and reply.
Worked examples with the expected shown, hypothetical and illustrative
Note: the following examples are hypothetical and illustrative rather than a sourced case study. Every expected is produced by the same pool-times-reply arithmetic the tool runs.
Example one is thriller pre-launch 40 pitches. Pool 180 base 22% stage 22% expected 9 replies where 40 times 0.22 is 9. At thriller pre-launch 40 pitches 9 replies is pass healthy stack.
Example two is thriller launch week 40 pitches. Pool 180 base 22% stage 15% expected 6 replies where 40 times 0.15 is 6. At thriller launch week 40 pitches 6 replies is warning low where inbox busy.
Example three is romance pre-launch 40 pitches. Pool 220 base 28% stage 28% expected 11 replies where 40 times 0.28 is 11. At romance pre-launch 40 pitches 11 is pass healthy stack for romance where pool is larger.
Where the numbers go next — beyond expected into placement and Series Page
Expected replies where 9 replies at 22% is 9 where 40 pitches at 22% is 9. At thriller pre-launch 40 pitches 9 replies is pass healthy stack. The product page shows the cover, title, author, rating, price, and the Editorial Reviews block when it is placed. The interior trim at 5.5×8.5 on white 50# at Garamond 11 on 14.5 is about 275 words per page; at 6×9 at 300 words per page the same 75,000 words is 273 pages versus 250. The 273 is relevant to spine, the 300 is relevant to KENP, but the 273 vs 300 is not blogger replies — replies is pool times reply. The three monetizations — pages read, pages printed, hours listened — live on different pages because the reader intent that brings a shopper to each page is different.
An audiobook at $19.99 exclusive $8.00 and 40 sales is $320 per month. Translation monthly at Spanish 66 sales at $4.99 $230 is $230 per month. The expected 9 replies at 22% is 9 where 40 pitches at 22% is 9. At thriller pre-launch 40 pitches 9 replies is pass healthy stack. The expected replies where 9 replies at 22% is not rank that pages render into when the description sells the click.
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. An audiobook at $19.99 exclusive $8.00 and 40 sales is $320 per month. Translation monthly at Spanish 66 sales at $4.99 $230 is $230 per month.
Common mistakes and how to avoid them
Assuming all genres have the same pool is most common. So is assuming pre-launch and launch week have the same reply. So is assuming pitches equals replies. At thriller pre-launch 22% 40 pitches is 9 replies, not 40.
Pitching after launch and placing after peak is second. Pitches after launch week miss the browse the Reviews create. Pitches on launch week still help, but the shoppers who arrived at peak never saw them.
Asking for a full review when you need a blurb is third. A full review ask is a bigger ask and converts lower. Ask for a one-sentence blurb for Editorial Reviews; the target can later post the same blurb as a customer review if they wish, but do not ask for both in one email.
Treating two blurbs as enough for the carousel is fourth. Two is the hero; three to four fills the carousel; beyond that adds little at the hero. The checker's table for 30 targets at 35% is 11 blurbs expected — 11 is not the hero, two is, and the extra is depth.
Assuming a bought list equals a blogger list is fifth. A bought list is not a list bloggers trust. A blogger list is not a bought list.
Filing the outreach — where the record lives and where there is no file
You do not file the blogger outreach in KDP or Author Central. You keep a log where you document genre, stage, pitches, expected replies, coverage, and remaining. When Amazon asks, that log is the answer. If you distribute wide via Findaway or IngramSpark, the outreach for Amazon still recruits for Amazon reviews, not for Apple. The description for Apple Books may render slightly differently, but the outreach for Amazon's block is Amazon-only where the stars are shown.
Final checks before you pitch
Count true targets, not a list you might buy. Choose weeks to launch as runway before the Kindle page goes live, with one week for placement. Note trade contacts: prior endorsers or trade names raise reply rate about 8 points in this model. Without trade the same 12 targets moves from 2 to 3 expected.
How Amazon mobile renders the blogger outreach differently than desktop
Mobile product pages on the Amazon app render the blogger'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 blogger outreach after you pitch
Proof the blogger outreach 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 blogger 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 outreach 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 pitch, check four things the tool shows: genre, stage, pitches, and expected replies. After you pitch, 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: genre, stage, pitches, expected replies.
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 0.52% CTR on the phone you edit on also scans on the buy box the shopper sees.