Optimize · Personalization at Scale

Write Personalized P.S. Lines for Cold Emails

Generate a batch of throwaway-but-specific P.S. lines (the last thing prospects actually read) tied to one detail per prospect.

repmanagerBeginner⏱ ~90 min per 50-prospect batch
When to use
Use when your base cold email is locked but you want to A/B a personalized P.S. — the line that often gets read even when the body is skimmed. The P.S. is short, low-stakes, and a great place to prove you did your homework without bloating the body.
The prompt
You are an agency SDR who knows the P.S. is the second-most-read line in a cold email. You use it for one human, specific observation per prospect.

Agency: [AGENCY_NAME] — [SERVICES]
Base email (unchanged): [BASE_EMAIL]
Prospect data (CSV or block per row):
[PROSPECT_CSV]

For each prospect, write ONE personalized P.S. line (≤20 words) that references a specific, verifiable detail — and is NOT a restatement of the email's CTA.

- P.S. must reference something specific (a podcast they were on, a tool in their stack, a city they're in, a specific page or product, a recent hire). Cite the source detail.
- P.S. must NOT pitch, restate the CTA, or say "would love to chat".
- Tone: human, low-stakes, mildly curious or complimentary in a specific way.
- If the row has no usable detail beyond name/title/company, output: "SKIP — no P.S. signal".
- Never invent a detail. If unsure, SKIP.

Prospect: [name] @ [company]
Detail used: [exact source phrase]
P.S.: P.S. [≤20 words]

Or:
Prospect: [name] @ [company]
SKIP — no P.S. signal

End with: "Generated: X | Skipped: Y".
Variables
  • [AGENCY_NAME] — Your agency
  • [SERVICES] — What you sell
  • [BASE_EMAIL] — The locked cold email body
  • [PROSPECT_CSV] — Enriched prospect list
Example input
AGENCY_NAME: Northpoint Digital
SERVICES: SEO for B2B SaaS
BASE_EMAIL: "...standard 4-line cold email ending in a CTA for a 15-min audit..."
PROSPECT_CSV:
name,company,detail
Sara Chen,Latchpad,"Was a guest on Demand Curve podcast Ep 142"
Mike Ortiz,Brillo,""
Priya Shah,Quotient HR,"Their /resources/ uses HubSpot CMS — visible in page source"
Example output
Prospect: Sara Chen @ Latchpad
Detail used: "Was a guest on Demand Curve podcast Ep 142"
P.S.: P.S. The Demand Curve ep was good — the part about pricing-page CRO is the one I keep recommending.

Prospect: Mike Ortiz @ Brillo
SKIP — no P.S. signal

Prospect: Priya Shah @ Quotient HR
Detail used: "Their /resources/ uses HubSpot CMS"
P.S.: P.S. Noticed /resources/ is on HubSpot — we've shipped some nasty schema wins there, happy to share if useful.

Generated: 2 | Skipped: 1
Pro tips
  • P.S. lines outperform openers in reply rate on lots of agency tests — A/B base-email-only vs base-email + P.S.
  • Don't pitch in the P.S. It's the human moment; the body did the selling.
  • Cite tech stack details (BuiltWith, page source) — they're verifiable and rarely used by competitors.
Works with
ClaudeChatGPTGemini
Done with prompts? Time to install the system
Book a STAOS call
Related prompts