CRM and Lifecycle skill 10 of 13

Lifecycle Email Copy and Design SKILL.md

The Lifecycle Email Copy and Design skill makes Claude, Codex or another AI agent write and review lifecycle emails that get one clear action. It covers honest subject lines and preheaders, mobile-first single-column design, accessibility with live text, alt text and contrast, personalisation with fallbacks, dark mode and client rendering, compliance footers, copy patterns by email type and tests judged on clicks and conversions.

lifecycle-email-copy-design/SKILL.md, version 1.0.0, 1,616 words.

A lifecycle email has seconds to earn attention in a crowded inbox, on a phone, often with images blocked or pre-loaded by privacy features. The best ones do one thing clearly: tell the reader why this message matters to them now, and what to do next. The worst look like miniature websites with five offers, three buttons and a paragraph of brand voice nobody reads.

This skill writes and reviews lifecycle emails (onboarding, post-purchase, retention, win-back, transactional with marketing elements and newsletters) for clarity, relevance, accessibility and rendering, and tests what matters.

Operating principles

  1. One job per email. One primary action, stated in the subject line and the button.
  2. Earn the open fairly. Subject lines that mislead drive complaints, which hurt deliverability.
  3. Write for mobile first. Most lifecycle email is read on phones; short paragraphs, large buttons, single column.
  4. Accessible by default. Real text (not text in images), alt text, sufficient contrast, logical reading order.
  5. Personalise with data that helps, not decoration ("Your order ships Tuesday" beats "Hi Sarah").

Anatomy of a strong lifecycle email

ElementGuidance
From nameRecognisable brand or a real person at the brand; consistent
Subject lineWhat's in it for the reader, specific, under about 50 characters as a guide for mobile
PreheaderAdds to the subject rather than repeating it
Opening lineThe point of the email in one sentence
BodyTwo or three short paragraphs or a short list; one idea
Primary buttonVerb plus outcome ("Send your first invoice"), large tap area
Secondary linkOptional, quieter, for people not ready to act
FooterWho you are, why they get this, preferences and unsubscribe, address where required

When to use, and when not to

Use it to write new lifecycle emails, rewrite underperforming flows, review templates, set an email style guide and design tests.

Don't use it for inbox placement problems (email-deliverability) or for deciding which journeys to build (customer-journey-mapping).

Inputs to ask for, in one message

  1. The email's place in the journey: trigger, audience, goal and what comes before and after.
  2. Brand voice, spelling (British or American English) and design system.
  3. Data available for personalisation.
  4. Current version and results (clicks, conversions, unsubscribes, complaints).
  5. Platform and template constraints (Klaviyo, Braze, Customer.io, HubSpot and so on).

Raw SKILL.md file

.md

This is the exact file agents read, including the credit header and licence notice. Save it as lifecycle-email-copy-design/SKILL.md.

---
name: lifecycle-email-copy-design
description: "Write and review lifecycle emails that get one clear action: honest subject lines and preheaders, mobile-first single-column design, accessibility with live text, alt text and contrast, personalisation with fallbacks, dark-mode and client rendering checks, compliance footers, copy patterns for onboarding, post-purchase, replenishment, win-back and re-permission emails, and tests judged on clicks and conversions. Use whenever someone asks to write an email, improve email copy, rewrite a flow, fix email design, write subject lines, create an email style guide, or make emails accessible and mobile-friendly."
license: CC-BY-4.0
metadata:
  author: Afeez Adebayo
  author_url: https://afeezadebayo.com
  author_linkedin: https://www.linkedin.com/in/afeez-adebayo/
  author_x: https://x.com/za_icon
  source: https://afeezadebayo.com/skills-md/marketing/crm-lifecycle/lifecycle-email-copy-design/
  category: marketing
  subcategory: crm-lifecycle
  version: "1.0.0"
  created: "2026-10-10"
  updated: "2026-10-10"
---

# Lifecycle Email Copy and Design

A lifecycle email has seconds to earn attention in a crowded inbox, on a phone, often with images blocked or pre-loaded by privacy features. The best ones do one thing clearly: tell the reader why this message matters to them now, and what to do next. The worst look like miniature websites with five offers, three buttons and a paragraph of brand voice nobody reads.

This skill writes and reviews lifecycle emails (onboarding, post-purchase, retention, win-back, transactional with marketing elements and newsletters) for clarity, relevance, accessibility and rendering, and tests what matters.

## Operating principles
1. **One job per email.** One primary action, stated in the subject line and the button.
2. **Earn the open fairly.** Subject lines that mislead drive complaints, which hurt deliverability.
3. **Write for mobile first.** Most lifecycle email is read on phones; short paragraphs, large buttons, single column.
4. **Accessible by default.** Real text (not text in images), alt text, sufficient contrast, logical reading order.
5. **Personalise with data that helps,** not decoration ("Your order ships Tuesday" beats "Hi Sarah").

## Anatomy of a strong lifecycle email
| Element | Guidance |
|---|---|
| From name | Recognisable brand or a real person at the brand; consistent |
| Subject line | What's in it for the reader, specific, under about 50 characters as a guide for mobile |
| Preheader | Adds to the subject rather than repeating it |
| Opening line | The point of the email in one sentence |
| Body | Two or three short paragraphs or a short list; one idea |
| Primary button | Verb plus outcome ("Send your first invoice"), large tap area |
| Secondary link | Optional, quieter, for people not ready to act |
| Footer | Who you are, why they get this, preferences and unsubscribe, address where required |

## When to use, and when not to
Use it to write new lifecycle emails, rewrite underperforming flows, review templates, set an email style guide and design tests.

Don't use it for inbox placement problems (`email-deliverability`) or for deciding which journeys to build (`customer-journey-mapping`).

## Inputs to ask for, in one message
1. The email's place in the journey: trigger, audience, goal and what comes before and after.
2. Brand voice, spelling (British or American English) and design system.
3. Data available for personalisation.
4. Current version and results (clicks, conversions, unsubscribes, complaints).
5. Platform and template constraints (Klaviyo, Braze, Customer.io, HubSpot and so on).

## Workflow

### Step 1. Define the job
Write one sentence: "This email gets [audience] to [action] because [reason]." If you can't, the email isn't ready.

### Step 2. Write the subject and preheader
Draft five options across angles: benefit, curiosity grounded in content, urgency only when real, personal data, question. Pick two to test.

### Step 3. Write the body
Opening line with the point; supporting detail; one button. Cut anything that doesn't support the action.

### Step 4. Design for mobile and accessibility
Single column, 14 to 16 pixel minimum body text, buttons at least 44 pixels high, live text over images, alt text for meaningful images, colour contrast checked, dark-mode safe logos and colours.

### Step 5. Check rendering
Preview in the main clients your audience uses (Gmail, Apple Mail, Outlook, mobile apps) with a rendering tool or test sends. Check dark mode.

### Step 6. Check compliance
Clear sender identity, working unsubscribe, physical address where the law requires it, accurate claims, consent appropriate to the message type.

### Step 7. Test what matters
Test the offer, the message angle or the call to action, not trivial colour changes. Judge on clicks and conversions, not opens.

## Copy patterns by email type
| Type | Opening approach | Button |
|---|---|---|
| Onboarding step | The outcome of the next step and how long it takes | Do the step |
| Post-purchase care | How to get the best result from what they bought | Read the guide |
| Replenishment | They're likely running low, with an easy reorder | Reorder |
| Win-back | What's new or improved since they left | See what's new |
| Re-permission | Ask plainly if they want to stay | Keep me subscribed |
| Review request | Ask for honest feedback, say how it's used | Write a review |

## Subject line checklist
- Says what's inside or why it matters.
- Uses real urgency only (an actual deadline).
- Avoids all caps, excessive punctuation and misleading "RE:" or "FWD:".
- Works with the preheader as a pair.
- Fits mobile previews.

## Email style guide essentials
| Area | Rule example |
|---|---|
| Voice | Warm, direct, no jargon; write like a helpful colleague |
| Spelling | British English; dates as 14 October 2026 |
| Subject lines | Sentence case; no emoji unless tested; no all caps |
| Buttons | Verb first, two to five words, one primary per email |
| Images | Live text for any message; alt text describes purpose |
| Personalisation | Always set fallbacks; never show raw tokens |
| Legal | Footer template with company details and preferences link |

## Personalisation that helps
| Data | Useful use | Avoid |
|---|---|---|
| Last product bought | Care tips, compatible products, reorder timing | Recommending the same item they just bought |
| Usage data | "You've sent 12 invoices this month" with a next step | Surveillance-sounding detail |
| Location | Local delivery times, store events | Assuming language from location alone |
| Plan or tier | Features they have but haven't used | Upselling on every message |
| Preferences | Topics they chose | Ignoring what they opted out of |

## Testing ideas worth running
- Offer versus no offer in a win-back email (with a holdout).
- Benefit-led versus problem-led opening line.
- One button versus button plus secondary link.
- Personal sender (named person) versus brand sender for onboarding.
- Short versus long format for a newsletter.
Run each test long enough to reach enough conversions, and test one variable at a time.

## Edge cases and judgement calls
| Situation | What to do |
|---|---|
| Brand wants long, story-led emails | Keep the story, but put the point and the button near the top |
| Image-heavy fashion or retail | Use live text for headlines and prices; alt text for every product image |
| Plain-text style from a person | Works well for onboarding and B2B; keep the brand in the from name |
| Several offers to promote | Split into separate sends or pick the most relevant per segment |
| Regulated claims (finance, health) | Get approvals; avoid guarantees; include required disclosures |

## Handoffs to related skills
- Journey context: `customer-journey-mapping`
- Onboarding, retention and win-back sequences: `onboarding-activation`, `retention-churn-prevention`, `win-back-reactivation`
- Inbox placement: `email-deliverability`
- Tests and holdouts: `lifecycle-experimentation`
- SMS and WhatsApp versions: `sms-whatsapp-lifecycle`

## Worked example
A subscription coffee brand's replenishment email had a 1.1% click rate. It opened with a brand story, showed six products and had three buttons. The rewrite used the subject "Running low on [blend name]?", a preheader with the reorder price, an opening line estimating when their bag would run out based on their order date, one button ("Reorder in one tap") and a secondary link to try something new. Click rate more than doubled and reorder revenue per send rose, with unsubscribes unchanged.

## Output format
```
# Email: <name>, <journey position>
Job: <audience> -> <action> because <reason>
Subject options (5) and recommended test pair
Preheader
Body copy (with personalisation tokens and fallbacks)
Button text and secondary link
Design notes (layout, images with alt text, dark mode)
Compliance check
Test plan and success metric
```

## Common mistakes
- Several competing calls to action.
- Important text inside images.
- Personalisation tokens without fallbacks.
- Judging success on opens.
- Clickbait subjects that raise complaints.

## Questions to ask before you write
- What single action should this email produce?
- What data can make it more relevant?
- Which email clients and devices does the audience use?

## Self-check before you answer
- Is there one clear job and one primary button?
- Is it readable and usable on mobile, with images off?
- Are accessibility and compliance checked?
- Is the test plan based on clicks or conversions?

## Further reading
- Litmus email resources: https://www.litmus.com/resources
- Email on Acid accessibility guidance: https://www.emailonacid.com/blog/
- W3C Web Content Accessibility Guidelines: https://www.w3.org/WAI/standards-guidelines/wcag/

---
Created by Afeez Adebayo, Marketing, SEO & Growth Expert
Website: https://afeezadebayo.com
LinkedIn: https://www.linkedin.com/in/afeez-adebayo/
X: https://x.com/za_icon
Source: https://afeezadebayo.com/skills-md/marketing/crm-lifecycle/lifecycle-email-copy-design/

Licence: CC BY 4.0 (https://creativecommons.org/licenses/by/4.0/). You may copy, share and adapt this skill, including for commercial use, as long as you credit Afeez Adebayo and link to the source URL above. Keep this notice in any copy or adapted version.

Workflow

Step 1. Define the job

Write one sentence: "This email gets [audience] to [action] because [reason]." If you can't, the email isn't ready.

Step 2. Write the subject and preheader

Draft five options across angles: benefit, curiosity grounded in content, urgency only when real, personal data, question. Pick two to test.

Step 3. Write the body

Opening line with the point; supporting detail; one button. Cut anything that doesn't support the action.

Step 4. Design for mobile and accessibility

Single column, 14 to 16 pixel minimum body text, buttons at least 44 pixels high, live text over images, alt text for meaningful images, colour contrast checked, dark-mode safe logos and colours.

Step 5. Check rendering

Preview in the main clients your audience uses (Gmail, Apple Mail, Outlook, mobile apps) with a rendering tool or test sends. Check dark mode.

Step 6. Check compliance

Clear sender identity, working unsubscribe, physical address where the law requires it, accurate claims, consent appropriate to the message type.

Step 7. Test what matters

Test the offer, the message angle or the call to action, not trivial colour changes. Judge on clicks and conversions, not opens.

Copy patterns by email type

TypeOpening approachButton
Onboarding stepThe outcome of the next step and how long it takesDo the step
Post-purchase careHow to get the best result from what they boughtRead the guide
ReplenishmentThey're likely running low, with an easy reorderReorder
Win-backWhat's new or improved since they leftSee what's new
Re-permissionAsk plainly if they want to stayKeep me subscribed
Review requestAsk for honest feedback, say how it's usedWrite a review

Subject line checklist

  • Says what's inside or why it matters.
  • Uses real urgency only (an actual deadline).
  • Avoids all caps, excessive punctuation and misleading "RE:" or "FWD:".
  • Works with the preheader as a pair.
  • Fits mobile previews.

Email style guide essentials

AreaRule example
VoiceWarm, direct, no jargon; write like a helpful colleague
SpellingBritish English; dates as 14 October 2026
Subject linesSentence case; no emoji unless tested; no all caps
ButtonsVerb first, two to five words, one primary per email
ImagesLive text for any message; alt text describes purpose
PersonalisationAlways set fallbacks; never show raw tokens
LegalFooter template with company details and preferences link

Personalisation that helps

DataUseful useAvoid
Last product boughtCare tips, compatible products, reorder timingRecommending the same item they just bought
Usage data"You've sent 12 invoices this month" with a next stepSurveillance-sounding detail
LocationLocal delivery times, store eventsAssuming language from location alone
Plan or tierFeatures they have but haven't usedUpselling on every message
PreferencesTopics they choseIgnoring what they opted out of

Testing ideas worth running

  • Offer versus no offer in a win-back email (with a holdout).
  • Benefit-led versus problem-led opening line.
  • One button versus button plus secondary link.
  • Personal sender (named person) versus brand sender for onboarding.
  • Short versus long format for a newsletter.

Run each test long enough to reach enough conversions, and test one variable at a time.

Edge cases and judgement calls

SituationWhat to do
Brand wants long, story-led emailsKeep the story, but put the point and the button near the top
Image-heavy fashion or retailUse live text for headlines and prices; alt text for every product image
Plain-text style from a personWorks well for onboarding and B2B; keep the brand in the from name
Several offers to promoteSplit into separate sends or pick the most relevant per segment
Regulated claims (finance, health)Get approvals; avoid guarantees; include required disclosures
  • Journey context: customer-journey-mapping
  • Onboarding, retention and win-back sequences: onboarding-activation, retention-churn-prevention, win-back-reactivation
  • Inbox placement: email-deliverability
  • Tests and holdouts: lifecycle-experimentation
  • SMS and WhatsApp versions: sms-whatsapp-lifecycle

Worked example

A subscription coffee brand's replenishment email had a 1.1% click rate. It opened with a brand story, showed six products and had three buttons. The rewrite used the subject "Running low on [blend name]?", a preheader with the reorder price, an opening line estimating when their bag would run out based on their order date, one button ("Reorder in one tap") and a secondary link to try something new. Click rate more than doubled and reorder revenue per send rose, with unsubscribes unchanged.

Output format

# Email: <name>, <journey position>
Job: <audience> -> <action> because <reason>
Subject options (5) and recommended test pair
Preheader
Body copy (with personalisation tokens and fallbacks)
Button text and secondary link
Design notes (layout, images with alt text, dark mode)
Compliance check
Test plan and success metric

Common mistakes

  • Several competing calls to action.
  • Important text inside images.
  • Personalisation tokens without fallbacks.
  • Judging success on opens.
  • Clickbait subjects that raise complaints.

Questions to ask before you write

  • What single action should this email produce?
  • What data can make it more relevant?
  • Which email clients and devices does the audience use?

Self-check before you answer

  • Is there one clear job and one primary button?
  • Is it readable and usable on mobile, with images off?
  • Are accessibility and compliance checked?
  • Is the test plan based on clicks or conversions?

Further reading

When to use this skill, and when not to

Use it to write new lifecycle emails, rewrite underperforming flows, review templates, set an email style guide and plan meaningful tests.

A lifecycle email has seconds to earn attention on a phone, often with images blocked or pre-loaded by privacy features. The best ones tell the reader why this message matters now and what to do next; the worst look like miniature websites with five offers and three buttons.

Don’t use it for inbox placement problems (use Email Deliverability) or to decide which journeys to build (use Customer Journey Mapping).

Example prompts

  • “Rewrite our replenishment email so it gets one clear action.”
  • “Write five subject lines and a preheader for our onboarding step two.”
  • “Review our Klaviyo templates for mobile and accessibility.”
  • “Create an email style guide for our team.”
  • “What should we test in our win-back email?”

Example output

The skill returns a fixed structure. A shortened example for an imaginary site:

# Email: replenishment, day 50 after order
Job: coffee subscribers -> reorder because their bag is likely running low

Subject: Running low on Ethiopia Yirgacheffe?
Preheader: Reorder in one tap for \u00a39.50

Opening: Based on your order on 12 August, your bag is probably nearly empty.
Button: Reorder in one tap
Secondary link: Try something new

Design: single column, live text, product image with alt text, dark-mode safe logo
Test: one button vs button + secondary link; metric = reorder rate

Every email starts from one sentence naming the audience, the action and the reason; if that sentence can’t be written, the email isn’t ready.

What the agent needs from you

The skill asks for the email’s place in the journey (trigger, audience, goal, what comes before and after), brand voice, spelling and design system, data available for personalisation, the current version and its results, and platform or template constraints.

How this skill hands off to related skills

Copy and design support every programme. Journey context comes from Customer Journey Mapping, sequences from Onboarding, Retention and Win-Back, inbox placement from Email Deliverability, tests from Lifecycle Experimentation and SMS or WhatsApp versions from SMS and WhatsApp.

How to run Lifecycle Email Copy and Design step by step

  1. Install the skill as lifecycle-email-copy-design/SKILL.md.
  2. Describe the email’s job and its place in the journey.
  3. Share voice, spelling rules and the design system or template.
  4. List personalisation data and the current version’s results.
  5. Review subject options, copy, design notes and the compliance check.
  6. Run the test plan and judge on clicks or conversions.

Situations this skill handles

Different emails need different structures. The skill handles these situations:

SituationWhat the skill does
Several competing offersSplits them or picks the most relevant per segment
Story-led brand voiceKeeps the story but moves the point and button up
Image-heavy retail emailsUses live text for headlines and prices, alt text for products
Plain-text personal emailsKeeps the brand in the from name and one clear ask
Regulated claimsAdds approvals and required disclosures
Broken personalisationAdds fallbacks for every token

What makes this skill different

Most email copy advice is a list of subject line tricks. This skill starts from the email’s job, writes for mobile and accessibility first, uses personalisation only where it changes the message and tests things that matter, judged on clicks and conversions rather than inflated opens.

It also connects copy to deliverability: honest subjects and clear senders reduce complaints, which keep the whole programme in the inbox.

Practical tips from real projects

  • One job, one button.
  • Put the point in the first line.
  • Never put important text inside images.
  • Set fallbacks for every token.

A worked example: a subscription coffee brand’s replenishment email had a 1.1% click rate. It opened with a brand story, showed six products and had three buttons. The rewrite used the subject “Running low on [blend]?”, a preheader with the reorder price, an opening line estimating when the bag would run out from the order date, one button and a secondary link to try something new. Click rate more than doubled and reorder revenue per send rose, with unsubscribes unchanged.

Copy patterns differ by email type. Onboarding emails open with the outcome of the next step and how long it takes. Post-purchase care opens with how to get the best result. Replenishment opens with the likely run-out. Win-back opens with what has changed. Re-permission asks plainly whether people want to stay. Review requests ask for honest feedback and say how it is used.

Design rules keep emails usable: single column, body text of at least 14 to 16 pixels, buttons at least 44 pixels high, live text over images, alt text for meaningful images, checked contrast and dark-mode safe logos. Previewing in the main clients your audience uses catches most rendering surprises.

The skill includes a style guide template (voice, spelling, subject lines, buttons, images, personalisation, legal), a personalisation table showing helpful uses and what to avoid, and testing ideas worth running, such as offer versus no offer and personal versus brand sender.

Compliance checks finish every email: clear sender identity, a working unsubscribe, a physical address where required, accurate claims and consent that matches the message type.

Subject lines get their own checklist: say what is inside or why it matters, use urgency only for real deadlines, avoid all caps and fake “RE:” prefixes, and write them as a pair with the preheader.

Frequently asked questions

As short as the job allows. Most lifecycle emails work best with the point in the first line, two or three short paragraphs and one button.

Around 50 characters is a useful guide for mobile previews, but clarity matters more than length. Pair it with a preheader that adds information.

Only where it helps. Data that changes the message, such as order date, product or usage, beats a first name. Always set fallbacks.

Many readers use screen readers, zoom or dark mode. Live text, alt text, contrast and a logical order make emails usable for everyone and more resilient when images are blocked.

Offers, message angles, calls to action and formats, judged on clicks or conversions. Not opens, and not tiny colour changes.

Both have roles. Plain, personal emails often work well for onboarding and B2B; designed emails suit retail and product launches.

Changelog

  • 1.0.0, 10 October 2026: first release.

Use, adapt and share this skill under CC BY 4.0: credit Afeez Adebayo and link to this page.