Optimize · Subject-Line & A/B Variants

Generate Subject Lines That Reference a Recent Post

Reference a prospect's recent LinkedIn or blog post in the subject line — 8 variants that earn the open without sounding like a stalker.

repmanagerAdvanced30-45 min
When to use
Use this when a prospect just posted something on LinkedIn, their company blog, or a podcast and you want to use it as an authentic opener. Done right, it has the highest open + reply rate of any outbound tactic. Done wrong, it reads like an SDR script. This prompt writes 8 variants that reference the post without parroting it.
The prompt
You are a cold-email specialist for a digital marketing agency. You know the line between "I read your post" (great) and "I commented on your post and now I'm DMing you" (creepy).
Agency: [AGENCY_NAME] — [SERVICES] | Email body: [EMAIL_BODY] | Prospect: [PROSPECT_NAME] at [PROSPECT_COMPANY] | Post link: [POST_LINK] | Post topic in 1 line: [POST_TOPIC] | Days since post: [DAYS_SINCE_POST] | The single most interesting claim or detail in the post: [POST_HOOK]
Write 8 subject line variants that reference [POST_TOPIC] or [POST_HOOK] honestly and tie naturally to [SERVICES].

- Max 7 words
- Reference the post content but NEVER "loved your post" or "great post on..."
- 2 variants must extend the post's argument; 2 must respectfully push back; 2 must ask a follow-up question; 2 must connect the post to a concrete [SERVICES] outcome
- Lowercase, no emoji, no spam triggers
- Stop being relevant after 14 days; flag if [DAYS_SINCE_POST] > 14
- Do NOT quote the post verbatim in the subject

Numbered 1-8: subject — type (extend / push-back / question / services-tie) — rationale (1 line). Mark (WINNER). End with a flag if [DAYS_SINCE_POST] > 14.
Variables
  • [AGENCY_NAME] — Your agency
  • [SERVICES] — Services
  • [EMAIL_BODY] — Email body
  • [PROSPECT_NAME] — First name
  • [PROSPECT_COMPANY] — Company
  • [POST_LINK] — URL to the post
  • [POST_TOPIC] — 1-line summary of post topic
  • [DAYS_SINCE_POST] — Days since the post went live
  • [POST_HOOK] — The most interesting specific claim from the post
Example input
Agency: PixelBarn — Webflow dev | Email body: offer to apply Maya's own framework to Klario's homepage | Prospect: Maya at Klario | Post link: linkedin.com/.../maya-hero-framework | Post topic: how to write a B2B hero in 3 lines | Days since: 4 | Post hook: "most B2B heroes are 11 words too long"
Example output
1. 11 words too long (WINNER) — extend — uses her hook back at her own homepage.
2. klario's hero is 14 words — services-tie — applies her rule to her own site.
3. counter-take on hero length — push-back — invites a debate she'll engage with.
4. line 2 of your framework? — question — extends her thinking.
5. her framework vs klario's hero — services-tie — implicit mirror.
6. when does line 1 fail? — question — pushes her framework's edge case.
7. shorter doesn't always win — push-back — respectful challenge.
8. extending your 3-line rule — extend — collaborative tone.
Pro tips
  • Reference the post in the subject AND open the email with a specific reaction — vague "loved your post" in body 1 kills the whole hook.
  • Push-back variants get the highest reply rate from founders — they want to debate, not be agreed with.
  • If the post is older than 14 days, switch to referencing a pattern across their last 3 posts instead — looks more thoughtful.
Works with
ClaudeChatGPTGemini
Done with prompts? Time to install the system
Book a STAOS call
Related prompts