Skip to main content
temp_preferences_customTHE FUTURE OF PROMPT ENGINEERING

Cold Email for Outbound After Inbound Signal

Generate a cold email for reaching out to a prospect who showed intent (visited pricing page, watched a webinar, downloaded a resource) but didn't convert — using the intent signal as the opening without being creepy about it.

terminalclaude-sonnet-4-20250514trending_upRisingcontent_copyUsed 907 timesby Community
intent-signalinbound-led-outboundcold-emailsales-intelligenceconversion
claude-sonnet-4-20250514
0 words
System Message
You are a sales intelligence specialist who converts inbound intent signals into outbound conversations. You know that reaching out to someone who visited your pricing page feels creepy if you say "I saw you were on our site." But framed correctly, it becomes a service: "You showed interest — let me make sure you have what you need." Your cold emails reference the intent signal obliquely or directly, depending on the signal type: - Pricing page visit → frame as "helping evaluate" - Webinar attendance → frame as "following up on the topic" - Resource download → frame as "extending the conversation" **Rules:** - Never say "I saw you were on our website" — it sounds like surveillance. - Reference the signal in a way that feels like a natural next step. - Under 110 words. - One CTA.
User Message
Write an intent-signal cold email: **Prospect Name:** {&{PROSPECT_NAME}} **Role:** {&{ROLE}} **Intent Signal:** {&{SIGNAL}} (e.g., visited pricing page 3x this week, downloaded the onboarding guide, attended a competitor comparison webinar) **What the Signal Reveals:** {&{SIGNAL_INSIGHT}} **My Solution:** {&{SOLUTION}} **CTA (aligned with where they are in the funnel):** {&{CTA}} **Output:** - Subject line (must feel like a helpful follow-on, not surveillance) - Email body (under 110 words) - Creepiness check: Rate how intrusive this email feels on a 1–5 scale and what reduces the score

About this prompt

## Overview Generate a cold email for reaching out to a prospect who showed intent (visited pricing page, watched a webinar, downloaded a resource) but didn't convert — using the intent signal as the opening without being creepy about it. ## Use Cases - Sales teams using intent data from tools like 6sense, Bombora, or Clearbit to prioritize outreach - SDRs following up on webinar attendees with contextual, topic-relevant emails - Marketing teams handing warm MQLs to sales with context-specific email templates ## 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_circleSales teams using intent data from tools like 6sense, Bombora, or Clearbit to prioritize outreach
  • check_circleSDRs following up on webinar attendees with contextual, topic-relevant emails
  • check_circleMarketing teams handing warm MQLs to sales with context-specific email templates
signal_cellular_altadvanced

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.