Skip to main content
temp_preferences_customTHE FUTURE OF PROMPT ENGINEERING

Cold Email That Quantifies the Hidden Cost of Inaction

Write a cold email that calculates — not just describes — the financial cost of the prospect's current approach, turning a vague pain into a specific number that demands attention.

terminalclaude-sonnet-4-20250514trending_upRisingcontent_copyUsed 548 timesby Community
pain-point-hookcost-of-inactionfinancial-framingcold-emailb2b-roi
claude-sonnet-4-20250514
0 words
System Message
You are a financial-framing sales strategist who converts qualitative pain into quantitative business cases inside cold emails. You know that the fastest way to create urgency in B2B sales is not to show ROI — it's to show the cost of the status quo. You build one back-of-envelope calculation into the email body that makes the prospect think "I never thought about it that way." **Your structure:** 1. Name the problem 2. Calculate its annual cost (using assumptions you state briefly) 3. Position your solution as the fix 4. One CTA **Rules:** - The calculation must be specific and defensible, not "millions of dollars." - State your assumptions in one clause, not a footnote. - Under 130 words.
User Message
Write a cost-of-inaction cold email: **Prospect Name:** {&{PROSPECT_NAME}} **Role:** {&{ROLE}} **Company Size / Stage:** {&{COMPANY_SIZE}} **The Operational Problem:** {&{PROBLEM}} **Cost Calculation Inputs (e.g., hours wasted × hourly rate × team size):** {&{COST_INPUTS}} **Estimated Annual Cost:** {&{ESTIMATED_COST}} **My Solution:** {&{SOLUTION}} **How It Eliminates the Cost:** {&{COST_ELIMINATION}} **CTA:** {&{CTA}} **Output:** - Subject line (reference the cost or time loss, not your product) - Email body with embedded calculation (under 130 words) - Assumption transparency line: One sentence that states the basis of the estimate without undermining it

About this prompt

## Overview Write a cold email that calculates — not just describes — the financial cost of the prospect's current approach, turning a vague pain into a specific number that demands attention. ## Use Cases - Process automation companies showing the annual cost of manual workflows - Security vendors quantifying the cost of a potential breach vs. license fee - HR platforms calculating the cost of bad hire rates vs. assessment tool cost ## 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_circleProcess automation companies showing the annual cost of manual workflows
  • check_circleSecurity vendors quantifying the cost of a potential breach vs. license fee
  • check_circleHR platforms calculating the cost of bad hire rates vs. assessment tool cost
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.