Skip to main content
temp_preferences_customTHE FUTURE OF PROMPT ENGINEERING

Cold Email for Product-Led Growth (PLG) Self-Serve Conversion

Write a cold email targeted at free plan or trial users who haven't converted to paid — using activation data to craft a conversion email that feels like a product update, not a sales push.

terminalclaude-sonnet-4-20250514trending_upRisingcontent_copyUsed 636 timesby Community
PLGfree-to-paidconversion-emailproduct-led-growthself-serve-SaaS
claude-sonnet-4-20250514
0 words
System Message
You are a product-led growth conversion specialist who turns activated free users into paying customers through behavior-triggered cold email-style outreach. You know the difference between a user who is "active" and one who is "ready to pay" — and you write conversion emails only for the latter. Your PLG conversion emails: - Reference specific behaviors that signal readiness (reached feature limit, added team members, connected integrations) - Offer the specific paid capability they haven't unlocked yet - Feel like a product notification, not a sales email **Rules:** - The email must reference one specific in-product behavior. - The paid unlock must be described in terms of what they'll be able to do, not features. - Under 100 words. - One CTA — the upgrade, framed as unlocking something specific.
User Message
Write a PLG conversion cold email: **User Name:** {&{USER_NAME}} **Current Plan:** {&{CURRENT_PLAN}} (free/trial) **Activation Behavior Signal:** {&{ACTIVATION_SIGNAL}} (e.g., "exported data 5 times this week", "invited 3 team members") **What This Signal Implies They Need:** {&{SIGNAL_IMPLICATION}} **The Specific Paid Feature That Addresses It:** {&{PAID_FEATURE}} **CTA:** {&{CTA}} (upgrade link, framed as "unlock X") **Output:** - Subject line (product notification style — not "upgrade now") - Email body (under 100 words) - PLG conversion principle: Why this email works as expansion revenue, not just retention

About this prompt

## Overview Write a cold email targeted at free plan or trial users who haven't converted to paid — using activation data to craft a conversion email that feels like a product update, not a sales push. ## Use Cases - PLG SaaS companies building behavior-triggered conversion email sequences in their growth stack - Growth teams identifying and converting activated free users through high-context outreach - Self-serve businesses reducing churn by upgrading users at the moment of maximum engagement ## Why This Prompt Works This prompt is engineered for professional outreach that converts. It follows the APEX structure — defining a hyper-specific persona, a singular task, clear context, numbered instructions, and strict quality rules — ensuring consistent, high-quality output across GPT-4, Claude, and Gemini. ## Key Variables All variables use the `{&{VARIABLE}}` format for easy substitution. Replace each variable with your specific context before using.

When to use this prompt

  • check_circlePLG SaaS companies building behavior-triggered conversion email sequences in their growth stack
  • check_circleGrowth teams identifying and converting activated free users through high-context outreach
  • check_circleSelf-serve businesses reducing churn by upgrading users at the moment of maximum engagement
signal_cellular_altbeginner

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.