Five-email welcome sequence plan

Use when someone has just subscribed or signed up and you have nothing sending to them yet.

welcome-sequence-five-email.md

Download .md

You are a lifecycle email strategist. Design a five-email welcome sequence.

Business: {{BUSINESS_DESCRIPTION}}
What the person just did to join the list: {{SIGNUP_TRIGGER}}
The one action I want them to take: {{PRIMARY_GOAL_ACTION}}
Main objection or hesitation they have: {{MAIN_OBJECTION}}
Sending window available: {{SEQUENCE_LENGTH_DAYS}} days

For each of the five emails give me a table row with these columns:
Number | Send delay | Job of this email | Subject line | Preheader | Body (120-180 words) | Single call to action | What it earns the next email

Rules:
- Each email must do one job only. If two emails could be described the same way, rewrite one.
- Email 1 must deliver whatever was promised at signup before anything else.
- Only one call to action per email, repeated at most twice.
- No em dashes. Do not open with scene setting about the industry. Do not use "it is not just X, it is Y". Do not end with a paragraph that restates the opening.
- Do not invent statistics, customer counts or awards. If a claim would need a number I have not given you, write {{NEEDS_FACT}} in its place.

After the table, list in three bullets what should change if the person does not open emails 1 and 2.

Fill in before running

Replace each placeholder with your own detail. The more specific you are, the less the model invents.

{{BUSINESS_DESCRIPTION}}
{{SIGNUP_TRIGGER}}
{{PRIMARY_GOAL_ACTION}}
{{MAIN_OBJECTION}}
{{SEQUENCE_LENGTH_DAYS}}
{{NEEDS_FACT}}

Getting a better result

Tell it the signup trigger precisely. A lead magnet download and a free trial start need completely different first emails.
Give it the real objection from sales calls or support tickets, otherwise it writes to a generic hesitation.
Ask for the no-open branch. Most welcome flows leak the majority of the list in the first two sends.