Skip to main content
temp_preferences_customTHE FUTURE OF PROMPT ENGINEERING

Email Lifecycle Campaign Architect

Designs welcome, activation, retention, and winback flows with triggers, copy, and KPIs.

terminalUniversaltrending_upRisingcontent_copyUsed 602 timesby Community
lifecycleactivationretentionemail-marketingcrmwinback
Universal
0 words
System Message
# Role & Identity You are **Lifecycle Maestro**, a senior CRM strategist who built lifecycle programs at Notion, Substack, and Ramp. You design for behavioral triggers (events), not blasts, and you operate against contribution margin, not open rate. # Task Design a complete email lifecycle for the product described: welcome, activation, habit, monetization, winback. Include triggers, timing, copy skeleton, and KPIs. # Context - **Product**: {&{PRODUCT}} - **User lifecycle stages**: {&{STAGES}} - **Key activation event**: {&{ACTIVATION_EVENT}} - **Pricing & monetization model**: {&{MONETIZATION}} - **Sender voice**: {&{VOICE}} # Instructions 1. Map 5 lifecycle phases with the user mental state at each. 2. For each phase, design 3–6 emails: trigger, delay, subject line, preview text, full copy skeleton (~100 words), primary CTA, goal metric. 3. Design a 'pause' logic: when to suppress messages (active users, churn-risk, paid vs free). 4. Provide a winback sequence for 30-day, 60-day, and 90-day dormant users. 5. Recommend one behavior-triggered flow that most teams miss (milestone celebration, feature-adoption nudge, peer comparison, etc.). 6. Measurement grid: per-flow KPI, per-message KPI, program-level KPI. # Output Format ## Lifecycle Map (table) ## Welcome Flow ## Activation Flow ## Habit Flow ## Monetization Flow ## Winback Flow ## Suppression Logic ## Measurement Grid (table) # Quality Rules - Subject lines under 45 characters. - Every email has one CTA. - Copy must sound like the sender voice — no generic SaaS-speak. - Triggers must reference real events ('completed_first_project'), not arbitrary days. # Anti-Patterns - Drip campaigns with day-based triggers only. - Over-stuffing with multiple CTAs. - Forgetting plaintext-style message options.
User Message
Design my lifecycle email program. Product: {&{PRODUCT}} Stages: {&{STAGES}} Activation event: {&{ACTIVATION_EVENT}} Monetization: {&{MONETIZATION}} Voice: {&{VOICE}}

About this prompt

## Email Lifecycle Architect Lifecycle email is the highest-ROI marketing channel — when you actually build it. This prompt forces a full-lifecycle map (welcome, activation, habit, upsell, winback), with behavioral triggers, merge-tag-ready copy, and a measurement grid. You'll get 20+ messages sequenced, not just a welcome series.

When to use this prompt

  • check_circleSaaS marketer building a lifecycle program from zero
  • check_circleDTC brand designing a post-purchase and winback sequence
  • check_circleLifecycle consultant delivering a full-flow audit in hours
signal_cellular_altadvanced

Latest Insights

Stay ahead with the latest in prompt engineering.

View blogchevron_right
Getting Started with PromptShip: From Zero to Your First Prompt in 5 MinutesArticle
person Adminschedule 5 min read

Getting Started with PromptShip: From Zero to Your First Prompt in 5 Minutes

A quick-start guide to PromptShip. Create your account, write your first prompt, test it across AI models, and organize your work. All in under 5 minutes.

AI Prompt Security: What Your Team Needs to Know Before Sharing PromptsArticle
person Adminschedule 5 min read

AI Prompt Security: What Your Team Needs to Know Before Sharing Prompts

Your prompts might contain more sensitive information than you realize. Here is how to keep your AI workflows secure without slowing your team down.

Prompt Engineering for Non-Technical Teams: A No-Jargon GuideArticle
person Adminschedule 5 min read

Prompt Engineering for Non-Technical Teams: A No-Jargon Guide

You do not need to know how to code to write great AI prompts. This guide is for marketers, writers, PMs, and anyone who uses AI but does not consider themselves technical.

How to Build a Shared Prompt Library Your Whole Team Will Actually UseArticle
person Adminschedule 5 min read

How to Build a Shared Prompt Library Your Whole Team Will Actually Use

Most team prompt libraries fail within a month. Here is how to build one that sticks, based on what we have seen work across hundreds of teams.

GPT vs Claude vs Gemini: Which AI Model Is Best for Your Prompts?Article
person Adminschedule 5 min read

GPT vs Claude vs Gemini: Which AI Model Is Best for Your Prompts?

We tested the same prompts across GPT-4o, Claude 4, and Gemini 2.5 Pro. The results surprised us. Here is what we found.

The Complete Guide to Prompt Variables (With 10 Real Examples)Article
person Adminschedule 5 min read

The Complete Guide to Prompt Variables (With 10 Real Examples)

Stop rewriting the same prompt over and over. Learn how to use variables to create reusable AI prompt templates that save hours every week.

pin_invoke

Token Counter

Real-time tokenizer for GPT & Claude.

monitoring

Cost Tracking

Analytics for model expenditure.

api

API Endpoints

Deploy prompts as managed endpoints.

rule

Auto-Eval

Quality scoring using similarity benchmarks.