Verified against ChatGPT · 2026-07-14
Turn one research signal into a cold email that doesn't read like a template
Build a cold-outreach email around a single verifiable trigger event instead of a generic personalization token, with banned generic openers spelled out.
The prompt
Ready to copy — highlighted parts are example details you can swap.
I'm writing a cold email to Priya Menon, VP of Operations at Fenwick Logistics. I want to open with ONE specific, real signal about them or their company — not a generic compliment. The trigger/signal I found: Posted on LinkedIn last week about opening a third regional warehouse What we sell: route-planning software for multi-warehouse logistics teams The specific problem it solves that connects to this trigger: A third warehouse usually means route planning that worked for two locations starts breaking down What I want them to do next: Worth a 15-minute call next week, or is this not the right time? Write a cold email following this structure, each part as ONE sentence except where noted: 1. OBSERVATION — reference Posted on LinkedIn last week about opening a third regional warehouse specifically enough that they could not mistake this for a mass email. No "I noticed you're the VP of Operations at Fenwick Logistics" openers — that's not a signal, that's a mail-merge field. 2. RELEVANCE — connect the observation to a problem Fenwick Logistics likely has right now, using A third warehouse usually means route planning that worked for two locations starts breaking down. Do not pitch yet. 3. VALUE — one sentence naming what we do, framed as the solution to the problem just named, not a feature list. 4. ASK — Worth a 15-minute call next week, or is this not the right time?, framed as a low-friction yes/no question, not "let me know if you're interested." Constraints: under 90 words total. No "I hope this email finds you well." No em dashes. Write 3 variants that differ in the observation-to-relevance bridge, not just synonym-swapping, so I can see genuinely different angles. After the 3 variants, tell me honestly whether Posted on LinkedIn last week about opening a third regional warehouse is strong enough to build an email around, or too generic to use — say so even if it means the answer is "this one's weak."
Customize the highlighted detailsoptional — the prompt above already works
Why this works
Naming and banning the specific generic opener ("I noticed you're the {{prospect_title}} at {{company_name}}") is the load-bearing move here — that exact sentence pattern is what makes mail-merge personalization instantly recognizable, and most prompts never rule it out explicitly. Capping the email at 90 words and forcing three variants that differ in reasoning path, not phrasing, stops the model from padding with filler or generating three emails that make the identical point in different words. The closing instruction to call out a weak trigger signal matters because a model asked only to "write the email" will personalize convincingly around a signal that has no real relevance link, which is how forced personalization ends up reading worse than no personalization at all.
What you get back
Priya — saw your post about the third warehouse going live next month. Most route-planning setups that work fine for two sites start falling apart once a third hub enters the mix — drivers end up covering overlapping zones nobody planned for. We built routing software specifically for that multi-warehouse handoff. Worth 15 minutes next week, or is this not the right time?
Verified against
ChatGPT GPT-5.1 · 2026-07-14
Claude Sonnet 4.5 · 2026-07-16
Changelog
- 2026-07-16 — Initial version, verified against GPT-5.1 and Claude Sonnet 4.5.
Need this built into your business?
If a prompt isn't enough — Google Ads management, built and maintained for you — that's Scult's day job.
EXPLORE GOOGLE ADS MANAGEMENT

