Four Gives, One Ask: The 14-Day Nurture Sequence, Built

The nurture sequence we rebuilt recently for a faith-based organization sends five emails over 14 days, at day 0, 2, 5, 9, and 14. Four of them hand the new subscriber something. The fifth, and only the fifth, asks for a gift. That is the whole design, and the rest of this article is how it is built: what each email does, what a secular organization sends in place of a daily devotional, the subject lines and calls to action for a worked example, and a packet with all of it written out.

Part 1 made the case for giving before asking and laid out the general shape of a series. This is the specific one. If you already have a welcome email and want the next four, start at the swap table and work down.

What does the faith-based sequence get right?

It holds the ask. The original held its gift request until the last message, the one thing it got right, and the rebuild kept that and changed everything around it. Day 0 delivers what the signup promised. Day 2 asks for a reply, not money. Day 5 lets the reader choose less. Day 9 hands over a free tool. Only day 14 asks, and it says out loud that it is the first time. Two weeks of giving is long enough that the ask reads as fair rather than sudden, and short enough that the reader still remembers signing up.

The part a secular organization envies is not in the five emails at all. The organization publishes a daily devotional, so every morning of those 14 days already carries something the reader chose to receive. The sequence never has to manufacture a reason to open. It rides on a habit that is forming on its own, and the five emails are the moments that turn a reader into a relationship. Without a daily stream, a welcome sequence is five emails arriving into silence, and the gaps between them are where people forget you. Part 1 covered why those first days matter, and M+R's finding that welcome-series clicks run at 1.6% against 0.59% for a standard appeal is the number behind it.

The craft rules are shared by all five emails and by the daily stream. They are unglamorous, and they are most of the difference between a sequence that works on a phone with images off and one that only works in the design tool.

• One primary action per email. A second link is allowed only in the footer.
• Buttons are live text on a colored table cell. An image button vanishes when images are off, and the one thing the email exists to do vanishes with it.
• The preference link sits ahead of the unsubscribe link in every footer, so the person who wants less finds less before they find gone.
• No first-name merge field. An empty token reads worse than no name at all, and most signup forms do not collect one reliably.
• Subject lines run 20 to 34 characters, which survive a phone's subject column without truncation.
• An effort expectation sits beside each call to action: about a minute, one tap, a two-minute read.
• Body text at 16px and full contrast, on a single column.
• Descriptive alt text on every image, written as the sentence a reader would need if the image never loads.

How does a secular organization swap in each piece?

The worked example is Larkfield Food Rescue, an organization that collects surplus food from grocers and restaurants and runs a network of neighborhood pantries. Larkfield is invented. Every name and number in the example is synthetic. The swaps below are the ones the packet is built on, and each one replaces the faith-based piece with something that does the same job for a person who signed up because of food, not faith.

Three of NextAfter's published tests shaped the form the swaps take. In one, a welcome series built around the resource people had signed up for beat a series built on stories, on both donor conversion and unsubscribes, which is why the Larkfield stream pairs every note with the guide rather than replacing it. In another, a first-person voice with a single text link beat a designed appeal. In a third, a plain-text version converted more donors than the designed one. The story notes are plain for a reason.

Who writes the seven-day story stream, and how often should it arrive?

One person writes and signs it, in the first person, and the reader learns their name on day 0. For Larkfield that is Maya Okafor, a route coordinator who drives the morning van. Seven notes of 90 to 120 words, one each morning, each true, each ending on one link, each with a subject in the form "Day 3: Why Hillcrest sets it aside". The subjects change and the writer does not: her own 6 a.m. pickup at Hillcrest Market on day 0, a volunteer's first shift, a family's Thursday at the pantry, the grocer who sets food aside instead of tossing it, the month in one number, an ice-storm route, and on day 6 the close that says what week two looks like. They are not appeals and they are not newsletters. They are what Maya would tell a friend who asked what the job is actually like. Day 0's story goes inside the first email, so the very first thing a new subscriber reads is the thing they signed up for.

The story series runs underneath the five sequence emails rather than replacing them. The day 2 and day 5 emails are their own sends, and each opens by acknowledging the stories so far instead of pretending to be one: day 2 begins "Two stories in, we want to ask you one question, and it is not about money." After day 6 the stories drop to one a week, day 9 and day 14 arrive on their own, and the next ask waits at least three weeks after the first.

Daily sends have a consent problem that the devotional never had. People who subscribed to a devotional asked for something daily. People who signed up for a food-rescue guide did not, and Yahoo's sender guidance warns specifically against starting daily mail to people who subscribed to something less frequent. So the cadence has to be stated twice and chosen once. The signup form says it plainly, and the first email repeats it in its opening paragraph, with the weekly option in the same breath: "You will get one story from the field every morning for seven days, then one a week after that. If daily is too much, choose weekly here and you will still get every story, on Sundays." Put the same choice on the form, and let the preference link in every footer keep offering it. People forgive mail they expected.

The stories need a second kind of consent, from the people in them. The packet's planner carries the line to read aloud to anyone quoted or photographed, asking permission to share a first name, a town, their words as written, and the photo, with the right to say no to any part and to change their mind later. Consent is never a condition of receiving food, volunteering, or partnering, and a guest who says no gets the same service and a story told in a different voice. Collect all seven in one afternoon on a single route, one photo and one logged number per story, and send each draft to the person quoted before it enters the queue.

What does each of the five emails do?

Every email has one job and one action. The table gives the Larkfield subject line, the job, and the call to action for each, and the paragraphs after it cover the one decision in each email that is easy to get wrong.

Day 0: deliver, and put the value in the first sentence

The first email carries the first story note in full. It does not link to it, tease it, or wrap it in a welcome paragraph. The first sentence of the body states what the reader is getting, because Apple Mail's inbox summaries are generated from the live text of the message and drop the preheader, so the sentence that used to be hidden preview copy is now the sentence a large share of readers see first. The cadence line and the weekly option come next, then Maya's note from the 6 a.m. pickup, then the one link, with the effort beside it.

Day 2: ask for a reply, and mean it

The exchange has to cost the organization something, or it is a survey. Day 2 asks one question, why did you sign up, and promises that Maya reads every answer herself and replies to each one within a few days. The email says the reply takes about a minute. Two pieces of research say the question belongs here and not later. Pittarello and Kogut found that asking people for an opinion before an appeal raised what they later gave. And NextAfter found that a soft yes-or-no question placed on the gift form itself lowered conversion, which is why the micro-ask lives upstream on day 2 and nowhere near the day-14 form.

Day 5: offer less, and only if the answer changes something

Preferences are framed as a way to receive less, never more. The choices are visible in the email itself, not behind a link to a preference center: pantry openings and volunteer shifts, where the food comes from, the numbers behind the work, food-waste policy explained plainly, stories from the field only. The click only confirms what the reader already decided. Send this email only if the answers actually change what people get. An organization with one weekly email and no segments should skip day 5 rather than collect a preference it cannot honor.

Day 9: give a tool, and let the inbox go quiet

The faith-based original handed over its app on day 9, and the habit moved from the inbox to the phone. Larkfield's version is the Larkfield Leftovers Guide, one printed page with 12 ways to keep a week's groceries out of the bin: what to do with bananas going brown, how long cooked rice keeps, the freezer trick for half a loaf, what a "best by" date means. The email ties it to the most common answer to day 2's question, which is some version of hating to watch good food get thrown out, and it asks for no account and no signup. The job is the same in both: give the reader a reason to keep the organization around that does not depend on opening the next email.