Most book launch email sequences do two things: announce the release and remind subscribers to buy. That is a content calendar, not a launch sequence, and the difference shows up in your review count on release day.
An announcement can sell. If your list is warm, an email saying the book is out will move copies. What it does not do is tell readers what to do after they buy, when, or where. That gap is where most review counts stall. Not because readers won’t leave reviews, but because the ask arrived at the wrong time, in the wrong form, or buried under three other requests in one email.
What should a book launch email sequence actually do?
A book launch email sequence should warm the list before release, sell the book on launch day, and then guide readers toward reviews on a timeline that matches how people actually read. It runs longer than launch week, and it treats subscribers as readers to serve rather than leads to convert.
Broken into parts, a working sequence covers four jobs: a pre-launch warm-up, a launch announcement, a delayed and separate review request, and a low-pressure check-in weeks later.
When should you send the review request email?
Send the main review request ten to fourteen days after launch, timed for readers who bought immediately, then add a follow-up at three to four weeks for slower readers. Sending it on release day asks for a review before anyone has finished the book.
A reader who buys on release day and reads at an average pace finishes in seven to fourteen days. A reader who adds the book to a long TBR may not open it for weeks. A review request that lands before the read is done gets ignored, or it pushes readers to think about a review they have nothing to base yet.
That timing means the review request is its own send, not a line inside the launch-day announcement, and your sequence extends further past launch than most authors plan for.
Should ARC readers get the same launch emails?
No. ARC readers need their own sequence. They already have a copy, they may have agreed to post on release day, and a “the book is out!” email reads as redundant or as a nag about a commitment they already made.
Give ARC readers:
- Before launch: a reminder of their commitment and a note on where to post.
- On release day: a short “we’re live” email with direct links to the review pages, copy they can use, and the specific platforms you want.
- After launch: a thank-you that does not ask for anything more.
Your general list gets the announcement and the delayed review request. Send both groups the same email and neither message is right for either audience.
What is the pre-launch warm-up email for?
Four to six weeks before launch, send your general list an email that has nothing to do with selling the book and everything to do with building context for it: the world of the book, who the protagonist is and why this character matters, what the reading experience feels like.
It does two jobs. Readers who are already excited get something to engage with before release, and readers who have gone quiet get a reason to re-engage before you need them to act. Warm subscribers convert better on launch week and leave more reviews. A list that has been silent for six months and suddenly gets “my book is out, here’s the link” is a cold list in launch-week clothing.
How many asks should the review email have?
One. The review request email does one thing: please leave a review if you enjoyed the book. Not one thing plus a reminder about the sequel. Not one thing plus a request to share with a friend.
A few rules that lift responses:
- Name the platforms you want. “Amazon and Goodreads” beats “wherever you like to post.” Readers who want to help often don’t know which platform matters for discoverability.
- Link straight to the review page, not the book’s landing page where they have to hunt for the review section.
- Keep it short. A two-paragraph email that says “finished the book? Here’s where a review would mean the most to me” outperforms four paragraphs on why reviews matter to indie authors.
What happens after the sequence ends?
The sequence ends, but the book doesn’t. Schedule a post-launch check-in at six to eight weeks that thanks readers who reviewed, says where the book is available, and quietly invites people who haven’t read it yet. It is not a second launch, just a reminder that the book exists without the urgency of launch week.
Skip the “last chance” email unless something is genuinely changing. A book does not expire. Unless the price is actually going up, that framing reads as a pressure tactic, and it costs you unsubscribes from readers who were still deciding.
Frequently asked questions
How many emails should a book launch sequence have?
Most fiction launches run well on four to six emails: a pre-launch warm-up, a launch-day announcement, a review request around ten to fourteen days out, an optional second review nudge at three to four weeks, and a check-in at six to eight weeks. ARC readers get their own shorter track.
When is the best time to ask readers for a review?
Ten to fourteen days after release for readers who bought early, with a follow-up at three to four weeks for slower readers. Asking on release day almost always lands before anyone has finished the book.
Should I send ARC readers and newsletter subscribers the same launch emails?
No. ARC readers already have the book and often a posting commitment, so they need a separate, shorter sequence focused on where and when to post. Your general list gets the announcement and the delayed review request.
Do "last chance" launch emails work?
Rarely, and they can backfire. A book does not expire, so manufactured urgency reads as pressure and drives unsubscribes. Only use that framing when something real is changing, like a price increase or a closing pre-order bonus.