Every guide answering "how often should authors send a newsletter" hands you one number. Monthly. The number is not wrong. It is under-specified.
An author's year is not one rhythm. It is two seasons on the same calendar. There is a dark season, when the next book is being written and nothing new is about to land. And there is a launch season, six to ten weeks around a release, when the newsletter is the single most valuable asset the author owns. Sending the same monthly rhythm through both is one of two mistakes. Either the launch quietly comes and goes on a single email that fought for attention alongside twenty other announcements, or the dark season fills with weekly updates the reader did not sign up for and slowly stops opening.
The honest cadence is not a number. It is a schedule.
What the SERP says, and where it breaks
The consensus across the top guides is tight. Monthly is the floor, one to three sends a month is the sweet spot, weekly is reserved for authors with an unusually engaged list or a release event to hang the send on. The BookBub survey of 500+ authors lands at the same place. The consensus is the right answer to the wrong question.
The consensus is aimed at the beginner. Someone starting an author newsletter from zero needs one number, not a matrix. Monthly is a defensible one. It is consistent enough to stay present, and infrequent enough that a single-person operation can maintain it through a first-draft grind.
The one-number answer starts to leak the day the next book has a cover, a release date, and an ARC team.
The two seasons
Break the year into the two rhythms that matter.
Dark season. The default. Between books, between events, between anything the reader is actively waiting for. A monthly send is enough. Its job is not to inform. Its job is to keep the address warm so the pipe does not close. Miss two months in a row and the next email lands with a re-engagement penalty: opens drop, spam complaints rise, deliverability wobbles. Send monthly, on a set week of the month if you can commit to it, and you protect the list you spent years building.
Launch season. The window around a release. Six to ten weeks: two weeks before ARC requests go out, three to four weeks around the cover reveal and pre-order, launch week itself, and a two-week tail after release for early reviews and any list finish worth naming. The right cadence in this window is not monthly. It is weekly at a minimum, with two or three sends in launch week alone. Each send announces a specific thing. ARC signup open. Cover live. Pre-order incentive. Launch day. First reviews. The reader is not being spammed. They are being kept in the loop of a thing they signed up hoping to hear about.
Trying to average the two seasons produces the mistake most author newsletters make. Monthly through launch buries the release. Weekly through the dark season burns the list.
The math on why the schedule beats the number
Author newsletters are one of the better-performing categories in email. MailerLite's 2025 benchmarks, computed across roughly 3.6 million campaigns, put the author benchmark at 43.14% opens and 2.75% clicks. That is within a rounding error of the 43.46% median across all industries, and materially higher than most business categories. The list is engaged. It is a resource to spend carefully.
Two scenarios, same 3,000-subscriber list.
Author A sends monthly all year. Twelve sends. Opens sit at the benchmark for eleven of them. The one send that happens to land in launch week gets a modest lift, then the release is over. Reviews trickle in slowly because there was no coordinated ask.
Author B runs the schedule. Nine dark-season monthly sends. Six weekly launch-season sends spanning ARC ask, cover, pre-order, launch day, launch week, and the tail. Fifteen sends across the year, six of them concentrated in the eight weeks around release. Dark-season opens hold at the benchmark. Launch-season sends over-perform because the list is being asked about the specific thing they signed up hoping to hear about.
The delta between the two authors is not average opens per send. It is reviews on release week, pre-orders in the two-week pre-order window, and rank on launch day. Those three numbers are what a release is measured on. The monthly rhythm gets you the first. The schedule gets you all three.
What has to be tagged
The schedule requires two tags most author lists do not carry.
launch-book-N. The tag written on anyone who explicitly opted into hearing more about the current release. ARC signups, pre-order incentive redeemers, cover-reveal RSVPs. This tag receives the launch-season cadence. Everyone else stays on the dark-season monthly send.
arc-team-book-N. The tag written on the subset who committed to reading the ARC and posting a review. This tag receives a shorter, more direct sequence around release. The ARC delivery email. A reminder two weeks in. The launch-day "your review can go live now" note. A thank-you the week after. Four sends, all specific, all tied to a promise the reader made when they signed up. Even the most engaged ARC teams post at a 20–40% review rate, so the sequence is written to be forwardable, sharable, and easy to say yes to a second time.
You do not write two newsletters. You write one, and the tag decides who hears which edition and when. A subscriber who has been on the list four years and never opted into a launch tag is not spammed with weekly release updates. A subscriber who ticked the ARC box gets the four sends they signed up for, then rolls back to the monthly baseline.
The tooling: the tag is the launch lever
Two things most author-newsletter stacks do not do well.
A tag written the moment the reader clicks. The ARC signup form writes the tag on submit. The pre-order incentive redemption writes a different tag. The cover-reveal RSVP writes a third. Not a nightly Zapier reconciliation. Not a manual sort in a spreadsheet. If the tag arrives late, the automation it was supposed to trigger has missed the window, and the launch schedule collapses back into a broadcast.
A single list where every send filters by tag. Not four lists on four calendars. One list, one send calendar, tags deciding which subscribers hear which edition.
Most newsletter tools handle the second half of that and skip the first. The tag ends up on the form endpoint but does not carry through the sync. The ARC subscriber lands in the list looking like everybody else, and the cadence they get is whatever the default send calendar decided.
This is why Nashra tags at the page. The Magic Link that hosts the ARC signup writes the tag on submit. The subscriber list holds the tag as a column. The automation that runs the ARC sequence keys on the tag from the first email. Two seasons, one send calendar, no stitching.
The answer, in one line
For most authors, the honest cadence answer is: monthly through the dark season, weekly for six to ten weeks around each release, with an ARC sub-sequence for the readers who explicitly signed up for it. One list. One send calendar. Two rhythms, decided by the tag.
Monthly, the number every guide gives you, is the right answer for the part of your list that is not actively waiting on a book. It is the wrong answer for the part that is, and the part that is waiting on the book is where launch-week reviews and rank on release day come from. The cadence is how you serve both readers from one calendar you were going to run anyway. For the reasoning on why an owned list of readers is worth so much more than the equivalent social following, even at author-friendly reach numbers, our cornerstone piece on subscribers versus followers walks the math.
