Marketing Email

Marketing Email Creator

Create compelling marketing emails in your authentic brand voice.

Before Writing

1. Identify the email type:

• Newsletter (regular value delivery)
• Launch announcement (course/product promotion)
• Nurture sequence (relationship building)

2. Run the rhetoric selector:

   python shared/rhetoric_selector.py --type email_newsletter
   # or --type email_launch
   # or --type email_nurture

3. Review context:

• VOICE_GUIDE.md
• BUSINESS_CONTEXT.md
• CONTENT_PILLARS.md

Email Anatomy

Subject Line

• 4-7 words ideal
• Create curiosity or promise value
• Rhetorical devices work brilliantly here (antithesis, tricolon)
• Avoid spam triggers (FREE, URGENT, !!!)
• Test with: "Would I open this?"

Subject line formulas:

• Curiosity: "The thing nobody tells you about [X]"
• Benefit: "How to [achieve X] in [timeframe]"
• Story: "I almost [dramatic thing] until..."
• Direct: "[Specific thing] that changed my [result]"
• Antithesis: "[Old way] vs [new way]"

Preview Text

• First 40-90 characters visible in inbox
• Complements (doesn't repeat) subject line
• Often the first sentence of your email

Opening

• Don't waste the first line on "Hi [Name]"
• Start with something interesting
• Hook them immediately - they're deciding whether to keep reading

Body

• Short paragraphs (2-3 sentences max)
• One idea per paragraph
• Use rhetorical devices for flow and emphasis
• Personal stories are your secret weapon
• Specifics > generalities (numbers, examples, real situations)

CTA (Call to Action)

• ONE clear CTA per email
• Button or link, not both
• Action-oriented text ("Join the masterclass" not "Click here")
• Earned, not forced - comes after providing value

Sign-off

• Keep it simple: Your name or "- [Name]"
• P.S. lines work for secondary CTAs or personal notes

Templates

See templates folder:

• Newsletter
• Launch Announcement
• Nurture Sequence

Voice Reminders

From your VOICE_GUIDE.md:

Do

• Write like you're emailing one person
• Share real stories and real numbers
• Be genuinely helpful before asking for anything
• Use "you" more than "I"
• Maintain your spelling conventions

Don't

• Start with "I hope this email finds you well"
• Use "we" when you mean "I"
• Include multiple CTAs competing for attention
• Write walls of text without line breaks
• Sound like a marketing department

Email Types Explained

Newsletter

Purpose: Regular value delivery, staying top of mind Frequency: Weekly or bi-weekly Mix: Technical tip + industry observation + personal note CTA: Soft (reply, share, optional product mention)

Launch Announcement

Purpose: Promote a specific offering Frequency: During launch windows only Structure: Problem > Solution > Proof > Offer > Urgency CTA: Direct (join, enrol, sign up)

Nurture Sequence

Purpose: Build relationship over time with new subscribers Length: 5-7 emails over 2-3 weeks Arc: Welcome > Value > Story > More value > Soft pitch CTA: Graduated (reply > free resource > learn more > offering)

Quality Checklist

Before sending, verify:

• [ ] Subject line creates curiosity or promises clear value
• [ ] Opening line is interesting (not "Hi, I hope...")
• [ ] Paragraphs are short and scannable
• [ ] Voice is authentically yours (check against guide)
• [ ] At least one rhetorical device used naturally
• [ ] ONE clear CTA (or none if pure value email)
• [ ] CTA is earned (value delivered first)
• [ ] No spelling errors
• [ ] Read aloud - does it sound like a person?

Template: Launch Announcement Email

Purpose

Drive action for a specific offering. Convert interested subscribers.

Best rhetoric devices

• Antithesis for before/after contrasts
• Tricolon for listing benefits
• Anaphora for building momentum

Structure

Subject: [Clear announcement with urgency or value]

[HOOK: The transformation or opportunity]

[PROBLEM: What life looks like without this]

[SOLUTION: What this offering provides]

[PROOF: Why you're the right person / results others have gotten]

[DETAILS: What's included - bullet points]

[OFFER: Price, timing, bonuses if any]

[URGENCY: Why act now - deadline, limited spots, price increase]

[CTA: Clear, single call to action]

[Your name]

Subject Line Examples

• "The [Offering Name] opens Monday"
• "Doors close in 48 hours"
• "Your invitation: [Offering Name] [Year]"
• "It's time"
• "The wait is over"

Example Launch Email Structure

Subject: The [Offering Name] opens Monday

In [timeframe], you could be [the transformation/outcome].

Right now, you're probably:

[Pain point 1 - describe in detail]

[Pain point 2 - describe in detail]

Wondering if there's a better way.

There is.

The [Offering Name] is everything I learned in [time period]
of [relevant experience] - compressed into a structured
[format] you can complete alongside your [day job/life].

Here's what's inside:

- [Feature 1]
  [Benefit explanation]

- [Feature 2]
  [Benefit explanation]

- [Feature 3]
  [Benefit explanation]

- [Feature 4]
  [Benefit explanation]

- [Feature 5]
  [Benefit explanation]

The uncomfortable truth: most [people in your audience]
learn [your topic] by struggling alone for years. They
reinvent wheels. They hit walls nobody warned them about.

This is the shortcut I never had.

Previous cohort results:
- [Metric 1]
- [Metric 2]
- [Metric 3]

The [programme/course/product] starts [Date].

Price: [Amount] (or [payment plan])

This cohort has [number] spots. When they're gone, the next
[intake/opportunity] is in [timeframe].

Join here: [LINK]

[Your name]

P.S. Not sure if it's right for you? Reply with your
situation and I'll give you an honest answer.

Email Sequence for Launch

Pre-launch (Day -7)

• Announce launch is coming
• Build anticipation
• No CTA yet

Open (Day 0)

• Full announcement (template above)
• Clear CTA

Social proof (Day 2)

• Student/customer stories / testimonials
• Specific results
• CTA

FAQ / Objections (Day 4)

• Common questions answered
• Overcome hesitations
• CTA

Final reminder (Day 6)

• Last chance messaging
• Urgency (doors closing)
• Strong CTA

Closed (Day 7)

• Thank those who joined
• When next opportunity is
• What to do in meantime

Voice notes

• More direct than newsletters - there's an ask
• Still personal, not corporate
• Specifics build trust (exact numbers, named companies if possible)
• Urgency must be real, not manufactured
• Offer the "reply for honest advice" out

Template: Newsletter Email

Purpose

Regular value delivery. Stay top of mind. Build trust.

Best rhetoric devices

• Tricolon for listing insights
• Anadiplosis for flowing narratives
• Litotes for understated observations

Structure

Subject: [Curiosity hook or clear value promise]

[HOOK: Interesting opening - story, observation, or surprising fact]

[MAIN CONTENT: The meat of the email]
- One clear insight or lesson
- Personal story if relevant
- Specific examples or code

[TAKEAWAY: What to do with this information]

---

[SOFT CTA: Question, invitation to reply, or gentle pointer]

[Your name]

P.S. [Optional secondary CTA or personal note]

Subject Line Examples

• "The 30-second trick that took me years to find"
• "Why your [thing] is lying to you"
• "I deleted 500 lines of code yesterday"
• "The question that changed how I [do X]"
• "What I got wrong about [topic]"

Example Newsletter Structure

Subject: The [topic] that made me look stupid

Last month, I [presented/delivered/showed] a [thing] to a [client/team].

[Time investment]. [Effort details].
Confident [outcome expectation].

Then someone asked: "[Question that exposed the flaw]"

I didn't know.

I'd [made assumption]. [Describe the assumption in detail].
Nice, neat, [convenient characteristic].

Real [systems/situations] don't work that way.

The fix was simple - [brief description of fix].
[Show the solution if relevant - code, process, approach]

But I'd missed it because I was optimising for "[wrong thing]"
instead of "[right thing]."

Now I start every [project/task] with one question:

[The better question to ask]

The [edge cases/exceptions/nuances] are where reality lives.

---

What assumptions have bitten you lately?
Hit reply - I read every response.

[Your name]

P.S. [Your topic] is covered in [your resource/offering].
Details here if you're curious: [link]

Variations

"Lesson learned" newsletter

[What happened]
[What I learned]
[How you can apply this]

"Quick tips" newsletter

Three things I learned this week:

1. [Tip with brief explanation]

2. [Tip with brief explanation]

3. [Tip with brief explanation]

Which one's most useful for you?

"Behind the scenes" newsletter

[What I'm working on]
[Why it matters]
[What's next]
[Invitation to follow along]

Voice notes

• Conversational, not formal
• Share genuine insights, not filler
• Stories from real projects (anonymised if needed)
• Okay to admit uncertainty or mistakes
• End with engagement prompt (question or reply invitation)

Template: Nurture Email Sequence

Purpose

Build relationship with new subscribers over time. Establish trust before asking for anything.

Best rhetoric devices

• Anadiplosis for narrative flow
• Litotes for humble, relatable tone
• Epistrophe for memorable closes

Sequence Overview (7 emails over 3 weeks)

---

Email 1: Welcome (Day 0)

Subject: Your [lead magnet] is ready

Here it is: [LINK]

I'm [Your name]. I [what you do and for whom].

Quick background: [1-2 sentences about your experience
and what led you to do this].

What you can expect from these emails:

- [Promise 1 - what kind of content]
- [Promise 2 - your unique angle]
- [Promise 3 - format/frequency]

I send roughly one email per week. You can unsubscribe
anytime - no hard feelings.

For now, enjoy the [lead magnet]. If you have questions,
hit reply. I read every response.

[Your name]

---

Email 2: Quick Win (Day 2)

Subject: The first thing I [do/build/check] in every [project]

Before I [tackle anything complex], I [do this one thing]:

[Simple, actionable advice]

Every time. No matter how complex the final [outcome] will be.

Here's why:

If this simple case doesn't work, nothing will.

[Example - code, process, or demonstration]

That's it. [Brevity statement].

From here, I add complexity piece by piece. Each addition
either works or breaks something. When it breaks, I know
exactly what caused it.

The [people] who struggle most are the ones who try to
[do everything at once].

Start simple. Verify as you go.

Does this match how you approach [relevant activity]?
Hit reply - I'm curious about your process.

[Your name]

---

Email 3: Story (Day 5)

Subject: The [project/thing] that almost [dramatic consequence]

True story.

Early in my career, I [situation setup].

[Context about the task/goal].

I [did the work]. [Delivered/completed] the [output].
[Expected positive outcome].

The [person/client] [unexpected negative reaction].

[Elaborate on why - the real issue]

They asked me to "[the unreasonable request]."

I understood what they meant: [the subtext].

I didn't. The [work] was right.

What I did wrong was [the actual mistake - usually about
communication, expectation setting, or understanding needs].

The lesson that stuck with me:

[One clear lesson in a memorable sentence]

Now I start every [project/engagement] with: "[The better
question/approach]"

Better to [preventive action] before you [start work].

[Your name]

P.S. [Brief resolution to the story - what happened eventually]

---

Email 4: Deep Value (Day 8)

Subject: The [approach/pattern/method] that changed everything for me

There's a [pattern/technique/approach] I use in almost every [project] now.

It's not in most tutorials. I figured it out after years
of hitting the same problems.

I call it the "[Name]" [pattern/approach/method].

The problem: [Problem description - something your audience
faces regularly]

The solution: [Your approach explained]

[Detailed explanation with example - code, process, or framework]

Now in your [work]:

[Show how to apply it]

After you [complete the work]:

[Show the benefit/result]

This single [pattern/approach] made my [work] [specific improvement].

I wrote a full guide on this with more examples:
[LINK TO FREE RESOURCE]

[Your name]

---

Email 5: Philosophy (Day 12)

Subject: Why I [your approach] (not [common alternative])

People sometimes ask why I focus on [your method/approach].

[Alternatives] have [their advantages]. [Acknowledge what
they offer honestly].

Here's my honest answer:

I've [experienced those alternatives]. [Describe your
experience with them].

And I've watched [people] become [negative consequence].

[Your approach] is different.

[Benefit 1]. [Benefit 2]. [Benefit 3].

You [positive outcomes]. You [empowerment]. You [control].

Is it harder to learn? [Honest assessment]. But you're
learning [transferable skill].

Is [common objection]? [Your reframe].

Does it have [limitation]? [Your honest answer and workaround].

I [do what I do] because I believe [your core philosophy].

That might not be the right choice for everyone.
But it's why I'm here.

[Your name]

---

Email 6: Soft Pitch (Day 16)

Subject: If you want to go further

For the past two weeks, I've been sharing [topic] tips
and stories.

If you've found them useful, there's more where that
came from.

The [Your Offering Name] is my complete [format] for
[target audience] who want to [desired outcome].

It's structured learning. Real projects. Direct support.

Not for everyone - it requires [honest requirement].

But if you're serious about [becoming/achieving something],
it's the fastest path I know.

You can see what's inside here: [LINK]

No pressure. These emails will keep coming either way.

But I wanted you to know it exists.

[Your name]

---

Email 7: Transition (Day 21)

Subject: What happens next

You've been getting these "welcome" emails for three weeks.

Starting now, you'll get my regular newsletter instead.

Same voice. Same mix of [content types].
Just less frequent - usually once a week.

If that's too much, you can switch to monthly updates
or unsubscribe entirely: [LINK]

No hard feelings either way. Your inbox, your rules.

Thanks for reading this far.

[Your name]

P.S. If you ever have a [topic] question, just reply.
I read every response.

---

Voice notes for nurture sequences

• Build trust slowly - no selling until email 6
• More personal, less polished than other content
• Stories > tips in early emails
• Ask for replies, not clicks
• Acknowledge that you're in their inbox by invitation