Outbound Sequence Templates, Organized by Trigger

Most teams file their outbound templates by persona or by stage, and then wonder why reply rates stay flat. The problem is that a persona does not tell you why you are reaching out today. A trigger does. When you organize templates by the signal that fired them, the first line of every message can name the specific reason this person is hearing from you right now.

A trigger is any observable event that suggests intent is rising: a new hire in a relevant role, a funding round, a product launch, a competitor mention, a spike in site visits, or a download. Each of these implies a different reason to reach out and a different proof point to lead with. Filing by trigger forces the copy to stay specific. It also makes the library easy to extend, because adding a new signal source simply means adding a new folder.

Build a small set of templates keyed to the highest-signal events. A 'new role' template references the person stepping into the job and the first thing peers in that seat usually fix. A 'funding' template ties the raise to a capacity problem the new budget tends to expose. A 'repeat site visit' template names the exact pages viewed without sounding like surveillance, framing it as relevance rather than tracking. A 'competitor switch' template offers a migration path instead of a generic pitch.

Keep each sequence to three or four touches across two channels, because the trigger has a half-life. A funding round is fresh for a few weeks, a pricing-page visit is fresh for a few days. Set the cadence to match how fast the signal decays, then stop. A sequence that runs for six weeks on a signal that was warm for six days is just noise wearing a template.

Trigger-based outbound only works if every signal resolves to the same account and contact record. If your intent data, your CRM, and your enrichment tools each hold a different version of the truth, you will fire the same sequence twice or contradict an inbound conversation already in flight. One shared identity graph is the substrate. Every signal writes to it, and every channel reads from it before sending.

This is the allbound idea in practice: inbound, outbound, paid, and content all act on one signal layer instead of running as separate silos. When a contact replies to an outbound trigger and then visits the pricing page, the system should suppress the next cold touch and route them as a warm hand-raise. Treat the sequence library like code: version it, observe which triggers convert, and retire the ones that do not earn their place.