The direct answer on welcome sequence length
A book launch welcome sequence usually needs five to seven emails, an evergreen sales sequence needs four to six emails, and a review request sequence needs three to four emails. That range is the whole answer most authors need before they open the calculator above. Six emails is the steady center for a launch, five is the steady center for ongoing sales, and three is the steady center for asking reviews.
Timing matters as much as count. Send one useful email every two days so new subscribers stay warm without feeling crowded. With five emails spaced two days apart, the full run covers nine days from signup to the last call to action. With six emails spaced two days apart, the run covers eleven days. That nine to eleven day window is long enough to introduce yourself, show proof, answer doubts, and make one clear offer.
One email should do one job and ask for one action. When every message has a single purpose, a shorter sequence can outperform a longer one. When messages mix three topics and three links, even a correct length feels confusing.
How the calculator above reaches its recommendation
The tool takes four inputs and returns a recommended range, a day-by-day map, a total span, and a fatigue verdict. The four inputs are the sequence goal, the current list size, the number of emails you planned, and the days between sends. Each input changes a different part of the result.
Goal sets the target range. Book launch maps to five to seven emails with six as the planning center. Evergreen sales maps to four to six emails with five as the planning center. Reviews map to three to four emails with three as the planning center. The calculator compares your planned count against that range and tells you whether you sit inside it, above it, or below it.
List size does not change the recommended count. A list of two hundred and a list of twenty thousand both need the same shape, because the shape follows attention, not volume. List size changes your workload and the number of replies you should prepare for, and it helps you decide how much care to put into each draft before sending.
Days between sends set the total span. The span formula is simple: subtract one from the planned email count, multiply by the days apart, then add one for the starting day. Five emails at two days apart give four gaps of two days, which is eight days of gaps plus the first day, for nine days total. Six emails at two days apart give five gaps of two days, which is ten plus one, for eleven days total. Four emails at three days apart give three gaps of three days, which is nine plus one, for ten days total. Three emails at one day apart give two gaps of one day, which is two plus one, for three days total.
The fatigue verdict reads the combination. Too many means the planned count sits above the top of the goal range. Too few means the planned count sits below the bottom of the range. Gap too wide means more than four days pass between messages. Daily barrage means the gap is zero and several messages land on the same day. A clean pass means the count sits inside the range with one to three days between sends.
The sequence map assigns each email a day number, one job, and one call to action. Email one always lands on day one. Email two lands on day one plus the gap. Email three lands on day one plus twice the gap. The pattern continues until the last email. Each row of the map names what that message must accomplish so you can draft in order instead of staring at a blank list.
Worked numbers you can check by hand
Start with the default case in the tool: goal set to book launch, list of one thousand five hundred subscribers, five emails planned, two days apart. The goal range for launch is five to seven, so five sits inside the range at the low end. The span is five minus one, which is four gaps, times two days, which is eight, plus one, for nine days. The map reads email one on day one, email two on day three, email three on day five, email four on day seven, and email five on day nine. The verdict passes because the count fits and the spacing sits in the one to three day band.
Change only the goal to evergreen sales and keep five planned at two days apart. The evergreen range is four to six with five as the center, so five is an exact hit. The span stays nine days with the same day numbers. The jobs change: the launch version leans toward preorder and bonus language, while the evergreen version leans toward a steady book offer that stays valid after the sequence ends.
Change only the planned count to eight with launch selected. Eight sits above the five to seven range, so the verdict warns about too many. The span becomes eight minus one, which is seven gaps, times two, which is fourteen, plus one, for fifteen days. Fifteen days is not automatically wrong for every purpose, but for a welcome run it stretches past the point where new-subscriber attention stays high, so the fix is to merge the two weakest middle emails into one proof message and return to six or seven.
Change only the gap to seven days with five planned. Five sits inside the launch range, but seven days apart gives four gaps of seven, which is twenty eight, plus one, for twenty nine days. Twenty nine days breaks the welcome effect because subscribers forget the opening promise before the offer arrives. The fix keeps five emails and moves the gap to two, which returns the span to nine days.
Change the list size to zero and keep everything else the same. The recommendation does not move: launch still suggests five to seven. The verdict switches to an informational note because there are no subscribers yet to tire or convert. The shape still matters, since writing the five drafts now means the sequence is ready the week subscribers start arriving.
What each goal range is for
The launch range of five to seven exists because a launch must do four things in order: introduce the author, raise interest in the story, show that other readers trust the book, and ask for the purchase with a reason to act now. Four emails can cover those four moves with no room for doubt handling. Five or six cover them with one spare message for the most common objection. Seven add a last-call reminder. Past seven, the extra messages usually repeat an earlier point instead of adding a new one.
The evergreen range of four to six exists because ongoing sales need a shorter loop that can run all year. New subscribers join in different months, so the sequence cannot depend on a launch date or a limited bonus. Four emails cover welcome with a gift, the problem the book solves, proof, and the offer. Five add a nudge for undecided readers. Six add a final reminder. Past six, evergreen sequences start to feel like a general newsletter wearing a welcome label, and general news belongs outside the welcome run.
The review range of three to four exists because a review ask must stay light. Readers agreed to receive messages, not to complete homework. Three emails cover thanks, a reading nudge, and the ask with a direct link. Four add one polite reminder. Past four, reminders turn into pressure, and pressured readers either ignore the messages or leave the list.
The day-by-day map for a six-email launch
Day one carries email one: welcome and set the promise. Thank the subscriber, name what the next messages will cover, and deliver anything you offered at signup, such as a sample chapter or a bonus scene. The single action is a small reply or a download, not a purchase. A purchase ask on day one skips the trust step and weakens everything after it.
Day three carries email two: story and stakes. Explain in plain terms what the book is about, who it suits, and why you wrote it. Keep the focus on the reader benefit rather than your writing journey. The single action is reading a sample, watching a short reading, or opening a story page.
Day five carries email three: proof. Share short lines from early readers, beta readers, or advance reviewers with their first names and permission. Two or three specific lines beat ten vague ones. The single action is opening a review page or a proof page with more reader words.
Day seven carries email four: the book reveal and the offer. Name the title, the format, the price, and where to buy. State exactly what happens after purchase, such as instant download or shipping time. The single action is the purchase link and nothing else.
Day nine carries email five: the objection answer. Name the most common hesitation for your genre, such as time to read, series order, or content level, and answer it directly with facts. The single action is a frequently asked questions page or a sample that resolves the doubt.
Day eleven carries email six: the launch ask with a bonus and a clear end. Restate the offer, name the bonus and its end date, and ask once. The single action is the same purchase link as email four so readers do not have to search.
If you run five instead of six, merge day nine and day eleven: answer the objection briefly inside the final ask rather than giving it a full message. If you run seven, add a short last-call reminder two days after email six with no new argument, only the deadline and the link.
The day-by-day map for a five-email evergreen run
Day one carries email one: welcome and gift delivery. Deliver the reader magnet or bonus immediately and explain the sending rhythm for the next week. The single action is downloading or opening the gift.
Day three carries email two: problem and change. Describe the situation the reader faces and the change the book offers, using one concrete scene or example. The single action is a story page or a sample chapter.
Day five carries email three: proof. Share reader words and, where honest, your own track record such as number of books or years writing in the genre. The single action is a reviews page.
Day seven carries email four: the core offer. Present the book, the format choices, and the price in one place. The single action is the purchase link.
Day nine carries email five: the nudge. Restate the offer once, remove one doubt, and close. The single action repeats the purchase link.
Evergreen wording must avoid dates, countdowns tied to a launch week, and bonuses that expire unless you can renew them for every new subscriber. A subscriber who joins in March should read the same valid offer as one who joins in October.
The day-by-day map for a three-email review run
Day one carries email one: thanks. Thank the reader for buying or downloading, confirm the title and format, and set a light expectation that a short review request will arrive after reading time. The single action is a reply or a tap to confirm they received the book.
Day three or day four carries email two: reading nudge. Ask where they reached, suggest a natural stopping point such as chapter three, and offer help with any format issue. The single action is continuing the book, not reviewing yet.
Day six or day seven carries email three: the review ask. Explain that honest reviews help other readers decide, give the direct review link, and state that two or three sentences are enough. The single action is the review link alone.
A fourth email, when used, is one reminder about five days later with the same link and no guilt language. No fifth review email belongs in a welcome run; further review mentions belong in the regular newsletter.
Illustrative hypothetical example one: debut novelist with a small launch list
This example is illustrative and hypothetical, built to show the math rather than to report any real list. Imagine a debut novelist with three hundred subscribers, a launch goal, four emails planned, and two days apart. The launch range is five to seven, so four sits one below the bottom. The span is four minus one, which is three gaps, times two, which is six, plus one, for seven days. The map gives day one welcome, day three story, day five proof, and day seven offer with no separate objection answer and no last call.
The gap in this hypothetical plan is the missing doubt handler. First-time buyers hesitate over unknown authors, so the sequence jumps from proof to purchase without answering the main worry. The fix adds one email between proof and offer that answers the top question for the genre, which moves the plan from four to five and the span from seven to nine days. The added message carries one question, one factual answer, and one link to a sample. Nothing else changes: same spacing, same list, same offer. The verdict moves from too few to a pass, and the author drafts one new message instead of rewriting the whole run.
Illustrative hypothetical example two: nonfiction author with a steady evergreen list
This example is also illustrative and hypothetical, with invented numbers for teaching. Picture a nonfiction author with two thousand subscribers, an evergreen sales goal, seven emails planned, and two days apart. The evergreen range is four to six, so seven sits one above the top. The span is seven minus one, which is six gaps, times two, which is twelve, plus one, for thirteen days. The map covers welcome, problem, proof, offer, nudge, reminder, and an extra follow-up that repeats the nudge with different wording.
The weakness here is repetition without new information. By email six the reader has seen the offer twice, and email seven adds a third ask with no new proof. The fix merges emails five and six into one stronger nudge that pairs the offer with the single strongest reader result, then keeps email seven only if it carries genuinely new material such as a fresh case or a new sample. Most authors in this position cut to five emails over nine days and watch replies rise because each remaining message earns its slot. The list size of two thousand does not force a longer run; it only raises the value of cutting weak messages, since each weak send reaches more people.
A third teaching case: weekly spacing that drifts too far
Consider a memoirist with eight hundred subscribers, a review goal, four emails planned, and seven days apart. Four sits inside the three to four review range, so the count looks correct at first glance. The span tells a different story: four minus one is three gaps, times seven is twenty one, plus one is twenty two days. Twenty two days turns a light review request into a month-long thread that readers stop connecting to the book.
The map shows why. Email one thanks the reader on day one. Email two nudges reading on day eight, when many readers have paused or finished and moved on. Email three asks for the review on day fifteen. Email four reminds on day twenty two. The ask arrives after the reading moment has cooled. The fix keeps four emails and moves the gap to two days: day one thanks, day three nudge, day five ask, day seven reminder, for a seven-day run that stays near the reading experience. Same four messages, same link, far better timing.
An illustrative note on open decay across a sequence
Treat this paragraph as an illustrative planning assumption, not measured platform data. Opens often fall as a sequence continues, because the most curious subscribers open everything and the least engaged open only the first message. An illustrative sketch for a one thousand five hundred subscriber list might show roughly one hundred readers opening email one in the sketch, seventy opening email three, and fifty opening email five, with the rest varying by subject line and timing. Those figures are invented to teach shape, and your own counts will differ.
The lesson from the sketch is structural, not numerical. Put the message that must be seen early, because early emails reach more readers than late ones. The welcome promise, the gift link, and the core story belong in the first half. The direct ask belongs after proof but not so late that only the most loyal readers ever see it. If your own past sends show a steep fall between two specific emails, inspect the earlier of the pair: its closing line sets up the next open, and a weak handoff explains many drops better than subject lines alone.
Never present decay sketches as forecasts to yourself or to a collaborator. Use them to order content, then replace them with your own observed counts after two or three real sends. The calculator includes a similar illustrative note in its output for the same reason: to help you plan the order before you have data, without pretending the sketch predicts your readers.
Fatigue signals and what each verdict means
Too many means the count exceeds the range for the goal. Readers feel it as repetition: the same proof reworded, the second nudge after the decision point, the extra story after the offer. The practical signs are falling opens on the last two emails, rising unsubscribes on emails past the range top, and replies that say the reader already decided. The fix removes or merges the weakest middle email rather than trimming the welcome or the final ask, because the ends carry the structure.
Too few means the count sits below the range. Readers feel it as a jump: welcome straight to purchase, or story straight to review link with no proof between. The practical signs are replies asking questions the sequence should have answered, such as price, format, series order, or content level, and a final ask that earns taps but few completions. The fix adds the missing function — usually proof or objection handling — as one full email before the ask.
Gap too wide means more than four days between sends. Readers feel it as a new conversation each time rather than one building thread. The practical signs are subscribers asking to resend the first gift, or replying to email three as if email one never arrived. The fix moves spacing into the one to three day band and keeps the same emails in the same order.
Daily barrage means a zero-day gap with several messages on the same day. Readers feel it as crowding, even when each message is short. The practical signs are same-day unsubscribes and spam complaints. The fix spaces sends at least one day apart so each job gets its own reading moment.
A pass means the count fits the range and spacing sits between one and three days. It does not promise sales or reviews. It only means the structure gives each necessary function a slot without exhausting the reader. Copy quality, offer strength, and list fit still decide the outcome.
Edge cases that change the plan
Zero subscribers is the most common edge for new authors. The tool returns an informational verdict and keeps the same range, because the shape should be ready before the list exists. Write the drafts now, load them into your sending setup later, and enter the real list size when subscribers arrive. Do not add extra emails to compensate for a small list; extra length does not create readers.
One to two hundred subscribers is a small but real list. Keep the standard range and spend the saved planning time on the proof email, which is hardest with few readers. Ask early readers for one specific sentence each about what the book gave them, with permission to quote the first name. One concrete line from a real reader outperforms a long paragraph of author claims.
Five thousand or more subscribers raises the cost of weak sends. Keep the same range but review every email for a single job and a single link before scheduling. Large lists also produce more replies, so plan reply handling for email one and email three, where questions cluster. A short personal reply to a real question during a welcome run builds more trust than any extra broadcast.
Twelve planned emails hits the tool maximum and always warns as too many for every goal. No welcome run needs twelve messages; that volume belongs to a longer course or a regular newsletter spread over months. Split the material: keep the welcome run inside its range and move the surplus into the ongoing newsletter calendar.
Zero-day spacing always warns even when the count fits. Same-day stacks suit urgent service notices, not welcome runs. Give each message at least a full day so readers can act on one call to action before meeting the next.
Fourteen-day spacing hits the tool maximum and always warns as gap too wide. Two weeks between welcome messages means no welcome effect remains. If a long pause is unavoidable, restart the thread briefly when you return: one line recalling the earlier promise, then the new message.
Mixed goals in one run form a quiet edge. Authors sometimes want launch sales and reviews from the same five emails. The calculator accepts one goal at a time, so run it twice: once for launch shape, once for review shape. Then choose which job the welcome run carries and move the other job to a separate follow-up. A welcome run that asks for both purchase and review in one final email splits attention and weakens both asks.
Failure modes worth naming before you send
The missing single action is the most frequent failure. An email that links the sample, the review page, and the store in one block forces the reader to choose, and most readers choose nothing. Repair it by deleting two links and keeping the one that matches the email job. The map above assigns exactly one action per row for this reason.
The late gift is the second failure. When the promised sample or bonus arrives in email three instead of email one, subscribers who joined for the gift feel misled and leave before the proof. Repair it by delivering the gift in the first message and repeating the link once in email two for anyone who missed it.
The proof-free offer is the third failure. An offer with no reader words asks strangers to trust the author alone. Repair it by moving one proof email ahead of the offer and quoting specific reader lines with permission. General praise such as great book belongs at the bottom; specific outcomes and scenes belong at the top.
The double ask finale is the fourth failure. Two different requests in the last email — buy the book and leave a review, or buy the book and join another list — divide the final energy. Repair it by keeping one ask in the welcome run and scheduling the second ask for a later separate message after the first outcome arrives.
The endless reminder loop is the fifth failure. Adding just one more nudge each week turns a welcome run into an open-ended chase. Repair it by closing the run on the planned last day and moving non-responders into the regular newsletter, where future issues can carry fresh reasons to buy rather than repeated versions of the same ask.
The borrowed voice is the sixth failure. Copying phrases from another genre or another author makes the sequence sound polished but generic. Repair it by writing each email in the plain words you would use to a single reader, then reading it aloud once before scheduling. Awkward lines reveal themselves in speech faster than on screen.
Writing each email so the count works
Email one must arrive fast and stay short. State the book or gift, deliver the link near the top, name the coming rhythm in one line, and close with a small reply invitation. Aim for under two hundred words. Long origin stories belong later, after the reader has a reason to care.
Story emails need one scene, not a summary. Pick the moment in the book or in your research that made you keep going, describe it concretely, and connect it to the reader in two sentences. End with the sample link. Readers remember one vivid passage longer than a full outline.
Proof emails need names and specifics. Quote two or three readers with first names and permission, keep each quote under two lines, and add one line of context about who each reader is, such as mystery reader or memoir book club member. Avoid anonymous praise walls; they read as decoration.
Offer emails need facts in order: title, format, price, where to buy, what happens next. Put the purchase link twice at most — once after the facts and once at the close — and keep both pointing to the same destination. Competing store links in one email split taps and complicate measurement.
Objection emails need the actual doubt, not a straw version. Read past replies, reviews of comparable books, and questions from events, then pick the single most common hesitation. Answer it with verifiable detail: page count and reading time, series order and stand-alone status, content notes, or format availability. Link the sample that proves the answer.
Final asks need a clean close. Restate the offer in three lines, name any end date once, ask once, and stop. No new story, no new proof, no apology for asking. A short postscript with the link helps readers who scroll fast.
Review sequences need a lighter hand
Review asks differ from sales asks because the reader already paid with money or time. The tone must thank first and request second. Email one thanks and confirms receipt. Email two checks progress with genuine interest. Email three makes the single review request with a direct link and a clear statement that two or three honest sentences are enough. Email four, when used, repeats the link once without reproach.
Never offer payment or gifts conditioned on a positive review. Platform rules and reader trust both forbid tilted incentives. A neutral thank-you gift available to all readers regardless of review content is a different matter, but keep it outside the ask email so no reader reads it as a trade.
Make the review path short. Link directly to the review form or the book page review section rather than to a general storefront. Each extra tap loses reviewers who meant to help. Test the link yourself on a phone before scheduling, because most review taps happen on mobile.
Handle non-response with grace. Many readers finish and forget, or never finish at all. One reminder is courteous; repeated reminders are not. Move silent readers into the regular newsletter where future books can earn the review that this one did not.
Evergreen sequences must stay valid all year
Evergreen means a subscriber who joins in any month reads a working offer. Remove launch dates, limited-week bonuses with fixed ends, countdown language tied to a past event, and references to seasons or holidays unless the book itself is seasonal. Read the full draft and ask of every line whether it stays true twelve months from now.
Gifts in evergreen runs need durable delivery. Host the sample or bonus at a stable address you control and check the link quarterly. A broken gift link in an automated run quietly burns trust for months before anyone tells you.
Offers in evergreen runs need stable pricing language. State the current price without promising it will never change, and avoid claiming a discount unless the mechanism renews for every new subscriber. When the price changes, update the evergreen draft the same day.
Length discipline matters more in evergreen because the run repeats for every subscriber. One weak email wastes attention hundreds of times. Review the evergreen run twice a year: cut anything that repeats, refresh proof with newer reader lines, and confirm every link still lands where intended.
Launch sequences must build toward one week
Launch runs differ because they point at a short window when attention, bonuses, and early momentum coincide. Order the emails so desire peaks in the launch week, not three weeks early. Early messages build interest; the offer and the bonus land when the purchase path is fully ready, including the store page, the price, and the bonus delivery.
Coordinate the email days with the store reality. Do not send the offer email before the purchase link works on both desktop and phone. Do not promise a bonus file you have not tested by downloading it yourself. One broken promise during launch week costs more than a late email ever could.
Prepare replies for launch week. Readers ask about formats, gifts, bundles, and deadlines in the same few days. Draft short answers in advance and keep them near your inbox. Fast accurate replies during the ask window convert hesitant readers who would otherwise drift.
Close the run cleanly after the bonus ends. Thank buyers, name what comes next such as the regular newsletter rhythm, and stop asking. Lingering launch asks after the deadline teach readers that deadlines do not matter, which weakens the next launch.
Measuring the run with your own numbers
Judge the sequence with counts from your own sends, not with general benchmarks repeated online. Track per email how many messages were delivered, how many were opened, how many taps each link received, how many replies arrived, and how many unsubscribes followed. Small lists produce noisy percentages, so read the raw counts alongside any rate.
Compare emails inside the same run before comparing across runs. If email three earns far fewer opens than email two, the end of email two probably failed to set up the next message. If taps cluster on an early link but the final ask earns few completions, the offer may lack proof or the purchase path may add friction. Fix the specific handoff rather than rewriting everything.
Replies deserve manual reading. Sort them into questions about the book, problems with links or gifts, and expressions of interest or thanks. Questions reveal the missing objection email. Link problems reveal testing gaps. Thanks reveal the lines worth keeping and reusing as proof with permission.
Unsubscribes during a welcome run are partly normal, because some subscribers joined for one gift and want nothing more. Rising unsubscribes on a specific email still deserve attention: read that message for crowding, repetition, or tone shifts. Removing or merging one weak middle email usually helps more than softening every message.
Review runs need a separate tally: how many review links were tapped and how many new reviews appeared within two weeks of the ask. The two counts will never match, since many tappers post later or not at all. Track the pairing over several sends to learn your own pattern, then use that pattern to plan rather than borrowing someone else conversion claim.
Questions authors ask next, answered in fresh words
Should a welcome run and a regular newsletter overlap. Pause general broadcasts for new subscribers while the welcome run is active, or set the system to suppress duplicates where possible. Meeting two different voices in one week confuses new readers. Once the run ends, introduce the newsletter rhythm in the closing line so the transition feels planned.
Does genre change the ideal count. The goal range already absorbs most genre differences, because launch, evergreen, and review jobs stay constant across categories. Voice and proof change by genre — a thriller leans on pace, a romance leans on feeling, a guide leans on outcomes — but the number of slots stays inside the same range. Adjust examples and quotes, not the count.
Can welcome emails go out daily. One day apart is the tightest spacing the calculator accepts without warning, and it suits short launches where the window is genuinely brief. Daily sends demand strong material every day; if any draft feels padded, widen to two days rather than forcing a weak daily message. Never stack several welcome emails on the same day.
What belongs in the subject line. Name the single benefit or question inside, keep it under fifty characters where possible, and avoid shouting punctuation. The subject promises, the opening line delivers, and the closing line sets up the next email. Test subjects by reading the inbox preview on a phone, where most subscribers first meet the message.
How long should each message be. Short enough to be read in one sitting: roughly one hundred fifty to three hundred words for most welcome emails, slightly longer for the story or objection answer when detail is required. One idea per email keeps length natural. When a draft passes four hundred words, look for a second idea hiding inside and move it to its own message or cut it.
Should images and design carry weight. Plain readable text with one clear link outperforms heavy layouts in most welcome runs, because it loads fast on phones and reads like a personal note. One cover image in the offer email is enough. Decorative banners add size without adding decisions.
What if early readers give no quotable proof yet. Use your own specific claims tied to verifiable facts: research sources, lived experience, sample scenes, or beta reader counts stated honestly. One line stating that twelve beta readers finished and nine asked for the sequel says more than a paragraph of adjectives. Replace placeholder proof with real reader words as soon as permission arrives.
When should the run start. Immediately after signup while intent is fresh. A welcome email delayed by days arrives after the subscriber forgot the signup moment. Automation that sends email one within minutes and spaces the rest by the planned gap preserves the context that makes the later asks work.
Where this work continues
Drafting the sequence is only the middle of the job. The messages must live somewhere they can send on schedule, connect to the signup form, and record what readers do next. The Author Desk at slash author-desk is the product destination this page routes to, and it is where list setup, scheduling, and follow-up planning continue. Keep this page open for the length math and the day map, then carry the finished drafts into the Author Desk workflow so the run you planned becomes the run your subscribers actually receive.