The emails of a subscription business we built and run
Crenas Coliseum, a subscription to UFC fight analyses with a 7-day free trial, needs an email for every moment: the first days, a declined card, a cancellation. Here is what we built, how each part works and what we learned.
The starting point.
New customers decide in a week whether the subscription is worth paying for.
Weekly, monthly and 3-month plans renew on a card, and some cards get declined.
Some customers cancel during the trial or later, and some of them would come back.
Customers in Europe, so quiet hours, easy unsubscribe and the right to be forgotten matter.
Six emails during the trial, one a day, the last one the day before it ends.
Each email shows one thing worth trying, so the customer reaches the end of the week knowing what they would pay for. If they cancel, the rest of the series stops.
Move through the trial and watch the emails go out.
Example subjects. The timing is the one we use.
Day 1: the first email goes out at sign-up, or the next morning if it’s night.
After a declined card, up to seven emails in two weeks, checked before each one.
The emails go out on days 0, 1, 2, 4, 7, 10 and 14. Before each send, the system asks the payment system if the invoice is paid, and stops the moment it is.
Choose why the card failed, then when the customer pays.
Example subjects. The timing is the one we use.
No emails at night, one-click unsubscribe and never the same email twice.
Every email first reserves its place in a list, then goes out. A second attempt finds the place taken and sends nothing, and if a send fails, the place is freed for a retry.
Try to break the rules.
Each button is a real situation the system handles.
Alex is on day 2 of the welcome series.
Knowing who reads, and forgetting people who ask.
Opens, bounces and complaints are recorded for each email. After a point, people who never open stop receiving the series, and anyone can ask to be forgotten without breaking the business's numbers.
Apply the rule, then forget a customer.
Example customers. Blue means opened.
Four customers, four emails each.
The project in numbers.
Source: the business's email service, September–October 2026.
What we learned.
Whether an invoice is paid is asked at the moment of each email, not when the series started.
That one step is what keeps a customer from getting the same email twice, even when two jobs run at once.
Our own records showed which declines are worth reminding and which deserve one clear email.
Quiet hours, one-click unsubscribe and stopping for people who never open keep the sender's name in good standing.
A test mode that lists who would get what makes every change safe to try before it reaches a customer.