Verified against ChatGPT · 2026-08-14
Build a cold outreach message from a specific trigger event instead of a generic timing coincidence
Writes a short outreach message anchored to a real, recent trigger event at the prospect's company, with an explicit check on whether the event genuinely justifies the outreach timing or is just being used as a flimsy excuse to message.
The prompt
Ready to copy — highlighted parts are example details you can swap.
Write a short outreach message triggered by a specific event at this company. Before drafting anything, tell me honestly whether this event actually justifies reaching out now, or whether it's a weak excuse being stretched to look like good timing. THE TRIGGER EVENT They announced last week they're opening a second warehouse location in a new region. COMPANY AND CONTACT Priya Nair, VP of Logistics, mid-size e-commerce retailer. WHAT I'M OFFERING Multi-location inventory sync software that prevents stock discrepancies across warehouses. WHY I THINK THIS EVENT MATTERS TO THEM RIGHT NOW A second warehouse location almost always creates inventory sync problems in the first few months that a single-location setup never had. First, assess honestly: does this trigger event create an actual, specific new need or pressure connected to what I'm offering, or is it just company news that happens to have occurred recently with no real causal link to my offer? If it's a weak link, say so plainly and tell me what would make a better trigger, rather than forcing a stretch connection into a message anyway. If the link is genuinely real, write the message so the event is the reason for the message's existence, not a decorative opening line bolted onto an otherwise generic pitch — the recipient should finish the message unable to imagine it being sent to them without this event having happened. Keep it short — under 100 words. State plainly, without hedging, why this specific moment is different from any other time you might have reached out. End with a single specific, low-effort next step. Do not invent details about the trigger event beyond what I've told you, and do not invent a statistic or outcome claim to strengthen the pitch. Output: first, one line — "Real trigger" or "Weak link, here's why" — then, only if real, the message itself.
Customize
Optional — swap in your own details for the highlighted parts above.
Why this works
Requiring an honest validity check on the trigger event before any drafting happens is the load-bearing rule in this prompt, because a model asked to "write outreach based on this trigger event" will draft persuasive-sounding copy regardless of whether the underlying causal link is real — fluency in language generation is not correlated with the strength of the argument being made, so without an explicit instruction to evaluate the link first, the model will happily produce a confident-sounding message built on a coincidental timing connection that a savvy recipient will see through immediately as a stretch. The instruction that the recipient should "finish the message unable to imagine it being sent without this event having happened" is a concrete, checkable bar that rules out the most common failure in trigger-based outreach: an opening line that name-drops the event ("Congrats on the new warehouse!") followed by a generic pitch that could have been sent regardless — that structure uses the trigger as decoration rather than as the actual reason for the message, and prospects register that gap even when they can't articulate it. Capping the message under 100 words and requiring a plain, non-hedged statement of why this moment specifically differs from any other time works against GPT-5.1's tendency to soften time-sensitive claims with qualifiers ("this might be a good time to consider...") that dilute exactly the urgency a trigger-event message is supposed to carry — a trigger that's genuinely real deserves to be stated with actual confidence, and hedged phrasing undercuts the one advantage this message type has over generic cold outreach. Banning invented details or statistics beyond what's supplied protects against the model manufacturing a specific-sounding but false elaboration on the trigger event itself, which would misrepresent something publicly checkable about the prospect's own company back to them.
What you get back
Real trigger. Message: "Saw the new warehouse announcement — most retailers hit inventory sync gaps in the first few months of running two locations, usually before anyone's looking for a fix. Worth a quick look at how that plays out for your setup before it becomes a real headache? Happy to send a two-minute walkthrough, no call needed."
Verified against
ChatGPT GPT-5.1 · 2026-08-14
Changelog
- 2026-08-14 — Initial publish, verified against ChatGPT GPT-5.1.
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
