Monthly email revenue, in four months.
Active list rebuilt from 21,922 to a 49,005 peak. EPS tripled.
Shared for evaluation purposes only.
Brand name withheld under engagement agreement.
A metabolic health publisher with a sizeable subscriber base, a portfolio of supplement products, and an active customer base — generating revenue per subscriber below $0.55. The brief was full operator engagement on email: architecture, calendar, lifecycle, segmentation, monetization. All of it.
Subscribers entered through a single opt-in path and received the same broadcasts regardless of what condition brought them in. Lifecycle flows were absent or built once and abandoned. New product launches landed in calendars that didn't accommodate them. Reorder behavior was unmanaged. Cart abandonment had no recovery system.
A list of that size, with that many products and that many distinct buyer profiles, should have been producing revenue at multiples of where it was. The infrastructure to produce it did not exist.
Each system was built around contribution margin and AOV — not opens or clicks.
The mechanism behind each — the segmentation logic, the offer sequencing, the resend rules, the calendar discipline — is the part that took fifteen years to learn how to build. The numbers below show what it produced.
| Month | Active List | Subs Added | List Revenue | EPS | Revenue Change |
|---|---|---|---|---|---|
| January | 21,922 | 34,085 | $11,086.78 | $0.51 | — |
| February | 27,413 | 41,535 | $26,677.23 | $0.97 | +58.4% |
| March | 29,714 | 54,341 | $30,772.56 | $1.04 | +13.3% |
| April | 34,302 | 54,783 | $49,739.83 | $1.45 | +38.1% |
| May | 49,005 | 75,567 | $48,770.75 | $1.25 | −2.0% |
Two lists of identical size can produce ten-fold differences in revenue depending on what infrastructure sits behind them.
EPS — earnings per active subscriber — is the metric that isolates the work of the operator from the work of the acquisition team. A subscriber list growing in EPS is a list where the email system is doing more with each person on it. That is the effect of architecture, not list-building.
In this engagement, EPS nearly tripled while the list grew. Both numbers matter. But EPS is the one that proves the system is working.
"EPS is the operator's metric. List size is the acquisition team's metric. When EPS rises while the list grows, the email system is the active variable."
A subscriber list is a piece of infrastructure. What gets built behind it determines what it earns.
A growing list does not, by itself, produce growing revenue. The two numbers move together only when the architecture compounds — when each subscriber enters a system designed to monetize their behavior, not just receive a broadcast schedule.
Earnings per subscriber is the operator's metric. List size is the acquisition team's metric. When EPS rises while the list grows, the email system is the active variable. When EPS falls or stays flat while the list grows, the operator is being credited for someone else's work.
For an engagement of this scope, the architecture produced a 184% EPS lift — which is the case for treating the email backend as infrastructure rather than as a content channel decorated to look like one.
This case study covers the multi-year engagement. The architecture was built in the first months and matured into ongoing optimization.
Five months is a short window. The system was built to compound beyond it.
If the backend is built correctly,
it pays for itself — usually inside ninety days.