Outreach on a detected company event — funding round, hiring spree, leadership change, product launch, expansion. The strongest hooks available, and the most ritualized failure mode in cold outreach ("congrats on the round, here's my pitch").
Not for conference or webinar follow-up — that's a different motion (attended events create a shared-context hook, not a company signal).
The angle
The event is public; everyone selling to this company saw it. And "congrats on the funding" is now a recognized automation tell — mature orgs ban new-job and funding congratulations as openers outright. The edge is inference: name the consequence the event creates, not the event. "Noticed the expansion into DACH" is weaker than "expansion into DACH usually means the compliance stack gets rebuilt within two quarters."
Do
- Map event → operational consequence, and lead with the consequence. Funding → a plan the money must deliver, and pressure on whatever was already slow. Exec hire → a 90-day agenda and no loyalty to current vendors. Hiring spree → capacity landing before process. Launch → a team newly accountable for adoption.
- Verify the signal before using it — two independent sources for anything inferred. A signal that fails verification gets dropped, not hedged.
- Target the person who owns the consequence — often not the person in the news. The new VP is drowning in congratulations; the director inheriting the agenda reads their inbox.
- Respect recency: under two weeks is a hook; past six weeks find what the event has since caused, or drop it.
- Make the proof a peer that went through the same event, not a generic customer win.
- Calibrate the event: one job post is not a hiring spree; three-plus roles on the same team is.
Don't
- Don't congratulate. At most one clause of acknowledgment; the message is about the consequence.
- Don't open with "I noticed" or "I saw that" — state the observation directly, or skip to its implication.
- Don't stack events. A company that raised, hired, and launched gets one consequence — the sharpest.
- Don't recycle the same event-template across a list; the market hears every "congrats on the Series B" template within a quarter.
- Don't use an event as a costume for a pitch that was going out anyway — if the consequence doesn't connect to what the org actually solves, the signal isn't a hook.
Sequence shape
Placeholder until this org sets its own:
| Step | Day | Channel |
|---|---|---|
| 1 | 0 | email — consequence-led opener + peer proof + one ask |
| 2 | 3 | email — second-order consequence, shorter |
| 3 | 8 | LinkedIn DM — lighter angle |
| 4 | 14 | soft close |
This org's rules
Nothing recorded yet. When the user gives feedback on signal outreach in conversation, write it here per event type: the consequence framing that works, who to target, retired framings and why. Rules only — approved copy accumulates automatically as message examples.