Send Cadence and List Fatigue: How Much Email Is Too Much

Teams watch unsubscribe rates for fatigue, but unsubscribing is what your most considerate subscribers do. The majority response to too much email is passive: they stop opening, filter you to a folder they never check, or mark you as spam because that button is closer than the unsubscribe link. The list count stays flat while engaged reach shrinks, and because most dashboards report per-send averages rather than list-level engagement, the decay hides in plain sight.

The compounding problem is that mailbox providers watch the same silence. Sustained sends to unengaged recipients degrade sender reputation, which pushes your mail toward spam folders even for subscribers who do want it. Over-sending does not just bore the bored, it taxes delivery for everyone, which is why cadence is a deliverability decision as much as a content one.

Asking how many emails per week is too many has no general answer, because tolerance depends on the value density of what you send and the relationship the recipient believes they have with you. A daily email that reliably delivers something useful can sustain frequencies a monthly mediocrity cannot. The honest question is not how often can we send, but how often can we send something the recipient is glad arrived, and the second number is the only real ceiling.

To find yours empirically, watch cohort engagement against frequency rather than guessing. When rising send volume produces falling engaged share, more spam complaints, or declining clicks per subscriber per month, you have crossed the line regardless of what any benchmark says. Some teams run holdout tests, reducing frequency for a slice of the list and comparing downstream engagement and pipeline, and it is common to find that fewer, better sends lose nothing that mattered.

In most B2B orgs, no single email is the problem; the pileup is. The newsletter team sends weekly, lifecycle automation fires on behavior, product sends release notes, an SDR sequence is running, and an event promotion is in flight, each defensible alone, collectively landing seven emails on the same contact in a week. Nobody decided that; it emerged because each program owns its own calendar and nobody owns the contact's total experience.

The fix is governance plus mechanism. Governance means someone owns the aggregate contact experience and programs are ranked by priority, so when messages collide there is a rule for which yields. Mechanism means frequency capping at the platform level, a per-contact ceiling per week, with priority sends like transactional and active-opportunity messages exempt, and lower-priority campaign mail deferred rather than dropped. A cap crude enough to fit on a sticky note prevents most of the damage.

A single global frequency treats your most devoted reader and your barely-attached subscriber identically, and it is wrong for both. The stronger pattern is engagement-tiered cadence: highly engaged contacts can receive everything they have signed up for, cooling contacts get only your best sends at reduced frequency, and dormant contacts leave the regular rotation entirely for a re-engagement track. This aligns volume with appetite and simultaneously protects deliverability, since your sends concentrate on people who actually engage.

Signals can sharpen this further. A contact showing fresh buying intent, repeat pricing visits, a demo request, active evaluation behavior, warrants more contact right now, while the same contact six months post-evaluation warrants much less. Cadence, done well, is not a fixed schedule but an output: a function of each contact's current engagement and intent, bounded by a global cap that keeps the whole system honest. Preference centers help too; offering a less-email option captures people who would otherwise silently disengage, and a downshift is always a better outcome than a spam complaint.