How to Build a Drip Email Sequence for a Book Launch
A book launch is mostly an email problem. Here is a 7-email drip sequence that takes a curious reader through your story, your reviews, and your buy link — without sounding like a marketing brochure.
A book launch is mostly an email problem.
Not the writing — that's the actual book. Not the cover — that's the designer. Not the Amazon listing — that's a checkbox. The hard part is the gap between "stranger discovers your existence" and "stranger gives you $14.99 for an ebook by someone they've never met."
That gap is closed by email. And not the kind of email where you blast your list with "MY BOOK IS OUT!" the day of launch and then go silent. The kind that runs in the background for every reader who finds you, takes them through your story, your reviews, your free chapter, and then gives them a soft, well-earned ask.
That's a drip sequence. Here's the one I recommend for indie authors.
Why "launch day blasts" don't work anymore
The pre-2020 playbook was: build an email list, queue a giant blast for launch day, hit send, watch Amazon rank go up for three days.
That still works if you have a list of 10,000 warm subscribers who already know you. For most indie authors writing their first or second book, the list is closer to 800, most are cold, and a single blast converts at 1–2%. You sell 10 books, the rank spikes for 12 hours, and then it sinks back into the long tail.
The post-2020 reality is that book launches don't have a single day. They have a long tail of new readers discovering you over months — from a podcast appearance, a guest post, a TikTok, a giveaway. The job of the drip sequence is to greet each one of those readers properly, whenever they show up, without you doing any work.
The sequence
Seven emails over fourteen days. Subscriber arrives any day; sequence starts immediately.
| # | Day | Subject | Goal |
|---|---|---|---|
| 1 | 0 | Welcome — and here's the first chapter | Deliver the magnet, set tone |
| 2 | 2 | Why I wrote this book | Build voice |
| 3 | 4 | The scene that took me a year to write | Showcase craft |
| 4 | 6 | What three early readers said | Social proof |
| 5 | 9 | A question I get from readers (and my answer) | Engagement |
| 6 | 11 | Behind the scenes — the cover that didn't make it | Intimacy |
| 7 | 14 | If you want the full book, it's here | The ask |
Every email below is a template — replace bracketed bits with your own. Keep it under 350 words per email. Indie author emails are most effective when they read like a letter, not a brochure.
Email 1 — Welcome + first chapter (Day 0)
Subject: Welcome — and here's the first chapter
Hi {first_name},
Thanks for subscribing.
You said you wanted to read the first chapter of {book_title}, so let's not bury the lede — here it is, as a PDF.
Quick note on what you've signed up for: over the next two weeks you'll get six more emails from me. Some of them are short stories about writing the book; some are behind-the-scenes things I don't share publicly; one is a peek at the original cover that almost made it onto the printed copy.
If at any point you'd rather not, the unsubscribe link is at the bottom of every email.
Hit reply and tell me what you're reading right now — I read every reply.
Talk soon, {your_name}
Email 2 — Why I wrote this book (Day 2)
Subject: Why I wrote this book
There's a version of this email where I tell you that {book_title} is "a thrilling story of redemption" with "characters that will stay with you." You can read that version on the Amazon page.
The real version is this: {one-paragraph honest origin story — what was going on in your life, what question you were trying to answer, what made the book unavoidable}.
That's what's actually in the book. If that question is at all interesting to you, you'll like it.
— {your_name}
Email 3 — The scene (Day 4)
Subject: The scene that took me a year to write
There's a scene in chapter {x} that I rewrote {n} times.
{Brief description of the scene — no spoilers, just the emotional weight of it. Why it kept resisting. What finally broke it open.}
The version that's in the book now is the {nth} draft. I cut {y} pages between draft {a} and draft {b}.
Writing a book is mostly subtraction, it turns out.
— {your_name}
Email 4 — Early reader reactions (Day 6)
Subject: What three early readers told me
Three quotes from real early readers (ARC reviewers, Goodreads, friends). One sentence each. No filler.
"{Quote 1}." — {Name}, {city}
"{Quote 2}." — {Name}
"{Quote 3}." — {Name}, {context}
If you want to be one of the early readers for the next book, just reply to this email — I keep a small list of people who want advance copies.
— {your_name}
Email 5 — Reader question (Day 9)
Subject: "Where do your characters come from?"
This is the question I get most.
{Two paragraphs answering honestly. Pick a character from the book; describe the real person or composite who inspired them; describe how that person became the character; describe what you had to invent.}
Got a question I haven't answered? Reply and I'll add it to a future email.
— {your_name}
Email 6 — The cover that didn't make it (Day 11)
Subject: The cover that almost was
{Embed: a JPEG of the rejected cover, with one paragraph of context. Why your designer pitched it. Why you rejected it. What the final cover does better.}
It's a small thing, but choosing the wrong cover would have changed who picked up the book entirely.
— {your_name}
Email 7 — The soft ask (Day 14)
Subject: If you want the full book
This is the only email in this sequence with an ask.
Over the last two weeks you've read the first chapter, the origin story, a peek at the writing process, what other readers thought, and a couple behind-the-scenes things I don't share publicly. You've got a pretty good sense of whether {book_title} is for you.
If it is, here's where it lives:
If you've already grabbed it: thank you. Honestly. Reply with what you thought and I'll write back.
If it's not for you, no hard feelings — you'll roll into my normal monthly newsletter starting next week, where I write about {your normal newsletter beat}.
Either way, thanks for reading.
— {your_name}
What makes this sequence work
Three things.
The ask is last. Six emails of investment, one email of pitch. Most launch sequences front-load the sale because the author is anxious to convert. Anxious converts poorly.
Every email is replyable. Six of the seven emails end with a direct invitation to hit reply. That's not just warmth — it's a deliverability signal to Gmail. A sender who gets replies stays out of the promotions tab.
Email 7 doesn't sell to people who already bought. The "if you've already grabbed it" line is small but huge. Repeat-buyer fatigue kills future trust. Acknowledging the people who already converted tells them you noticed.
Setting it up
You need a tool that does drip sequences — pre-written emails that go out automatically X days after subscribe, in order, regardless of when the subscriber arrived.
If you're already on Substack, Substack itself doesn't support drips. You need to add a sidecar tool that handles the welcome arc while Substack handles your ongoing newsletter. The Substack + drip setup is documented here.
If you're starting from scratch, Drippery lets you write the seven emails above, embed a subscribe form on your author site, and runs the sequence automatically for every new subscriber — for free, up to 500 subscribers. That's enough to launch your first book.
The pre-launch version
A few authors have asked: can I run this sequence before the book is out, to build a launch list?
Yes, and you should.
Modify email 7 to say "the book launches {date}, here's where to preorder" instead of an immediate buy link. Modify email 1 to say "as a thank you for subscribing pre-launch, you'll get the first chapter early." Everything else stays the same.
The sequence will warm up subscribers in the months before launch, and on launch day you don't blast — you let the existing automation do the work and add a single celebratory email to the broader newsletter.
What to do this week
Pick three emails from the seven. Email 1, email 4, email 7. Those are the load-bearing ones.
Draft them in plain text. No formatting. 200–350 words each. Set them to send on day 0, day 6, day 14.
Then ship.
You can always add the other four later. A three-email sequence that runs beats a seven-email sequence that lives in a Google Doc forever.
The book is the hard part. The sequence is twenty minutes of writing that compounds for years.