HAMMAD YOUSUF

SALES OPERATIONS // FREE LIVE DEMO

Signal Opener Writer

Trigger events — a funding round, a new hire, an office expansion — get spotted and then wasted on a generic "congrats on the news!" opener that reads like every other message referencing the same event.

WHAT IS SIGNAL OPENER WRITER?

An AI signal-based opener writer takes a specific trigger event — a funding round, a new hire, a product launch, a market expansion — and writes a cold-outreach opener that connects the event to a concrete operational implication, deliberately avoiding the generic 'congrats on the news!' pattern that most trigger-based outreach falls into.

HOW IT WORKS

Trigger-event outreach has a well-known failure mode: everyone who spots the same public signal (a funding announcement, a LinkedIn hire post) sends some version of 'congrats!' the same week, and the prospect's inbox fills with identical noise. This agent is prompted to skip the congratulations sentence entirely and instead reason one step further — what does this specific event imply operationally, and why does that implication create urgency to talk now rather than later. A funding round implies budget; a rapid hiring spree implies onboarding strain; a new office implies logistics gaps before staffing catches up.

The system prompt enforces this by requiring the opener to name the event and state its operational consequence in the same sentence, which structurally prevents the generic congratulations pattern from slipping through — there's no room left in the output for it.

Gemini 2.0 FlashStructured JSON outputTrigger-event pattern library
system-prompt.md
You are a trigger-event outreach copywriter. Given a specific trigger event (funding, hiring, launch, expansion, leadership change) and a prospect, write an opener that explicitly connects the event to a concrete operational implication — not a congratulations line. The opener must name the event and state why it specifically creates a reason to talk now. Output ONLY a JSON array of typed blocks matching the OutputBlock union — no prose outside the JSON.

USE CASES

Funding-announcement outreach

A target company raises — the agent turns the raise into a specific budget-and-scaling implication instead of a congratulations line lost in the inbox crowd.

New-hire trigger outreach

A prospect hires a new Head of Ops or Marketing — the agent frames the opener around what that new hire will need in their first 90 days.

Expansion/launch signals

A company announces new locations, markets, or product lines — the agent connects the expansion to a near-term operational gap it likely creates.

Leadership-change outreach

A new exec joins a target account — the agent opens around the typical priorities a new leader sets in their first quarter, not a generic welcome note.

RESULTS & BENCHMARKS

Time to draft a trigger-based opener

~15 min → ~20 sec

projected (modeled)

Reply rate on personalised sends (IBRAHIM production)

21.8%

real, anonymized

LIVE DEMO

Try it right now

FAQ

Common questions

What counts as a 'trigger event' for this agent?

Any public, timely signal about a prospect — a funding round, a new senior hire, a product launch, an office or market expansion, a leadership change. The more specific the event, the sharper the opener.

Why does it avoid 'congratulations' language?

Because every competitor spotting the same public signal sends a version of the same congratulations line that week — it reads as noise. The agent is prompted to reason to the operational implication instead, which is much harder to copy.

Does this replace researching the trigger myself?

No — you (or a monitoring tool) still need to spot the event. This agent turns a spotted event into a usable, differentiated opener in seconds.

Hammad Yousuf

Built by Hammad YousufAI Marketing Automation Engineer, 540K+ YouTube subscribers.

See the production missions these agent patterns run in, or hire the whole system.