Learn email marketing by designing a welcome sequence that a subscriber actually asked to receive. Start with a clear signup promise, record permission, write useful messages, and test exits before considering performance. This roadmap uses a fictional weekend gardening newsletter. The project stays in draft or test mode until a real sender has confirmed its permissions, identity, technical setup, and applicable requirements. You can demonstrate the full planning skill without sending unsolicited messages.

Define the signup promise and audience

The fictional newsletter promises three beginner gardening lessons over one week, followed by a weekly practical tip if the subscriber chooses that ongoing subscription. State what will arrive, who sends it, and how to stop. Do not hide marketing permission inside an unrelated download or assume a public email address grants permission to send a sequence.

Mailchimp’s permission guidance explains its requirement to obtain permission before sending marketing through its service Source 1. That is a provider rule and useful practice guidance; actual legal obligations depend on the sender and audience jurisdiction. Keep the first exercise simple by using only your own test addresses and invented subscriber records.

Map the sequence before writing

Draft three messages. The first welcomes the subscriber and delivers a short checklist for choosing a container. The second explains a basic watering observation. The third asks the reader to choose the next topic and clearly describes any ongoing subscription option. Each message has one primary purpose and an action that follows naturally from it.

Use a planning table with trigger, delay, subject, promise, link, and exit condition. Define the trigger as a confirmed subscription event under your chosen setup. If the person unsubscribes after message one, they must not receive messages two and three. If the same event arrives twice, the sequence should not restart and send duplicate welcomes.

Write subject lines that describe the content without false urgency. “Your container-garden checklist” is a clear promise; “Final warning” is not justified by a voluntary lesson. The sender name and reply route should be recognisable. Do not invent customer testimonials, results, or scarcity to make the practice messages seem persuasive.

Build a testable message and exit path

For the first message, include a welcome, the promised checklist link, what comes next, and an unsubscribe option. Keep a plain-text version readable. Test links using a staging destination rather than collecting real subscriber details. Mailchimp’s unsubscribe guidance explains how unsubscribed contacts are handled within its platform Source 2; check the equivalent behaviour in whichever tool you use.

Create four fictional test records: new subscriber, duplicate signup, unsubscribed contact, and address that produces a delivery failure in the platform’s supported testing method. Expected outcomes are one welcome for the new subscriber, no duplicate restart, no later marketing for the unsubscribed contact, and a visible failure record rather than endless retries.

Review rendering on a narrow screen and with images disabled. The checklist link must remain identifiable without a large banner. Check that every lesson matches the signup promise. A technically delivered email can still be a poor experience if the content changes from beginner lessons to unrelated promotions without a clear basis.

Document readiness and measurement

Google’s sender guidelines describe authentication and other requirements for delivery to personal Gmail accounts Source 3. Before any real launch, use the provider’s current setup guidance and verify the actual sending domain. Do not interpret a successful test to yourself as proof of delivery to every mailbox or permission to send to a purchased list.

For a fictional performance exercise, assume 100 delivered messages and 12 unique checklist clickers. The defined clicker share is 12%. If three people unsubscribe, record that separately; do not treat leaving as a technical failure to bypass. Opens can be affected by email-client behaviour, so choose metrics that fit the learning question and explain their limitations.

Your portfolio should contain the signup wording, sequence map, three finished drafts, test cases, and a launch-readiness note. Clearly label simulated metrics. The next learning step is an authorised small send with a real consent process and monitored results, followed by one carefully justified improvement.

Practice sequence
  1. PromiseExplain what the subscriber will receive.
  2. PermissionRecord the appropriate subscription event.
  3. WelcomeDeliver the promised value promptly.
  4. Respect exitsStop or suppress messages when required.
Practice decisions and evidence
Checkpoint What to produce How to review it
Permission Clear lesson and subscription promise No bundled or assumed consent
Sequence Three messages with distinct purposes Content matches the signup wording
Exit Unsubscribe stops later marketing Test after message one
Measurement 12 unique clickers of 100 delivered Report as simulated 12% clicker share
Evidence before advancement
New signup
One welcome sequence begins.
Duplicate signup
Do not create a second active sequence.
Unsubscribed
Suppress remaining marketing messages.

Common questions

Can I practise without an email platform?

Yes. Write the signup wording, sequence table, message drafts, and test cases in ordinary documents first. You can review timing and content without sending anything. A platform becomes useful when you need to test triggers, suppression, rendering, and logs. Keep the practice audience limited to authorised test addresses.

Is a publicly listed email address permission?

No, public availability does not by itself establish that someone asked for your marketing sequence. Use an appropriate permission process and check the rules that apply to the actual sender and recipients. In this learning exercise, avoid real prospect lists and focus on drafting and testing a consent-based flow.

Should I use single or double opt-in?

That choice depends on the platform, audience, risk, and applicable requirements. Learn what each process records and test its effect on the sequence trigger. Do not start lessons before the subscription state you require is reached. Document the decision rather than assuming one setup is universally mandatory or universally sufficient.

How long should the welcome sequence be?

Long enough to deliver the stated promise without adding messages merely to increase contact frequency. Three lessons suit this fictional brief because each has a distinct beginner task. A different promise may need fewer or more. Evaluate usefulness and subscriber expectations rather than copying a fixed number from an unrelated campaign.

What happens if someone unsubscribes midway?

The remaining marketing messages should be suppressed according to the platform and applicable requirements. Test that behaviour explicitly after the first lesson. Do not re-add the contact through another import or automation to continue the sequence. A working exit is part of the product experience, not an obstacle to engagement.

Are open rates a reliable success measure?

They can provide context, but email-client privacy and image-loading behaviour affect what an open means. Choose a metric tied to the goal, such as a defined checklist action, and state its denominator. No single metric explains subscriber satisfaction. Review replies, exits, delivery issues, and content usefulness alongside any performance figure.

Can I use invented results in my portfolio?

You can use simulated numbers to demonstrate calculations, provided they are clearly labelled as fictional. Do not describe them as a campaign you sent or as client outcomes. Include the assumptions and expected arithmetic. A transparent simulation can show planning skill without misleading a reviewer about real experience.

What must be checked before a real send?

Confirm the actual audience permission, sender identity, domain setup, links, suppression rules, and relevant legal and provider requirements. Review the current documentation because technical rules can change. Send only within the authorised scope and monitor failures. This draft exercise is preparation, not automatic authorisation to contact real people.

Continue your learning

Copywriting Roadmap: Turn Customer Research into Clear Marketing Copy. No-Code Automation Roadmap: Design and Test a Simple Business Workflow.

Sources and further reading