Fit tells you an account could buy. A trigger tells you they might buy now. Most teams have the first and call it the second.
The two-part test
A signal earns a place in the workflow only if you can answer both:
- What does a rep do differently because of it? Not "prioritise". A
specific different action: call today rather than sequence, open with this angle, work this contact instead of that one.
- How long does it stay live? Every signal decays. If nobody has set the
window, reps will work month-old triggers as though they were fresh, and the message will land as obviously stale.
Signals that fail either test are a subscription to a dashboard.
The triggers that hold up
Roughly in order of how reliably they convert into a conversation.
A job posting for a role your product touches. Public, dated, and it names a problem the company has already budgeted to solve. A posting for two SDRs says the pipeline target went up. Window: weeks, until it is filled.
A leadership hire in the function you sell to. New leaders review vendors, change process, and want early wins. Window: a quarter, and the first month is the strongest part of it.
Funding. Widely used, which is the drawback: everyone sees it the same day and the inbox reflects that. Still real, because it precedes hiring and tooling. Window: a quarter, but the first week is crowded.
A technology change. They adopted something you integrate with, or dropped something you replace. High precision when detectable. Window: months.
A competitor mention or a public complaint. Rare and strong. Window: days.
Expansion signals, such as a new office, a new market, or a new product line. Slower burn, better for account narrative than for urgency.
The trigger most teams overweight
Generic intent data: an account is reading about your category.
It is not worthless, but it is a prioritisation input rather than a reason to call. It says someone at a company read something, not that anyone is buying, and often not even which team. Treat it as a tiebreaker on an account that already fits, never as an entry criterion on its own.
The test again: if nobody can name what the rep does differently on a spike, it is not a trigger.
Set the decay window explicitly
Write it per signal type. It takes an hour and it changes what gets worked.
| Signal | Live for |
|---|---|
| Competitor complaint | Days |
| Funding | A quarter, best in week one |
| Leadership hire | A quarter, best in month one |
| Job posting | Until filled |
| Technology change | Months |
| Generic intent spike | Days, as a tiebreaker only |
Then enforce it: an account whose trigger has expired goes back to the fit list, not the working list. This is the same discipline as the exhaustion exit in cadence design, and it fails for the same reason, which is that nobody wants to remove things.
Stacking beats any single signal
One trigger is a reason. Two unrelated triggers on the same account inside a window is a much stronger reason, and it is the cheapest scoring improvement available: a hiring post plus a leadership hire in the same function is a different account from either alone.
Do not build a weighted model first. Start by counting distinct live triggers per account and sorting by that.
Using it in the message
A trigger in the first line is the whole point, and it is also where teams waste it. Two failures:
- Naming the trigger without the consequence. "I saw you raised a Series
B" tells them what they already know. "I saw you raised a Series B and posted two SDR roles, which usually means the pipeline number moved before the team did" says something about them.
- Using a trigger the whole market can see, with no angle. Funding
announcements produce a wave of identical emails. If that is your only signal, differentiate on the consequence, not the observation.
Related: the first ten seconds of a cold call and the sales development process, where signal is stage two.
Where this sits
This is the Signal pillar of the Tenbound Pipeline Architecture Standard, and it is the pillar teams skip most often. Skipping it is why an engagement layer produces volume without meetings: the sequences run fine, they are just aimed at accounts with no reason to care this week.