Optimize · Cold Email Rewriting

Rewrite a Cold Email Using a Trigger Event

Rebuild your cold email around a specific trigger (funding, hire, launch, exec change) so the timing feels obvious.

founderrepIntermediate~25 min/email
When to use
Use when you've spotted a trigger event (new funding, exec hire, product launch, layoffs, expansion, RFP) and your existing template doesn't reference it. Trigger-based emails get 3-5x reply rates vs. generic outreach when the trigger is genuinely relevant to your offer. Don't force it — if the trigger doesn't connect to your service, the email feels stalkerish.
The prompt
You are a senior outbound copywriter for a digital marketing agency. You've built outbound systems around trigger events (funding rounds, exec hires, product launches, expansion announcements) and you know the pattern that works: lead with the trigger, connect it to a specific problem the trigger creates, offer one specific next step.

Agency: [AGENCY_NAME] — [SERVICES]
ICP: [ICP_DESC]
Prospect: [PROSPECT_NAME], [PROSPECT_TITLE] at [PROSPECT_COMPANY]
Trigger event: [TRIGGER_EVENT] (include date and source)
Why this trigger matters for our offer: [TRIGGER_RELEVANCE]
Current email: [CURRENT_EMAIL]

Rewrite my cold email so the trigger event is the opener and the entire pitch logically follows from it. The email should make it obvious why I'm reaching out NOW and not 3 months ago. Don't bury the trigger in line 4 — it goes in the subject or line 1.

- Under 100 words
- Trigger event in subject line OR first sentence — not buried
- Connect the trigger to a specific problem we solve — no generic "congrats on the news!"
- One specific CTA tied to the trigger (e.g., "want a 90-day plan for the new hire?")
- No "hope this finds you well", no "saw the news, congrats", no "thought I'd reach out"
- Reads like a peer who pattern-matches this trigger to a real problem

Subject line (must reference trigger):
Email body:
2 A/B subject variants:
Variables
  • [AGENCY_NAME] — Your agency name
  • [SERVICES] — Core services
  • [ICP_DESC] — ICP in one line
  • [PROSPECT_NAME] — Prospect first name
  • [PROSPECT_TITLE] — Prospect title
  • [PROSPECT_COMPANY] — Prospect company
  • [TRIGGER_EVENT] — The trigger — funding, hire, launch, layoffs, etc. + date + source
  • [TRIGGER_RELEVANCE] — 1-2 sentences on why this trigger creates demand for what you sell
  • [CURRENT_EMAIL] — Your current generic email
Example input
AGENCY_NAME: Pierside
SERVICES: Paid social for DTC apparel
ICP_DESC: DTC apparel brands $5-30M
PROSPECT_NAME: Devin
PROSPECT_TITLE: CMO
PROSPECT_COMPANY: Bayhill Apparel
TRIGGER_EVENT: Closed $12M Series B (TechCrunch, May 14, 2026)
TRIGGER_RELEVANCE: Post-Series B apparel brands almost always 3-5x ad spend within 90 days. Most blow up CAC because their creative pipeline can't keep up with the new budget.
CURRENT_EMAIL: Subject: Helping apparel brands grow / Hi Devin, We help DTC apparel brands scale on paid social. We'd love to chat about working with Bayhill.
Example output
Subject: post-Series B creative pipeline

Devin — saw the $12M Series B last week. Congrats.

Reason I'm reaching out now: every apparel brand we've onboarded post-Series B has 3-5x'd ad spend inside 90 days, and the #1 thing that breaks is the creative pipeline. New budget hits, same 4 ads/week, CAC blows up by month 2.

We ship 30+ creative variants/week for 9 apparel brands. Average CAC drop in the first 60 days post-onboarding: 28%.

Want the 90-day post-raise playbook we use? It's a 1-pager, no call needed.

A/B:
1. before you 3x ad spend
2. 90-day post-raise playbook
Pro tips
  • Set up Apollo/Clay/LinkedIn Sales Nav alerts for your top 3 trigger types — feed the prompt fresh triggers daily.
  • If the trigger is older than 30 days, lead with what's happened SINCE the trigger ('3 weeks in, what's broken?') instead of the trigger itself.
  • The best triggers create urgency the prospect already feels. If you have to explain why it matters, pick a different trigger.
Works with
ClaudeChatGPTGemini
Done with prompts? Time to install the system
Book a STAOS call
Related prompts