The short answer: which emails to send before launch
Send one email per week plus a launch-day email. With six weeks left that means seven sends in this order: announcement, story setup, excerpt, social proof, behind the scenes, countdown, and launch day. Each send has one job, one link placement near the top, and one repeat of the link near the sign-off. The announcement names the date, the middle four sends earn attention, and the final two sends ask for the order. That rhythm is the whole plan, and the tool below turns it into dated sends for your exact runway.
If you remember nothing else, remember the split between earning and asking. The first five sends earn the click by giving readers something useful or interesting: the date, the premise, a sample, proof from early readers, and a look at your process. The last two sends spend that attention by asking clearly for a purchase or preorder. Authors who struggle with pre-launch email almost always flip this ratio, asking in every send and earning in none, which trains subscribers to ignore the sequence right when it matters most.
The direct answer restated in numbers: a six-week runway to 2,000 subscribers supports seven emails from day minus 42 to launch morning, with each send reaching about 700 opens and 100 clicks under illustrative planning assumptions, and the full sequence producing roughly 700 launch-week store visits from the email channel alone. Shorter runways compress the same logic into fewer sends, and a missing list turns the runway into a growth period first and a selling period second. Everything below explains how those numbers are calculated, when to adjust them, and what each email should contain.
How the sequence math works
The tool uses three inputs: weeks until launch, current subscriber count, and genre. From weeks it derives the email count with a simple clamped rule: add one to the week count, then keep the result between two and eight. Six weeks therefore gives seven emails, three weeks gives four, one week gives two, and anything above seven weeks caps at eight so long runways do not turn into spam schedules. The lower bound guarantees at minimum an announcement plus a launch-day send, and the upper bound protects deliverability on very long runways.
Send days spread evenly from the first day of the runway to launch morning. The tool multiplies weeks by seven to get runway days, then places the sends at equal fractions of that span with rounding to whole days. At six weeks the runway is 42 days, and seven sends land on day minus 42, day minus 35, day minus 28, day minus 21, day minus 14, day minus 7, and launch day itself, which is the familiar same-weekday rhythm with the final two sends forming the launch-week push. At three weeks the runway is 21 days and four sends land on day minus 21, day minus 14, day minus 7, and launch day. The spacing is deterministic, so the same inputs always produce the same calendar, and you can shift individual sends by a day or two for weekends without breaking the plan.
Open and click estimates come from illustrative planning assumptions tied to genre, not from measured platform data or any live integration. Romance assumes a 38 percent open rate and a 5 percent click rate, mystery assumes 36 and 4.5, fantasy assumes 35 and 4.5, nonfiction assumes 32 and 4, and other fiction assumes 35 and 4.5. Each rate applies to delivered subscribers, so expected opens equal list size times the open rate and expected clicks equal list size times the click rate. These are planning numbers you use to size effort and compare scenarios, and your real rates will differ based on list age, signup source, subject lines, and inbox placement.
Worked numbers for the default case make the arithmetic concrete. Start with 2,000 subscribers in romance at 38 percent opens and 5 percent clicks. Expected opens per send equal 2,000 times 0.38, which is 760, rounded in tool copy to about 700 to avoid false precision. Expected clicks per send equal 2,000 times 0.05, which is exactly 100. Across seven sends the illustrative total is 700 clicks, and the launch-day send alone contributes about 100 of those visits. If your real open rate settles at 30 percent instead of 38, the same list delivers 600 opens per send, which is still a workable launch-week base, and the planning value of the math is that you discovered the gap before release week rather than during it.
Illustrative example 1 (hypothetical): six weeks, 2,000 subscribers, romance
Consider a hypothetical romance author with six weeks left and 2,000 subscribers, used here as an illustrative example rather than a promise of results. The tool returns seven sends: announcement on day minus 42, story setup on day minus 35, excerpt on day minus 28, social proof on day minus 21, behind the scenes on day minus 14, countdown on day minus 7, and launch day on day zero. Each send shows about 760 illustrative opens and 100 illustrative clicks, which the author treats as a ceiling for planning store-visit math. The practical schedule is one email every Tuesday, plus the launch-day send on release morning, with no midweek extras until the final week.
What makes this example work is the separation of roles across the middle sends. The story-setup email carries the premise for readers who forgot why they subscribed, the excerpt email gives skimmers a reason to care within ninety seconds, the social-proof email answers the quiet objection that nobody else wants this book, and the behind-the-scenes email gives loyal readers a forwarded-worthy moment. By the time the countdown send arrives on day minus 7, the list has received four value-first touches and one date-setting touch, so a direct selling ask feels like a natural next step instead of a cold pitch. The launch-day email then repeats the store link high on the page and once more near the close, and the author watches day-zero clicks as the single number that matters.
Failure handling inside this example is straightforward. If the excerpt send underperforms the illustrative 760 opens by a wide margin, the author does not rewrite the whole sequence, and instead shortens the subject line of the social-proof send and moves the store link above the first image. If unsubscribes spike after the behind-the-scenes send, the author checks whether that email buried its point below three screens of process detail, because long process essays are the most common cause of late-sequence fatigue. The sequence survives single-send weakness as long as the excerpt, countdown, and launch-day sends stay intact, which is why those three are never the ones cut.
Hypothetical example 2 (illustrative): three weeks, 500 subscribers, mystery
Take a second hypothetical case, labeled illustrative because every rate in it is an assumed planning figure: a mystery author with three weeks left and 500 subscribers. The tool returns four sends across a 21-day runway: announcement on day minus 21, excerpt on day minus 14, countdown on day minus 7, and launch day on day zero, with story setup, social proof, and behind the scenes folded or dropped. At the mystery assumptions of 36 percent opens and 4.5 percent clicks, each send reaches about 180 opens and about 22 clicks, so the full compressed sequence represents roughly 88 illustrative store visits before any sharing or forwarding. That total will not carry a launch alone, which is exactly the honest conclusion the math is supposed to surface.
The tactical lesson of the short runway is compression without stacking. Each send goes out immediately on its spaced date, gaps stay at six to seven days, and no two selling emails sit adjacent except the unavoidable countdown-to-launch pair at the end. The announcement send must do double duty by naming the date and sketching the premise in three sentences, because there is no separate story-setup send to catch readers who forgot the book. The excerpt send becomes the hardest-working email in the sequence, carrying the sample, one early-reader line, and the preorder link in a single tight layout. Authors in this position often want to add extra sends to compensate for lost time, but a fifth send inside 21 days usually suppresses the launch-day open rate, so restraint is the higher-performing choice.
This author should also pair the sequence with one growth action per week, because 500 subscribers at 22 clicks per send leaves little margin for soft opens. A reader magnet linked from the announcement send, one newsletter swap with a comparable mystery author in week two, and a short excerpt post on the platform where current readers already gather can each add a meaningful percentage to the launch-day send. The sequence itself stays at four emails, and the extra effort goes into the audience those emails reach rather than into more emails.
Hypothetical example 3 (illustrative): eight weeks, zero subscribers, nonfiction
A third illustrative hypothetical covers the hardest starting point: eight weeks left, zero subscribers, nonfiction. The tool still returns a schedule, capped at eight sends, with per-send estimates of zero opens and zero clicks, which reads as a failure until you interpret it correctly as a build order. The verdict block says the runway is list-building time, and the recommendations name the only two emails to draft now: announcement and excerpt. Everything else waits until weekly signups give the later sends someone to reach.
Week by week, this author treats list growth as the pre-launch campaign. Weeks eight through six carry a reader magnet, such as a checklist, starter chapter, or worksheet tied to the book promise, plus one outreach action per week like a guest post, podcast appearance, or swap with a small aligned list. Weeks six through four draft the announcement and excerpt sends while signups accumulate, with subject lines written to the magnet audience rather than to a general crowd. Weeks four through two add social proof from beta readers and a behind-the-scenes send that doubles as forwardable content, and the final two weeks run countdown and launch day to whatever base has been built. Even 150 subscribers at the nonfiction assumptions of 32 percent opens and 4 percent clicks put about 48 opens and 6 clicks behind the launch-day send, which is small but real, and more importantly the author enters launch with a list asset that compounds into book two.
The mistake to avoid here is writing all eight emails before anyone subscribes. Drafting the full sequence feels productive and quietly consumes the exact weeks that should have gone to growth, and then the polished emails launch to an empty room. Write two, grow weekly, and let signup language from the magnet teach you which subject lines the eventual countdown send should use.
The purpose of each email, in send order
Announcement opens the runway and has exactly one measurable goal: readers who can state the release date without opening the email again. Name the book, name the date, name who it serves in a single sentence, and ask readers to save the date or watch for the excerpt rather than asking for money now. Keep it short enough to read on a phone in under a minute, because the announcement earns its keep through clarity and forwarding, not through persuasion. A simple PS line pointing to the reader magnet captures the subscribers this send will attract.
Story setup rescues the large share of any list that subscribed months ago and forgot the premise. Restate the situation, the central tension, and the stakes in plain sentences, and close with a single curiosity question the book answers. For fiction this means character, problem, and cost of failure; for nonfiction it means reader, current pain, and promised outcome. This send should deliberately contain no excerpt and no testimonials, because its job is orientation, and mixing jobs is how middle-sequence emails become skimmable walls of text.
Excerpt is the trial close of the sequence and usually the highest-clicked non-launch send. Offer a short sample that ends on tension: a chapter break for fiction, a worked step for nonfiction, and a link labeled by what happens next rather than by format. Frame the sample with two sentences before and one question after, then place the preorder or save link directly beneath the sample so momentum converts immediately. If you test anything in the sequence, test the excerpt subject line and the position of this link, because small changes here move more launch-week visits than any other single edit.
Social proof answers the objection every reader holds silently, which is whether anyone like them already trusts this book. Use two or three short early-reader lines with first names and roles, plus one line of your own that connects each quote to a concrete promise. Keep quotes brief and specific, naming what the reader felt or finished rather than generic praise, because vague praise reads as filler and specific praise reads as evidence. One store or preorder link near the top is enough, since this send sells by proxy rather than by pitch.
Behind the scenes gives loyal readers something worth forwarding and gives you a break from selling language. Tell the story of one decision: a cut chapter, a changed ending, a research trip, or a cover choice, and connect that decision to a benefit the reader receives. End with a question that invites replies, because replies lift sender reputation and hand you language for the countdown send. This is the send to cut first on short runways, since it builds warmth rather than urgency, and warmth without time rarely converts before launch day.
Countdown is the first direct selling send and the strictest one to write. State what changes and when: price, bonus, availability, or event access, with the exact day and time in the reader timezone you serve most. Repeat the link twice, keep every paragraph under three lines on mobile, and remove every secondary link that competes with the order action. Readers forgive urgency they can verify and punish urgency they cannot, so name a real boundary rather than manufacturing pressure.
Launch day is the shortest email and the most clicked. Lead with the live link above everything else, state the book is available now in one sentence, and add at most two supporting lines such as formats and one reader quote. Send in the morning of release day in your largest reader timezone, and resend only to non-openers the next morning with a changed subject line rather than resending to the whole list. The launch-day send is not the place for thanks, process, or long recaps; those belong in the post-launch email after the order window has done its work.
Timing, spacing, and send-day rules
Same weekday cadence is the default because it teaches the list when to expect you and keeps spacing honest without a spreadsheet. Pick the weekday with your best historical opens, or Tuesday through Thursday morning if you have no history, and hold that slot for every send except countdown extras and launch day. The tool spread already spaces sends evenly, so your operational task is protecting those gaps: at least five days between value sends, at least three days anywhere on runways under three weeks, and never two selling sends on consecutive days except the countdown-to-launch pair that the calendar forces.
Morning sends in the largest reader timezone beat midnight sends in every genre this planner covers, because the launch-day email in particular earns most of its clicks in the first six hours. If the list splits across continents, favor the timezone holding the plurality of subscribers and note the time explicitly in the countdown send so nobody misreads the boundary. Weekend sends are acceptable for the behind-the-scenes email, which benefits from longer dwell, but keep announcement, excerpt, countdown, and launch day on weekdays when attention and store traffic run higher.
Resends deserve a narrow rule rather than a habit. Resend the launch-day email once, the next morning, to non-openers only, with a new subject line and no other changes, then stop. Resending earlier sequence emails routinely trains subscribers to open late and depresses the per-send open rates the whole plan depends on. One disciplined resend captures genuine misses; repeated resends manufacture fatigue that looks exactly like a dead list.
Subject-line templates that survive the inbox
Every subject template in the tool follows the same constraints: under fifty characters where possible, no misleading urgency, and a promise the email body keeps within the first screen. Announcement reads as a date save, story setup reads as orientation, excerpt reads as access, social proof reads as evidence, behind the scenes reads as a decision story, countdown reads as a boundary, and launch day reads as availability. The table output gives you one template per send in order, and your customization task is inserting the book title, the date, and one concrete noun from the book rather than rewriting the structure.
Small genre adjustments improve these templates without changing their skeleton. Romance subjects can name the trope or pairing dynamic once, mystery subjects can pose the central question without spoiling the turn, fantasy subjects can name the place or system readers will enter, and nonfiction subjects should name the outcome and the reader, such as who finishes what by when. Keep personalization to title, date, and that one noun, because over-personalized subject lines in pre-launch sequences consistently underperform clear ones in small-list planning reviews.
Length discipline matters more than cleverness across the full sequence. If a subject exceeds sixty characters, cut the adjective before cutting the noun, and if two consecutive subjects start with the same word, rewrite the second even when both are accurate. The sequence is read as a set in the inbox weeks later, and visual variety across seven subject lines does quiet work that no single clever line can replace.
Genre-specific guidance
Romance lists tend to open and click at the top of the illustrative ranges used here, which means frequency tolerance is slightly higher but expectation discipline is stricter. Send the full seven on a six-week runway, keep the excerpt send early enough that tropes are explicit by day minus 28, and use social proof that names emotional payoff rather than plot mechanics. Avoid stacking bonus offers across both countdown and launch day, because romance readers respond to one clear boundary and discount the second. The behind-the-scenes send performs well when it covers a cut scene or an alternate ending beat, and poorly when it becomes publishing process detail.
Mystery and thriller lists reward questions and punish spoilers, so calibrate every middle send around curiosity preserved. The story-setup send should pose the inciting situation and stop, the excerpt should end mid-tension rather than at a resolution point, and social proof should quote pace and twists without naming them. Countdown language stays factual about price or availability rather than dramatic about the story, because drama in the selling sends cheapens the tension the book itself should deliver. If opens dip mid-sequence, shorten the next subject to a single question and move the link above the sample rather than adding a new send.
Fantasy and science-fiction lists tolerate longer emails and reward world detail, but only when detail arrives as story rather than encyclopedia. Let the story-setup send introduce one place, one cost of magic or technology, and one character choice, then stop before systems exposition. The excerpt send should immerse within the first three paragraphs, which usually means starting inside a scene rather than inside history. Social proof quoting immersion and pace outperforms proof quoting worldbuilding depth, and the behind-the-scenes send covering one cut creature, system, or chapter earns more forwards than any process recap. Guard the countdown send against lore creep, since one paragraph of world detail there costs clicks that a single boundary sentence would have kept.
Nonfiction lists behave most transactionally, which clarifies every send. Announcement names the reader and the outcome with a date, story setup restates the pain and the method in three sentences, excerpt delivers one complete usable step rather than a teaser fragment, and social proof quotes finished results with names and roles. The behind-the-scenes send should cover one rejected chapter or framework choice and the reader benefit of that cut, not writing routine. Countdown and launch-day sends name formats, bonuses, and the exact boundary, because nonfiction readers convert on clarity about what they receive and when the terms change. With the lowest illustrative open rate in this planner, nonfiction authors should invest the most in signup-source quality, since a smaller engaged list outperforms a larger cold one at every send.
Other fiction, including literary, historical, and cross-genre work, borrows the romance cadence with mystery restraint. Keep all seven sends on a full runway, let the excerpt carry voice rather than plot summary, and choose social proof that quotes feeling and finish rather than twists. The announcement send needs one extra sentence of orientation compared with category fiction, because cross-genre readers decide fit more slowly. Countdown stays plain and factual regardless of how lyrical the book prose runs, since the selling sends serve readers who have already decided they are interested and now need only the link and the boundary.
Edge cases and failure modes
A stalled list that stops growing mid-runway is the most common edge case, and the fix sits outside the sequence rather than inside it. Hold the send calendar steady and redirect effort to one magnet and one swap per week, because adding sends to a stalled list accelerates fatigue while adding subscribers lifts every remaining send. Watch the excerpt send as the diagnostic: stable opens there with flat growth means the sequence is healthy and acquisition is the constraint, while falling opens there means content or deliverability needs attention before any growth spending.
Sudden open-rate drops on a single send usually trace to three causes: a vague subject, a link-heavy layout that triggered filtering, or a send-time shift into a crowded hour. Diagnose in that order by comparing the subject against the template structure, counting distinct links, and checking the send timestamp before rewriting anything. A one-send dip that recovers on the next send is normal variance and needs no structural change, while two consecutive dips justify shortening the next email by a third and moving its primary link above the first image.
High unsubscribes after a specific send identify that email as the problem with unusual precision. Behind-the-scenes sends cause the most late-sequence exits when they run long on process, and story-setup sends cause early exits when they assume knowledge new subscribers lack. Trim the offending send to one idea, restore the single-link hierarchy, and keep the remaining calendar unchanged rather than apologizing with an extra email that compounds the damage. Small lists feel each exit more acutely, so read unsubscribe counts alongside opens rather than alone: three exits on 180 opens deserves the same calm response as thirty on 1,800.
Deliverability trouble looks different from content trouble and needs its own response. Content trouble shows as falling opens with steady delivery, while deliverability trouble shows as abrupt collapse across segments or a spike in spam placement. The sequence-level protections are consistent authentication, steady cadence rather than bursts, plain-text-friendly layouts with few images, and reply invitations that earn engagement signals. No subject-line rewrite fixes an authentication or reputation problem, so check the technical base before rewriting copy that was never the cause.
Zero-list and tiny-list cases are edge conditions the tool handles with an explicit info verdict rather than fake estimates. The honest reading is that per-send math at zero subscribers equals zero, and the runway converts to growth weeks with two drafted emails waiting. Tiny lists under 150 subscribers should still run the full spaced cadence, because the discipline of the calendar matters more than any single send total, and each send doubles as a forwarding asset that can add the subscribers the next send needs. Judge these sequences by replies, forwards, and weekly signup delta rather than by raw open counts that small denominators make volatile.
Overlong runways above eight weeks create a subtler failure mode where early attention decays before the selling sends arrive. The tool cap of eight emails is the first defense, and your second defense is deliberate quiet weeks with no sends between the announcement and the story setup when the calendar allows. Fill those quiet weeks with growth and drafting rather than with extra emails, and never move the countdown send earlier to fill silence, because countdown urgency only works adjacent to launch. If the runway extends past twelve weeks, plan two phases with a rest gap instead of stretching one sequence across the entire span.
List health, consent, and what not to do
Every send in this sequence assumes permission you can defend: subscribers who joined through your magnet, site, events, or swaps with clear expectations. Purchased lists, scraped addresses, and borrowed lists without consent do not become acceptable because a launch approaches, and they damage the deliverability that your real subscribers depend on. The announcement send is the worst place to add questionable addresses, since early spam placement poisons the reputation every later send inherits. Growth tactics in this guide all assume opt-in sources, and the illustrative rates assume a permission-based list as well.
Frequency promises from signup sources constrain the sequence more than most authors expect. If the magnet promised monthly mail and the sequence suddenly sends weekly, the first two sends will underperform no matter how good the subjects read. Bridge the gap inside the announcement send with one sentence that names the launch cadence and its end date, which converts surprise into anticipated mail. After launch day, return to the promised cadence promptly rather than extending launch frequency into the post-launch weeks.
Accessibility and layout choices affect measured opens more than copy tweaks once the basics are right. Use readable body sizes, real text rather than image-only emails, descriptive link text that states the destination, and alt text on every image so blocking does not erase meaning. Keep total images low and total distinct links to two placements of the same destination, because link proliferation is a reliable suppressor of both clicks and inbox placement. These are unglamorous decisions that protect the illustrative rates from degrading into much lower realized ones.
Questions authors ask next (going deeper than the quick answers)
How many emails is too many before launch? The tool cap of eight encodes the practical ceiling for runways up to twelve weeks, and the one-per-week-plus-launch-day rule keeps most plans between four and seven. Reader tolerance depends less on raw count than on spacing and variety: seven spaced sends with rotating purposes outperform four stacked sends with repeated pitches. If you feel the urge to add a ninth send, convert it into a better excerpt or countdown email instead, since strengthening the highest-leverage sends beats extending the calendar.
Should announcement and excerpt both carry a buy link? Yes, with different framing and weight. The announcement link points to a save, wishlist, or preorder page framed as date-keeping rather than purchasing, placed once and described as optional. The excerpt link sits directly under the sample as the natural next step and carries the sequence first real purchase framing. Later selling sends then escalate cleanly instead of introducing the link for the first time under deadline pressure.
What belongs in social proof when early readers are few? Two genuine lines beat five vague ones, and specific comparisons beat generic praise in every genre covered here. A single sentence naming what a reader finished, felt, or stayed up for carries more weight than a paragraph of adjectives. When beta readers are truly scarce, one honest line from a crit partner plus one line of your own connecting it to the book promise is enough, and manufacturing quotes is never acceptable regardless of list size.
How should nonfiction and fiction excerpts differ? Fiction excerpts should break on tension inside a scene, while nonfiction excerpts should complete one usable step the reader can apply the same day. The fiction reader decides with feeling and continues to find out what happens, and the nonfiction reader decides with utility and continues to get the full system. Both excerpts stay short enough to finish on a phone, and both place the next-step link immediately after the sample rather than after commentary about the sample.
When does the countdown send go out if launch shifts? Keep countdown adjacent to the real date by moving it with the launch, not by sending it on the original schedule against a moved release. A countdown that expires before the book is available spends trust that the launch-day send cannot recover, and readers remember false urgency longer than they remember any single subject line. If the date slips by more than a week, insert one plain update email that names the new date and reason in three sentences, then resume the planned countdown position.
What if the launch-day email flops? Diagnose before reacting by checking delivery first, opens second, and clicks third. Delivery collapse points to reputation or authentication issues that no resend fixes without repair. Opens collapse with steady delivery points to the subject line and sender name, which the non-opener resend with a rewritten subject addresses directly. Clicks collapse with steady opens points to link placement or page friction, which means moving the link above the fold and testing the store page path before any further email. One measured correction beats three hurried extra sends.
Tracking the numbers week by week
Plans improve when weekly reality replaces assumptions, so record opens, clicks, unsubscribes, and new signups after every send while the runway is live. Compare each result against the illustrative per-send estimates from the tool, note which purpose over- or under-delivered, and carry one lesson into the next subject line and link position. This running record is what turns a generic eight-email cap into a personal cadence you can reuse for the next book with far less guessing.
To keep that record somewhere durable, track these numbers inside Author Desk at /author-desk alongside the rest of your launch checklist. Log each send date with its opens, clicks, and signup delta on your Author Desk page at /author-desk, then review the trend before drafting the countdown email. That single habit connects the planner estimates to real subscriber behavior and keeps every future sequence grounded in your own list history.
A closing checklist for send week
Confirm the store, preorder, or save link resolves correctly from a logged-out phone before the countdown send leaves, because every illustrative click in the plan becomes a wasted open against a broken destination. Verify the launch-day email link placement renders above the first screen on small phones, with the repeated link intact near the sign-off and no competing secondary links. Draft the non-opener resend subject in advance so the morning-after decision is execution rather than composition under stress. Name one growth action for each remaining week, even during send week, since launch-day forwarding plus one swap or post extends the audience the resend can still reach. Then send in order, log the numbers, and let the sequence do the compounding work it was built to do.