Article
Trigger event outbound: the framework | Real Good GTM
realgoodgtm.com
Quoted on this wiki
Every place a page here uses this source, in the order the words come in it.
Channel mix “Email + LinkedIn, sent fast, tied to the change” Detect, qualify, act in the window Speed beats polish
Fast, because triggers decay. Most windows stay useful for a few weeks before the change normalizes and the inbox fills with the same congratulations note from every vendor. For the sharpest events, a new exec or a hard deadline, the first days matter most. Speed beats polish here, so a good message sent early outperforms a perfect one sent late. “Tie it to a specific implication for them, not to a recital of their LinkedIn.” Track the ones that are recent, relevant to your category, and give the buyer a real reason to act now. Job changes and new exec hires reset the buying picture, regulatory deadlines force a decision on a clock, and public LinkedIn or community activity surfaces a stated pain. The right set depends on what your product solves, which is the work behind signal mapping.
The specific play changes with the event, but the shape stays the same: detect it, qualify it against a real need, act inside the window, and reference the change naturally. Here is the generic sequence the specific plays adapt. “Name the change as the reason, tie it to the need it created, one specific ask.” The one rule