LeadHaste
IntermediateNo variables to fill — paste & go

Write a cold email when you have no personalization signal

Solves the no-signal prospect problem with segment-level precision instead of fake personalization. You get an under-80-word email whose opening problem statement is so specific to the role and industry that it reads as researched — the honest, scalable alternative to 'I was browsing your website'.

The prompt
You are a cold email strategist who specializes in the hardest brief in outbound: the prospect where you have nothing — no trigger, no post, no news, just a name, a title, and a company. You know the two standard failures here: faking personalization ('I was browsing your website and was impressed') or giving up and blasting a feature pitch. Your approach is different: when you can't be personal, be precisely relevant. A hyper-specific problem statement for a narrow role-industry-size combination reads as researched even when it's segment-level.

Write ONE cold email:

- Under 80 words.
- Opens with a problem statement so specific to this role at this type of company that a stranger reading it would assume research happened. Name the situation, the internal symptom, or the tradeoff they live with — not 'companies like yours struggle with X'.
- One outcome sentence with proof, one interest-based CTA.
- Absolutely banned: fake familiarity, 'I noticed', 'I came across', compliments about the company, and any claim to have researched them individually.

Also give me a 1-3 word lowercase subject line that matches the problem, not my product.

Before you write anything, interview me. Ask me these questions ONE AT A TIME, waiting for my answer each time:
1. What do you sell, and what's your proudest concrete customer outcome?
2. Define the segment narrowly: exact role, industry, and company size.
3. What does this problem look like from inside their job — what do they see, complain about, or work around?
4. What would this person be doing about the problem today without you?

Once you have my answers, write the email. If my segment in question 2 is broad, narrow it with me first — segment-level relevance only works when the segment is tight.

How to use it

  1. 1

    Copy the prompt into Claude, ChatGPT, or any LLM.

  2. 2

    Answer the interview — question 3 is where the email is won; describe the problem in the prospect's own vocabulary.

  3. 3

    Check the opener against the 'stranger test': would a prospect assume you researched them?

  4. 4

    Use the output as the default step for unenriched prospects in your sequencer, and re-run per segment.

Best practices

  • Narrow beats broad every time — 'ops managers at 50-200 person 3PLs' can get a specific email; 'logistics companies' cannot.

  • Source question 3 from real material: call recordings, reviews of competitor tools, or community threads where your buyers complain.

  • Never let the model sneak in implied personalization; honesty about being segment-level is what keeps this deliverability- and trust-safe.

  • Write one version per segment, not one version for everyone — the whole method depends on it.

Example: what this looks like in practice

An SDR at a 60-person payroll platform has 300 prospects with nothing but names and titles — controllers at 100-500 person manufacturers. In the interview he describes the inside view from support tickets: month-end payroll reconciliations done in spreadsheets because the ERP and time-tracking system don't talk. The model writes a 74-word email opening with 'Most controllers running payroll across an ERP and a separate time system lose two to three days a month to reconciliation nobody sees.' Subject line: 'month-end payroll'. The segment pulls a 3.4% reply rate with zero personalization data — and several replies ask how he knew their setup.

Best fit

Roles
SDR / BDRFounder / CEORevOps
Company size
Solo founderStartup (1–10)SMB (11–50)Mid-market (51–500)
Audience
B2B
Industries
Any industry
Works with
Any LLM
Difficulty
Intermediate

This prompt is one gear in a bigger machine. We orchestrate 20+ tools into outbound systems our clients own — and guarantee the results.

Apply for a Pilot Spot →
Prompt FAQ

Frequently asked questions

You don't fake it — you substitute segment relevance for personal relevance. A problem statement precise to the prospect's exact role, industry, and company size reads as researched even though it's written once per segment. That's what this prompt engineers, and it consistently beats both generic blasts and fabricated 'I noticed' openers.