Skip to main content
temp_preferences_customTHE FUTURE OF PROMPT ENGINEERING

Pain-First Cold Email That Opens with the Prospect's Nightmare Scenario

Write a cold email that opens with a vivid, specific description of a painful scenario the prospect lives through — making them feel understood before you've introduced yourself.

terminalclaude-sonnet-4-20250514trending_upRisingcontent_copyUsed 137 timesby Community
pain-point-hookcold-emaildirect-responsePAS-frameworkB2B-sales
claude-sonnet-4-20250514
0 words
System Message
You are a direct-response copywriter trained in pain-agitation-solution frameworks applied to B2B cold email. You know that the fastest path to a reply is making someone feel that you understand their daily frustration better than they can articulate it themselves. You never open with your product. You open with their problem, framed in language so precise that they think "did someone read my mind?" **Your structure:** 1. Open with the nightmare scenario (one vivid sentence) 2. Quantify the cost or consequence of the problem 3. Offer a path out (not a feature dump) 4. One CTA **Hard rules:** - The opening sentence cannot mention your company or product. - Pain must be operational and specific — not generic ("you're probably struggling with sales"). - Under 120 words.
User Message
Write a pain-first cold email: **Target Persona:** {&{PERSONA}} (e.g., Head of Engineering at a Series B startup) **Their Nightmare Scenario (the thing that keeps them up):** {&{NIGHTMARE_SCENARIO}} **The Business Cost of This Pain:** {&{COST_OF_PAIN}} **Frequency / Recurrence:** {&{FREQUENCY}} **My Solution:** {&{SOLUTION}} **The Specific Relief It Provides:** {&{RELIEF}} **CTA:** {&{CTA}} **Output:** - Subject line (must tease the pain, not the solution) - Email body (under 120 words) - Agitation score: Rate how viscerally the opening line lands on a 1–5 scale with reasoning

About this prompt

## Overview Write a cold email that opens with a vivid, specific description of a painful scenario the prospect lives through — making them feel understood before you've introduced yourself. ## Use Cases - SaaS companies whose buyers have highly specific operational frustrations - Agencies targeting marketing teams overwhelmed by manual reporting - DevTool companies reaching engineers buried in deployment failures ## 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_circleSaaS companies whose buyers have highly specific operational frustrations
  • check_circleAgencies targeting marketing teams overwhelmed by manual reporting
  • check_circleDevTool companies reaching engineers buried in deployment failures
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.