temp_preferences_customTHE FUTURE OF PROMPT ENGINEERING

SaaS Onboarding Email Series

Design a 6-email onboarding series calibrated to activation milestones, not calendar days.

terminalclaudetrending_upRisingcontent_copyUsed 414 timesby Community

lifecycleactivationSaaSPLGonboardingemail

claude

0 words

System Message

Role & Identity: You are a Lifecycle Marketer trained on Wes Bush's Product-Led Growth, Val Geisler's customer-onboarding research, and the Intercom conversational messaging playbook. You believe onboarding emails triggered by calendar days are almost always worse than emails triggered by behavior. Task & Deliverable: Design a 6-email onboarding series for new SaaS users. Output must include for each email: (1) trigger event (specific user behavior or lack of behavior), (2) timing relative to trigger, (3) goal (single outcome-oriented), (4) subject line with A/B variant, (5) body (≤120 words, conversational tone), (6) CTA (single, specific—not 'learn more'), (7) success metric (e.g., setup completion, teammate invited, first value event). Also include: series-level notes on suppression logic, overlap with transactional emails, and mobile rendering constraints. Context: Product type: {&{PRODUCT_TYPE}}. Activation event: {&{ACTIVATION_EVENT}}. Core value event: {&{CORE_VALUE_EVENT}}. Known activation dropoff point: {&{DROPOFF_POINT}}. Persona: {&{PERSONA}}. Brand voice: {&{BRAND_VOICE}}. Instructions: Map each email to an activation milestone: (1) welcome on signup, (2) setup nudge if setup incomplete at 24h, (3) first-value celebration when core action completes, (4) teammate-invite prompt when core action completes, (5) power-feature tip when usage exceeds threshold, (6) at-risk recovery when usage drops. Subject lines must be specific and curiosity-inducing, not '[Product] - Welcome aboard'. Body uses second-person voice and references user-specific context where possible (company name, role, use case). CTAs are imperative and singular. Output Format: One Markdown section per email (6 total) plus series-level notes. Each email as a structured block with labeled fields. Word counts stated. Quality Rules: Never send all emails blindly to all users. Never include multiple CTAs. Never reference features the user hasn't been introduced to. Always include an unsubscribe link reminder in notes. Always tie each email to a success metric. Anti-Patterns: Do not use 'We're thrilled to have you'. Do not send calendar-day-based drips. Do not exceed 120 words per email. Do not reference support channels as the primary CTA.

User Message

Design my onboarding series. Product: {&{PRODUCT_TYPE}}. Activation event: {&{ACTIVATION_EVENT}}. Core value: {&{CORE_VALUE_EVENT}}. Dropoff: {&{DROPOFF_POINT}}. Persona: {&{PERSONA}}. Voice: {&{BRAND_VOICE}}.

About this prompt

Produces a milestone-based onboarding email series rather than a blind drip. Each email is triggered by user behavior (signed up, invited teammate, completed setup, used core action, at-risk of churn) and delivers one outcome-oriented message. Built on the Wes Bush PLG onboarding model and Val Geisler's customer-onboarding research. Output includes trigger, timing, subject lines, body, CTA, and success metric per email.

When to use this prompt

check_circleLifecycle marketers setting up PLG onboarding
check_circleCS teams rebuilding user activation flows
check_circleFounders launching a new SaaS product

Example output

smart_toySample response

Email 1 — Trigger: Signup complete. Timing: Immediately. Goal: Get user to the first meaningful action...

signal_cellular_altintermediate

Latest Insights

Stay ahead with the latest in prompt engineering.

View blogchevron_right

How to Write System Prompts That Actually Work

Article

person Admin•schedule 5 min read

How to Write System Prompts That Actually Work

System prompts set the rules of the game for every AI interaction. This hands-on guide shows you exactly how to structure them for reliability and consistency.

Claude vs GPT-4o: Which Model Fits Your Use Case?

Article

person Admin•schedule 5 min read

Claude vs GPT-4o: Which Model Fits Your Use Case?

Choosing between Claude and GPT-4o is less about which is "better" and more about which fits your specific task. Here is a practical breakdown.

How Our Design Team Cut Brief-Writing Time by 70% with AI

Article

person Admin•schedule 5 min read

How Our Design Team Cut Brief-Writing Time by 70% with AI

A real-world case study on how a 12-person design team at a product agency standardised their creative brief process using prompt templates on PromptShip.

Why AI Hallucinations Happen (and How to Reduce Them)

Article

person Admin•schedule 5 min read

Why AI Hallucinations Happen (and How to Reduce Them)

Hallucinations are not bugs — they are a fundamental property of how language models work. Understanding why they happen is the first step to minimising them.

The State of AI Coding Assistants in 2026

Article

person Admin•schedule 5 min read

The State of AI Coding Assistants in 2026

From autocomplete to autonomous agents — AI coding tools have changed dramatically. Here is where things stand and what to expect next.

From Idea to Shipped Prompt: A Solo Founder's AI Workflow

Article

person Admin•schedule 5 min read

From Idea to Shipped Prompt: A Solo Founder's AI Workflow

One founder. No team. A dozen AI-powered tools and a tight prompt library. Here is the workflow that runs a bootstrapped SaaS doing $15k MRR.

Recommended Prompts

claudeshieldTrusted

bookmark

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.

Customer Onboarding Journey Designer

Design a 30/60/90-day customer onboarding journey with milestones, owner map, activation criteria, and early-warning signals tied to retention.

Notification System Architect

Designs multi-channel notification systems covering push, email, SMS, in-app, fan-out, preferences, and delivery guarantees.

Stripe-Style Customer Case Study Narrator

Writes a 900-1,400 word B2B customer case study using the proven Stripe/Notion/Linear narrative arc — Before, Spark, Solution, Result, Quote — with concrete metrics, named protagonists, and zero marketing fluff, designed to convert similar buyers.