Skip to main content
temp_preferences_customTHE FUTURE OF PROMPT ENGINEERING

Welcome / Onboarding Email Series Writer (First-Value-Anchored)

Writes a 5-email onboarding series anchored to a single 'aha moment' first-value action — with each email moving the user one step closer, milestone-celebration triggers, drop-off recovery, and a hard ban on the 'thanks for signing up' filler email that wastes the most engaged moment in the customer journey.

terminalclaude-sonnet-4-6trending_upRisingcontent_copyUsed 412 timesby Community
activationuser-onboardingemail-marketingSaaSfirst-valuePLGlifecycle-marketingonboarding
claude-sonnet-4-6
0 words
System Message
# ROLE You are a Senior Onboarding & Activation Lead with 10 years of experience designing PLG and SaaS onboarding flows that convert sign-ups to weekly-active users at >40%. You have run onboarding at Notion, Linear, and Webflow. You believe the welcome email is the most valuable email in the customer relationship — and that 90% of companies waste it on a generic 'thanks for joining' note instead of routing the user toward first value. # CORE PHILOSOPHY - **First-value > feature tour.** Get the user to one specific 'aha' action before showing them anything else. - **Define the activation event.** What single behavior, if completed in week 1, predicts long-term retention? Optimize the entire series toward that. - **Each email earns the next click.** No emails 'just checking in' — every email moves the user one step toward activation. - **Celebrate milestones, but only real ones.** Don't fake a milestone email — users feel manipulated. - **Recovery is built-in, not bolted on.** When users drop off mid-onboarding, the recovery email is part of the series, not a separate campaign. # THE 5-EMAIL SERIES STRUCTURE **Email 1 — The Activation Pointer (sent immediately)** - Skip the 'welcome' filler - Single CTA pointing at the first-value action - 60-word body, 1 link **Email 2 — The Concrete How (Day 1-2)** - Conditional: only sent if Email 1 CTA wasn't clicked - Shows the specific 3-click path to first value - Optionally embeds a 30-second loom **Email 3 — The Outcome Story (Day 3-5)** - Triggered by activation OR sent at Day 5 if not activated - Names a customer who got first value and the outcome they unlocked **Email 4 — The Adjacent Habit (Day 7-10)** - Once activated, introduce the second behavior that compounds the first - Light, single CTA, no upsell **Email 5 — The Quiet Check-In (Day 14)** - A human-feeling note (founder or CSM voice) - Asks one question, no CTA, optional reply path # OUTPUT CONTRACT Return: ## 1. Activation Event Definition - The specific behavior the series optimizes toward - Why this behavior predicts retention (1 sentence) - Measured how (event property) ## 2. Series Map | # | Trigger | Job | Subject | CTA | Send-or-skip rule | ## 3. Full Email Drafts For each email: subject (under 50 chars), preview (under 90 chars), 60-200 word body in plain-text feel, single CTA, sender signature. ## 4. Drop-Off Recovery Branch - If user opens Email 1 but no click → Email 2 variant - If user opens Email 1 + 2 but no activation → Email 3 variant with a different angle - If user has not opened any email by Day 7 → final value-distilled email ## 5. Milestone Celebration Triggers - Activation event fired → 'You just did X' email - Power-user threshold (defined behavior) → 'You're in the top 10%' email - Each celebration email under 80 words, single CTA optional ## 6. Self-Check Is there a defined activation event? Does each email have one CTA? Is the 'thanks for signing up' filler banished? Is recovery branching included? # PROHIBITED PATTERNS - 'Thanks for signing up!' as the dominant message - 'Here are 5 things you can do' (multi-CTA paralysis) - A feature checklist email - 'We're so excited to have you' (centers the company, not the user) - An NPS survey before the user has activated - Multiple emojis in a B2B sequence - Auto-renewal reminders disguised as onboarding # CONSTRAINTS - Maximum 5 emails over 14 days. If user activates earlier, exit and route to lifecycle. - All copy in plain-text feel; mobile-readable; no image-dependent layouts. - One CTA per email. Always. - Subject lines under 50 characters; preview text under 90. - 'You did it' celebration emails are conditional on the actual event firing — never 'congrats!' on day 1 by default.
User Message
Write a 5-email onboarding series. **My product** (one sentence): {&{PRODUCT}} **The single first-value action** (the 'aha' moment): {&{FIRST_VALUE_ACTION}} **Why that action predicts retention**: {&{RETENTION_HYPOTHESIS}} **Target user persona**: {&{USER_PERSONA}} **Brand voice**: {&{BRAND_VOICE}} **Sender persona** (founder / product / CSM): {&{SENDER_PERSONA}} **Named customer who reached first value + outcome**: {&{CUSTOMER_PROOF}} **Adjacent habit that compounds first value**: {&{ADJACENT_HABIT}} Return the full 6-section deliverable per your output contract.

About this prompt

## The wasted welcome The most engaged moment in the entire customer relationship is the 60 seconds after sign-up. Most companies use it to send a 'Thanks for joining! We're so excited!' email with a feature checklist and a 'happy exploring!' sign-off. By email 3, the user is gone. The activation moment was wasted on filler. ## What this prompt does differently It forces the marketer to **define a single activation event before writing any email** — the specific behavior that, if completed in week 1, predicts long-term retention. Every email in the 5-touch series is then engineered to move the user toward that one event, with conditional branching for users who drop off mid-funnel. ## Behavior-triggered, not calendar-spammed Email 2 only fires if Email 1's CTA wasn't clicked. Email 3 fires either on activation or on Day 5 if not activated, with different copy in each path. Email 4 only fires after activation, introducing the next compounding habit. This converts the series from a fixed drip into a behavior-aware program that respects user signal. ## Real milestone celebration, not fake congratulations The prompt outputs separate milestone-celebration triggers — 'You just did X' for activation, 'You're in the top 10%' for power-user thresholds. These only fire on actual events, not by default on day 1. Users feel celebrated when celebration is earned and manipulated when it isn't. ## What you get back - An activation event definition with measurement spec - A 5-email series map with trigger conditions - Full drafts of all 5 emails in plain-text feel - A drop-off recovery branch for unengaged users - Milestone celebration triggers for activated users - A self-check ensuring no filler patterns slipped in ## When to use - PLG SaaS teams designing post-signup activation flows - B2C apps converting sign-up to first session - Marketplaces routing supply-side or demand-side users to first transaction - Founders setting up the first onboarding flow before scaling spend

When to use this prompt

  • check_circlePLG SaaS teams designing post-signup activation email flows
  • check_circleB2C apps converting sign-up to first session within week one
  • check_circleFounders setting up first-time onboarding sequences before scaling acquisition spend

Example output

smart_toySample response
An activation event definition, a 5-email series map with triggers, full email drafts in plain-text feel, drop-off recovery branches, milestone celebration triggers, and a self-check.
signal_cellular_altintermediate

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.