Optimize · Cold Email Rewriting
Rewrite a Cold Email With a Stronger CTA
Replace your weak 'open to a quick chat?' CTA with a specific, low-friction next step that prospects actually click.
foundermanagerrepBeginner⏱ ~12 min/email
When to use
Use when your open rates are fine but replies are dead. Most of the time the body is OK and the CTA is killing it — vague asks like 'open to a chat?' get ignored. Best when you can offer something concrete the prospect can say yes to without a calendar booking. Don't use this if your body is also weak — fix that first.
The prompt
You are a senior outbound copywriter for a digital marketing agency. You've A/B tested 200+ cold email CTAs and the pattern is brutal: 'open to a quick chat?' converts at 1-2%, specific low-friction asks (audits, teardowns, 1-pagers, named-time meetings) convert at 6-10%. Agency: [AGENCY_NAME] — [SERVICES] Prospect: [PROSPECT_NAME] at [PROSPECT_COMPANY] Current email with weak CTA: [CURRENT_EMAIL] Deliverables I can actually offer as low-friction CTAs: [AVAILABLE_DELIVERABLES] (e.g., 1-pager teardown, 10-min Loom audit, benchmark report, 15-min call with named agenda) Keep my email body roughly intact, but rewrite the CTA so it (a) proposes a specific next step from [AVAILABLE_DELIVERABLES], (b) reduces friction (no calendar required if possible), and (c) makes the value to the prospect explicit. Also rewrite the 1-2 lines that lead INTO the CTA so the ask feels earned, not bolted on. - Under 110 words total - Banned CTAs: "open to a quick chat?", "got 15 min?", "worth a conversation?", "happy to hop on a call", "let me know if you're interested" - The new CTA must be a single, specific yes/no question - The value of saying yes must be obvious in the CTA itself (what they get + how long it takes them) - Lead-in to CTA must connect to the email's hook, not pivot abruptly - Reads like a peer offering value, not a vendor asking for time Subject line: Full rewritten email: Old CTA → New CTA (1-line diff): Why the new CTA converts better:
Variables
- [AGENCY_NAME] — Your agency name
- [SERVICES] — Core services
- [PROSPECT_NAME] — Prospect first name
- [PROSPECT_COMPANY] — Prospect company
- [CURRENT_EMAIL] — Email with the weak CTA
- [AVAILABLE_DELIVERABLES] — List of low-friction assets you can offer — teardowns, audits, Loom walkthroughs, benchmarks, 1-pagers, etc.
Example input
AGENCY_NAME: Pierside SERVICES: Paid social for DTC apparel PROSPECT_NAME: Reese PROSPECT_COMPANY: Salt & Stone Apparel CURRENT_EMAIL: Subject: Quick question / Hey Reese, We help DTC apparel brands grow on Meta. We've done great work for similar brands and would love to chat about Salt & Stone. Open to a quick 30-min call next week to discuss? AVAILABLE_DELIVERABLES: 1) 5-min Loom teardown of their current Meta ad library 2) Benchmark report comparing their CPMs to 9 apparel brands we manage 3) 1-pager '90-day post-raise playbook' 4) 15-min audit call with screen-share
Example output
Subject: Salt & Stone ad library teardown Reese — we run paid social for 9 DTC apparel brands ($3.1M/mo Meta spend, avg 4.2x ROAS). Pulled your current Meta ad library this morning. Three things jumped out that look like the same pattern we fixed for Wovenly (28% CAC drop in 60 days). Want the 5-min Loom teardown? I'll record it Thursday and send it over — no call, no calendar link, just the video. If it's useful, we talk. If not, you've got a teardown. Yes / no? Old CTA → New CTA: "Open to a quick 30-min call?" → "Want the 5-min Loom teardown? Yes/no?" Why it converts: removes calendar friction, gives prospect a clear deliverable (5-min video), makes the value asymmetric (they get the teardown either way).
Pro tips
- The best CTAs answer 'what do I get + how long does it take me' in one sentence.
- If your low-friction deliverable requires you to do 4 hours of work per prospect, it's not low-friction — build a templated version first.
- Try replacing every calendar-link CTA with a 'yes/no?' CTA for one week. Track reply rate.
Works with
ClaudeChatGPTGemini
Done with prompts? Time to install the system
Book a STAOS callRelated prompts