Why I Built 5dayemail

The textbook advice for building an audience is to start a newsletter. It is good advice for the person who wants to write every week for years, and it quietly asks a great deal of everyone else: an open-ended commitment from the writer, and an open-ended place in the inbox from the reader. I built 5dayemail for the other shape — the one where you know a subject well enough to teach it in a week, and that is the whole ask. Five to ten emails, one a day, in the order you wrote them, and then it ends.

The problem I kept running into

An email course is the simplest thing an email tool can send. It has no audience logic and no decisions in it: a fixed list of lessons, delivered a day apart, to each person from the day they join. And yet setting one up in a general email tool means working backwards through software built for everything else — sequences, triggers, segments, a sending domain to verify, an automation canvas with one arrow on it. All of that sits between you and the first sentence of day one.

The effect is predictable. The setup outlasts the motivation, and the course that was going to take a weekend becomes a half-configured automation nobody opens again. The writing was never the hard part; the plumbing was.

The insight

A course that goes out one day at a time doesn't need any of the machinery. If the order is fixed and the gap is always one day, there is nothing to configure — so the product can be a list of days and an editor. That is what 5dayemail is: you write a subject, a preview line and a body for each day, and you move days up and down. Publishing gives you a hosted sign-up page that lays the whole course out, day by day, before anyone hands over an address.

"

A newsletter asks a stranger for a place in their inbox with no end date. A course asks for five mornings and tells them what arrives on each. The second is a much smaller decision — which is exactly why people make it.

The finiteness does real work. A reader who knows the course ends on Friday is deciding about a week, not about a relationship. And someone who reaches day five has actually finished something of yours — which is a different kind of list from one made of people who never unsubscribed.

The design choices that matter

The length is capped at ten, on every plan. The obvious commercial move is to sell longer courses on a bigger tier. I didn't, because the cap is the format: ten mornings is already a lot to ask of a stranger, and a product that sold a thirty-email "course" would be a drip-campaign tool wearing this one's name. It's the same discipline as choosing who a product is for — the narrowness is the feature.

Each reader runs on their own clock. Day one follows the confirmation; every later day arrives on the next calendar day, at the hour the creator picked, in the reader's own timezone. Nobody gets lesson three at 3 a.m. because the author lives nine hours away.

Confirmed opt-in is not a setting. Every creator sends from the same domain, so one careless list damages everyone else's delivery. An address that hasn't clicked its confirmation link receives exactly one message, ever — and there is no switch for that, anywhere.

No open tracking. Apple Mail fetches a tracking pixel whether or not anyone read anything, so an open rate is a number that looks like information without being any. The stats page shows what can actually be known: who signed up, who confirmed, what was delivered, what bounced, who reached the end.

You see exactly what the reader receives. The editor sits beside a live preview of the real email — as HTML, as plain text and as a line in an inbox list. Writing the expected output before the screen is how I build everything; here the expected output is the product's main screen.

The business shape

5dayemail runs on the same Nuxt and Supabase stack as everything else I build, with one deliberate difference: the process that sends email is separate from the one that serves pages, so a deploy can never interrupt a send. The pricing is two lines — Free for three courses, or $49 a month — with nothing charged per subscriber or per email. That Free plan is a departure from my usual rule against free plans, and it's a deliberate one: every lesson a creator sends carries the product's name in its footer, so here a free user is part of how the next creator finds it.

I built 5dayemail because the simplest thing in email — a short course, one lesson a day — deserved a tool that did only that. If you know something worth a week of someone's mornings, that's what it's for.

See also why confirmed opt-in is not a setting in 5dayemail and my product operating system.