Outbound Wiki

Article

Trigger event outbound: the framework | Real Good GTM

realgoodgtm.com

Open at publisher

Quoted on this wiki

Every place a page here uses this source, in the order the words come in it.

  1. 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

    In Trigger-based cold call openers

  2. Reference the event as the reason you are reaching out now, then move straight to the need it creates. Tie it to a specific implication for them, not to a recital of their LinkedIn. A creepy "I saw that you..." lists what you found. A useful opener names the change and the problem it just put on their desk, then offers something concrete. The event is the context, never the whole pitch. “Track the ones that are recent, relevant to your category, and give the buyer a real reason to act now.” This page is the framework, the way to think about acting on any timely event. A specific play, like champion tracking, is one motion off one trigger, run end to end. You use the framework to decide whether an event is worth chasing and how to respond, then you run the matching play to actually do it. The framework points to the plays, it does not replace them.

    In Buying signals and triggers

Quotes are verbatim and belong to their publishers. Where a quote has been translated, the original wording is kept below it.