5-day challenge email template: the seven emails, written out

Before it starts: You are in. Here is what to have ready

Subject line: You are in. Here is what to have ready. Preheader: Day 1 arrives [tomorrow / Monday] at [time]. Two minutes of setup today.

You are in for [the challenge name]. Here is everything you need to know, and then I will leave you alone until [tomorrow / Monday].

What happens: five emails, one each morning at about [time]. Each one asks you to do one thing that takes [10 to 20] minutes. That is the whole challenge. On Saturday you will have [done the thing five times / written five things / cleared five surfaces], and you will know whether it is worth keeping.

What to have ready today, which takes about two minutes: [the one item, account or space required]. [If a tracker is used: here is a one-page tracker with five boxes on it, if you like ticking things: [link].]

One request. When you have done a day, reply to that email with a word. I read every reply for the five days, and people who tell somebody they did day two are the ones who do day three.

Why this email is shaped this way: it exists so that day one is spent on the action rather than on setup, which is the commonest reason a first day is missed. It also names the arrival time, so the first daily email is expected rather than a surprise, and it sets the terms in advance: what arrives, how long it takes, and what happens after Saturday. The reply request is here rather than on day one because a habit asked for before the challenge starts is a habit, and the same request made mid-week is an interruption.

Day 1: [the action], and why it is this small

Subject line: Day 1: [the action, in four words]. Preheader: Ten minutes. Smaller than you expect, on purpose.

Today: [the action, written as one imperative sentence]. That is it. Ten minutes, and you are done with day one.

It is deliberately small. The point of today is not progress, it is finishing, because the single best predictor of whether somebody completes a five-day challenge is whether they completed day one. So I have made today easy enough that a bad morning cannot stop you.

How to do it: [three or four short steps, in order, in the imperative]. If you get stuck at [the known sticking point], do [the simpler fallback] instead. Both count.

When it is done, reply with a word, or tick box one. Tomorrow: [what day two asks], which takes about the same time.

Why this email is shaped this way: the action is in the first line because that is the only part some readers see, and the explanation follows rather than leads. The smallness is stated out loud, which stops an eager participant inventing a larger version and then failing at it. The fallback exists because a challenge that can only be completed one way loses everybody who hits the sticking point, and it loses them permanently rather than for a day. The last line names tomorrow, which is close to free and measurably reduces the number of people who stop.

Day 2: the same thing, one notch harder

Subject line: Day 2: [the action], with [the one change]. Preheader: Same shape as yesterday. One thing is different.

Today: [the action], but this time [the one change]. Same ten to twenty minutes.

[One or two sentences on what yesterday was for, only if it changes what to do today. Not a recap for its own sake.] The reason for the change is [the mechanism: why this version is the one that produces the result].

How to do it: [the steps, with the changed part marked]. [One example, written out, showing the difference between yesterday’s version and today’s.]

Reply when it is done, or tick box two. Tomorrow is the day most people stop, and I will have something to say about that.

Why this email is shaped this way: the action keeps its shape so the participant does not have to make a new decision, and the variation sits inside the task instead of between tasks. The worked example does the job an explanation cannot, which is to show the difference rather than assert it. The last line pre-empts day three by naming it, so that tomorrow’s wobble arrives as something predicted rather than as a personal failure.

Day 3: this is the day people stop

Subject line: Day 3: this is the day people stop. Preheader: The novelty has gone and the end is not visible yet. Today is small.

Today: [the action, the most immediately satisfying version of it you have]. Fifteen minutes, and it is the best one of the five.

First, the thing nobody says. Day three of any five-day commitment is where it gets dropped, and it is not a motivation problem. The novelty of Monday has worn off and Saturday is not close enough to pull. Everybody who has ever done one of these has felt exactly this on a Wednesday.

So today is designed for it: [why this action is the most rewarding of the five, in one or two sentences]. How to do it: [the steps]. [If it can be done in five minutes badly, say so: doing it badly today beats doing it properly on Friday.]

You are halfway plus one. Reply when it is done, or tick box three. Tomorrow: [what day four asks].

Why this email is shaped this way: naming the pattern is the content. A participant who was about to quit recognises themselves in a sentence about everybody quitting on Wednesday, and recognition converts a private failure into a normal one. The strongest action of the five is spent here rather than saved for the finale, because day five does not need help and day three does. The explicit permission to do it badly exists because the alternative most people choose is not doing it at all.

Day 4: the mistake that undoes the other four days

Subject line: Day 4: [the common mistake]. Preheader: The part that goes wrong, and how to see it coming.

Today: [the action], and while you do it, watch for [the failure mode].

[The failure mode, described concretely: what it looks like, why it is tempting, and what it costs.] This is the thing that undoes the work of the other four days, and it is almost always invisible from the inside, which is why it gets its own day.

How to check: [two or three specific tests the participant can run on their own work today]. If you find it, [the fix, in one sentence]. If you do not, [what that probably means].

Reply when it is done, or tick box four. Tomorrow is the last one, and it is the day you will actually want.

Why this email is shaped this way: day four is where trust is earned, because it is the day a brochure would never include. A challenge that only ever says what to do reads as a promotion, while one that says what goes wrong reads as somebody who has done this before. Putting the failure mode on day four rather than day one also means the participant now has four days of their own work to check it against, which makes it useful rather than theoretical.

Day 5: last one, and what you have now

Subject line: Day 5: last one. Preheader: Finish it, then read what you have actually built this week.

Today: [the action, the version that ties the week together]. Then you are finished.

How to do it: [the steps]. [One sentence on how today uses the four earlier days, if it does.]

When it is done, look back at what you have: [the concrete result of five repetitions, named specifically]. On Monday that did not exist. Whatever else happens, that is yours now.

What to do next week, if you want to keep it: [the smallest sustainable version, honestly stated: twice a week rather than daily, or ten minutes rather than twenty]. Most people cannot sustain a daily version of anything, and the people who keep this are the ones who shrink it rather than the ones who resolve harder.

Reply and tell me how it went. I will send one more email tomorrow and then this goes back to [your normal cadence].

Why this email is shaped this way: day five names the result, which is the only reward a challenge actually has, and it names it concretely rather than congratulating the participant in general terms. The advice for next week is deliberately smaller than the challenge, because a challenge that ends by recommending its own intensity forever sets up a failure the following Wednesday. There is no offer in this email. That is tomorrow, and keeping it out of today is what stops the achievement reading as a sales close.

Day 6: what I do, once, and then back to normal

Subject line: [What you did this week], and one thing from me. Preheader: The offer, once. Skip it if it is not for you.

You did [the action] five times this week. [If you have the number: around [X] people started and [Y] finished, which is [the honest fraction].] That is the whole challenge, and it is yours whether or not you read the rest of this email.

Here is the one thing I sell, once. [The offer in one sentence: what it is, who it is for, what it costs, in the currency.] It exists because of the pattern the week just showed: people can do [the action] with a daily prompt, and almost nobody keeps it up without one. [What the offer supplies: the prompt, the group, the check-in, the accountability.]

[Two or three sentences of specifics, in nouns: how long it runs, how often it meets, how many people, what happens in a week of it, the price.]

It is not for you if [the honest exclusion]. In that case [the free alternative: the tracker, the archive, the weekly email] covers the same ground more slowly, and that is a perfectly good answer.

[The offer, linked, as the single call to action.] [If there is a deadline, state it and give the real reason: the cohort starts on [date], or the price rises when [the real thing] happens.]

From here this goes back to [one email a week, on Tuesdays]. Thank you for the week, and for the replies.

Why this email is shaped this way: the offer arrives the day after the achievement, which is what allows day five to be about the participant. It opens by naming what they did, so the ask follows from the week rather than interrupting it. Naming who it is not for raises conversion rather than lowering it, because it is the sentence that makes the rest believable, and any deadline carries its real reason, since five days of telling the truth about small things is an expensive thing to spend on a fake countdown.