Trigger event

Cold outreach fails on relevance far more often than it fails on copy. A message that opens with a reason specific to the recipient's week is answering a question they are already asking themselves; a message that opens with a description of your product is asking them to care on your schedule. The trigger is what supplies the first kind of opening.

It also changes the volume you need. If a reason to write exists for eight accounts this week, eight emails are worth more than four hundred sent to a list where nothing in particular is happening — and they cost your sending domain almost nothing, because the reply rate on relevant mail is what keeps a mailbox healthy in the first place.

The useful ones are public, dated and specific enough that a stranger could verify them. That rules out most of what gets sold as intent and leaves a short, dependable list:

• A job posting for a role that only exists once a problem does — a first sales hire, a first platform engineer, a compliance lead.
• A funding announcement, which changes both the budget and the mandate to spend it.
• A leadership hire in the function you sell to. New leaders replace tools in their first two quarters more often than at any other time.
• A product launch, a new market or a new office — each one implies work that has to be bought or built.
• A public technology change: a stack migration, a new integration, a posted architecture decision.

Reference the event once, in the first line, in the words a human would use — then move immediately to the consequence you can speak to. The failure mode is the email that recites the trigger back in detail and never explains why the sender is writing, which reads as surveillance rather than as relevance.

The second rule is a deadline on the trigger itself. A funding round is a reason to write for about a quarter; a job posting for about as long as it stays open. Working an old trigger is worse than working none, because it advertises that the list was built once and never refreshed.

In SalesShift a trigger is a record, not a note. Every signal in the shared pool carries its type, the source URL it came from and a relevance score you can sort and filter on, and any signal can be pushed straight to a lead or converted into a deal without leaving the feed.