Three cold email variants for A/B/C testing
Use when you want to test distinct outreach angles to the same ICP segment rather than tweaking one line.
Act as a cold email strategist. Produce 3 structurally different cold emails to the same audience so I can split-test angles, not just words.
ICP segment: {{icp_segment}}
Pain I solve: {{pain}}
Proof I can point to: {{proof}}
CTA goal: {{cta_goal}}
Variant A: pain-led (lead with the cost of the status quo).
Variant B: outcome-led (lead with a specific result a peer got).
Variant C: question-led (open with a sharp diagnostic question).
For each: subject line, body under 80 words, and a one-line note on which belief this variant is testing. Keep tone direct and peer-to-peer. No emojis, no em dashes.Click the copy button in the top right of the block to grab the full prompt.
Replace each placeholder below with your own values before you run the prompt.
- {{icp_segment}}
- {{pain}}
- {{proof}}
- {{cta_goal}}
Related prompts
You are an experienced B2B sales rep who writes short, human cold emails that get replies. Write a first-touch cold email to {{prospect_name}}, who is {{prospect_role}} at {{prospe...
You are a sales copywriter. Create three distinct cold email variations for the same prospect so I can A/B test them. Prospect: {{prospect_role}} at {{prospect_company}} What I sel...
You write natural LinkedIn connection notes that do not feel like a pitch. Write a connection request note to {{prospect_name}}, {{prospect_role}} at {{prospect_company}}. Reason f...
You are a social-selling expert. Build a 4-message LinkedIn DM sequence for a prospect who just accepted my connection request. Prospect: {{prospect_role}} at {{prospect_company}}...
You write follow-up emails that add value rather than nag. Write a follow-up to {{prospect_name}} who did not reply to my first email. Original email was about: {{original_topic}}...
You are a sales cadence specialist. Design a 5-email follow-up sequence for a cold prospect. Prospect type: {{prospect_role}} at companies like {{target_company_profile}} What I se...
0 Comments
Loading discussion...