# The Outbound Trigger Reference: What to Watch and When to Move

*You will be able to build a trigger watchlist ranked by buying proximity, know each signal's decay window and false-positive trap, and route every signal to outreach before it goes cold.*

- Canonical URL: https://www.refolk.ai/guides/outbound-trigger-reference
- Pillar: Sales and go-to-market
- Format: Reference
- Published: 2026-07-30
- Last reviewed: 2026-07-30
- Reading time: 17 min
- Keywords: sales trigger events to track, how long do trigger events last, signal based prospecting, buying intent signals b2b, when to reach out after funding round

## Key takeaways

- 85% of B2B purchases go to a vendor already on the buyer's day-one shortlist, so trigger speed is about existing before the shortlist forms, not closing faster.
- A new executive typically reviews existing vendors within their first 90 to 180 days, with the strongest window inside the first 90 days.
- Intent data has a half-life measured in days: weight the last 7 to 14 days and decay anything older than 30, or every account in your database will look in-market.
- 91% of B2B marketers use intent data but only 24% report exceptional ROI, and the gap is decay discipline, not access.
- In Refolk's index there are 17,539 US CMO-buyers versus 4,942 CRO-buyers, so the same executive-change trigger yields roughly 3.5x the reachable surface for a marketing-tool seller.
- Cap Tier 1 at 10 to 15% of your territory; overloading it cuts engagement by more than half.

This is a lookup document for deciding which company signals to build outbound around and how fast to act on each one before it goes cold. It is for founders selling their own product, account executives, SDR leads, and partnerships teams who already know what a trigger is and need to know its shelf life, its proof of intent, and its false-positive trap. Jump to the row you need. You do not have to read it front to back.

Most public trigger content is a wall of "23 events to watch" listicles that name signals and stop there. They never tell you how long a signal stays actionable or how to tell a real one from curiosity. This reference gives every signal a decay window, a statement of what it proves, a warning about when it lies, and the public source that surfaces it.

## Why trigger speed is about existing, not closing

The point of speed is not to close the deal faster. It is to exist in the buyer's mind before the shortlist forms. Corporate Visions found that 85% of B2B purchases go to a vendor already on the buyer's day-one shortlist, and Forrester found that 92% of buyers enter a purchase with a shortlist while 41% enter with a single preferred vendor. If your first touch lands after that shortlist is written, the trigger you chased was decoration.

This reframes what "actionable window" means. It is not the window in which the deal is winnable. It is the window in which you can still influence who gets on the list. A leadership change caught in week one buys a three-month head start over a competitor who waits for the quarterly account review.

**85% - B2B purchases that go to a day-one shortlist vendor**

If your first touch lands after the shortlist forms, the trigger did not help you. Source: Corporate Visions.

Speed-to-lead evidence backs this up. HBR's 2011 study of 2,241 US companies found that firms contacting a lead within an hour were seven times more likely to have a meaningful conversation with a key decision maker than those who waited even one hour longer, and companies that waited 24 hours or more were 60 times less likely to qualify the lead at all. The commonly cited claim that 78% of buyers purchase from the vendor that responds first traces to InsideSales, not HBR, so weight it as a vendor figure. Both point the same direction: latency is expensive.

> Trigger speed is not about closing faster. It is about existing before the shortlist is written.

## The decay window per trigger

Every trigger has a shelf life, and they differ by an order of magnitude. Below is the actionable window and the public source that surfaces each one. Treat the window as the period in which acting on the signal still shapes the buyer's shortlist.

| Trigger | Actionable window | Primary public source |
|---|---|---|
| New executive hire | 90-180 days (act by day 90) | executive-hire monitoring, press |
| Funding round | 45-90 days (some say 72h to 2 weeks) | Crunchbase, funding press |
| Hiring surge | 60-120 days | job boards, career pages |
| M&A / integration | 3-6 months (functions) to 12-18 months | filings, M&A press |
| Category intent (review-site) | days (half-life) | review-site intent |

Two of these need unpacking because the sources disagree.

**Funding.** Some sources say act within 72 hours; a weekly-cadence workflow frames it as a 2 to 6 week window; the most defensible published figure is 45 to 90 days after announcement, when initial hiring is complete but vendor selection is still in progress. Reach out too early and you are interrupting planning and landing in a flood of congratulations. Too late and they have already chosen. If you move early, lead with the problem the round creates, not the round.

**M&A.** No single outreach window is published, because integration itself runs long. Post-merger integration takes 12 to 18 months for mid-market deals from close to full value realisation, though finance, sales, and HR functions typically settle in 3 to 6 months. There is no instant buying window here. The signal tells you a consolidation decision is coming, not that it has arrived.

**Category intent.** This is the fastest-decaying signal you will handle. Intent data has a half-life measured in days, not weeks. The practical rule is to weight the last 7 to 14 days heavily and decay anything older than 30 days to zero.

> **Rule:** Decay everything or trust nothing
>
> Intent data is among the most time-sensitive data types available. If you store historical buying signals without decay logic, every company in your database will soon appear to be showing intent, and your Tier 1 becomes meaningless.

## What each signal proves, and when it lies

A window is half the answer. The other half is what the signal actually proves about buying, and the specific way it misleads. Here is the per-signal breakdown.

**New executive hire.** Proves that someone with budget authority and a mandate to change things has arrived. New executives typically review existing vendors within their first 90 to 180 days. The strong second-hand LinkedIn figure is that 70% of new executives make a technology purchase within their first 100 days, and a vendor claim puts new execs at 5 to 10 times more likely to evaluate new vendors in the first 90 days. **It lies when** the hire is a lateral backfill with no change mandate, or when the exec inherits a vendor a predecessor just signed.

**Funding round.** Proves capital is available and a growth plan exists. **It lies when** you read the round itself as intent. Funded companies are buried in press and outreach in week one, and the round signals only that you are on a list, not that a specific problem is live. The buying happens as the growth plan executes, which is why the 45 to 90 day window beats the 72-hour spray.

**Hiring surge.** Proves a team is scaling and will need tools to support the new headcount. SDR hiring signals sales-tool spend; an engineering surge signals infrastructure spend. The published window between a job posting and a purchase decision is 60 to 120 days. **It lies when** it is a single posting. One req is noise, often a backfill. A meaningful pattern is 3 or more related roles within 30 days, or department growth above 20% quarter-over-quarter.

**M&A.** Proves that two vendor stacks are about to collide and one will win. **It lies when** the deal is announced but integration has not begun, or when an incumbent loyalist inside the customer blocks the logical consolidation. As one source puts it, somebody inside the building is attached to the incumbent, and no amount of combined-company logic moves them in a quarter.

**Category intent (review-site research).** Proves that someone at the account is actively comparing vendors in your category. **It lies constantly.** Not all research activity indicates buying intent. Employees browse for professional development, students research for coursework, journalists investigate for articles. A single content download or topic surge means little on its own.

> **Watch out:** The single-signal trap
>
> A lone job posting, a single content download, or a fresh funding headline is not a signal by itself. Require a pattern (3+ related roles in 30 days) or a second stacked signal before you promote the account. Acting on single events is how Tier 1 fills with noise.

The confirming discipline across all of these is signal stacking: high intent means three or more aligned signals plus high specificity, ideally including first-party engagement. One signal ranks an account. Three signals move it to the front of the queue.

## Grouping signals by buying proximity

Rank every trigger into one of three tiers by how close it sits to a purchase, then attach a response SLA to each tier. This is the dominant public model, and it is the single most useful thing you can standardise across a team.

| Tier | Example signals | SLA |
|---|---|---|
| Tier 1 | pricing-page visit, new exec at pipeline account, demo request | Same day |
| Tier 2 | G2 research, relevant job postings, competitor visits | Within 48 hours |
| Tier 3 | topic surges, single downloads, conference attendance | Review weekly |

The quantified variant of this model does not sort into hard tiers. It builds a living score from ICP fit (40%), buying signals (35%), and engagement data (25%), and updates it as signals fire. Use hard tiers if your team is running manual plays and needs a clear same-day rule; use the composite score if you have the tooling to keep it live.

The discipline that makes tiering work is a cap. Limit Tier 1 to 10 to 15% of your territory. If everything is urgent, nothing is, and overloading Tier 1 cuts engagement by more than half. The evidence that focus pays: the Ebsta and Pavilion 2025 benchmarks, drawn from an analysed 48 billion dollars of pipeline, found the top 14% of sellers generate 80% of revenue. That is what disciplined prioritisation looks like at scale.

#### How trigger volume narrows to a same-day queue

| Stage | Figure | Note |
| --- | --- | --- |
| All monitored signals | 100% | raw feed across all sources |
| Pass velocity threshold | fewer | single events filtered out |
| Tier 1 (capped) | 10-15% | same-day, one owner each |

*Most signals never earn a same-day touch, and that is the point.*

## Sizing the ceiling before you build the watchlist

The size of your buyer persona pool sets the ceiling on how much volume any trigger can ever produce. The same executive-change trigger yields wildly different results depending on which persona you sell to and where. These are counts of current title-holders from Refolk's index, published nowhere else.

| Persona | Country | Current title-holders |
|---|---|---|
| CRO / VP Sales | US | 4,942 |
| CRO / VP Sales | UK | 669 |
| CMO / VP Marketing | US | 17,539 |
| RevOps / Sales Ops | US | 1,566 |

Read these as the reachable surface for an executive-change trigger. A marketing-tool seller working US CMO changes has roughly 3.5 times the reachable executive-change surface of a sales-tool seller (17,539 versus 4,942). A RevOps-tool seller has about a third of the sales-tool seller's pool (1,566). And geography compresses the funnel hard: the US CRO pool is 7.4 times the UK's (4,942 versus 669), so a UK-only watchlist built on executive change needs far more triggers per account, or a wider persona net, to hit the same pipeline.

**17,539 - Current US CMO and VP Marketing buyers in Refolk's index**

About 3.5x the US CRO pool, so the same exec-change trigger produces far more volume for a marketing-tool seller. [OURS]

Once you know the persona pool, you can turn a trigger into a live list. This is where a plain-English search beats a stack of alerts, because you can express the pattern and the persona in one query instead of stitching three tools together.

I ran this search: `New CROs and VPs of Sales who started in the last 60 days at US SaaS companies under 500 employees` - [see the full result list](https://www.refolk.ai/s/w1pxhrtyt4).

*Returns named executives inside their vendor-review window, filtered to your persona, size band, and geography, so the watchlist is populated before day 90 closes.*

Refolk exists for exactly this seam between "a trigger fired" and "here is the named person to reach." Rather than monitoring a source and reverse-engineering who moved, you ask [Refolk](/) for the pattern and the person together.

## The procedure: from signal map to touch inside the window

Run this sequence once to stand up the system, then keep steps five through seven running continuously. It moves from a written signal map to a monitored feed to a logged touch before the window closes.

#### Build and run the trigger watchlist

1. **Define the signal map** - List which public events map to your buying cycle - SDR hiring if you sell sales tools, security hiring if you sell security. Done = a written list of triggers, each with a source and a buyer persona.
2. **Assign a decay window and SLA per trigger** - Attach each trigger to a tier and a hard response deadline. Done = every trigger has a tier, an actionable window, and a review-by date.
3. **Wire up monitoring per source** - Set alerts for news, Sales Navigator for hires and departures, Crunchbase for funding and M&A, review-site intent, and job-board monitoring, aggregated into one feed. Done = signals land in one queue with timestamps.
4. **Set velocity thresholds to kill false positives** - Require patterns, not single events - 3+ related roles in 30 days or 20% QoQ growth. Done = noise filters are live.
5. **Score and route** - Combine ICP fit, buying signals, and first-party engagement into a living score, and route three-or-more-signal accounts to immediate qualification with an AE within 24 hours. Done = each account has a live tier and a named owner.
6. **Act inside the window** - Work Tier 1 same day and Tier 2 within 48 hours, with every message referencing the specific trigger. Done = the touch is logged before the window closes.
7. **Review and reprioritize** - Reprioritize quarterly but monitor continuously, expiring stale signals and applying promotions and demotions. Done = stale signals are expired and the tier map is current.

On step ordering, sources disagree. One school works explicit inbound first, then multi-signal accounts, then single high-tier signals. Another routes purely by a fit-plus-signal composite score. Both agree on one thing: multi-signal accounts jump the queue. If you take nothing else from the ordering debate, take that.

#### A signal's path from source to logged touch

1. **Event fires** - an exec moves, a round closes, a surge begins
2. **Alert lands** - source refreshes and the signal enters your queue with a timestamp
3. **Filter and score** - velocity thresholds drop noise, remaining accounts get a tier
4. **Route to owner** - multi-signal accounts jump the queue to an AE
5. **Touch inside window** - message references the specific trigger before the window closes

*The clock starts at the event, not at the alert, so measure event-to-touch latency end to end.*

## Refresh cadence is not freshness

The most expensive mistake in this whole system is trusting a vendor's refresh cadence as a proxy for how fresh your signals are. They are different numbers, and they can differ by weeks. A source that refreshes its database daily can still hand you an event that happened three weeks ago, after a competitor already called.

Published cadences vary widely. Some intent scores and buyer-intent feeds refresh daily, some topic-level surge feeds refresh weekly, some contact-tracking tools refresh every 2 to 4 weeks, and several large contact databases show practical refresh cycles of 90 to 180 days. G2 Buyer Intent, for example, pulls research activity from G2, Capterra, Software Advice, and GetApp, and in some integrations refreshes every 24 hours. None of that tells you how long it took the event to reach you.

> **Watch out:** Ask for event-to-alert latency, not refresh rate
>
> A "daily refresh" describes how often the database is rewritten, not how quickly a real-world event becomes an alert on your screen. Demand the latency number. If a vendor cannot give it, treat their freshness claim as unproven and verify it against a source you can date, such as a press release or a filing.

This gap explains a striking pair of numbers: 91% of B2B marketers use intent data, but only 24% report exceptional ROI. The bottleneck is not access. Everyone has the data. The difference is whether the team decays it and acts inside the latency. Undecayed, stale data makes every account look hot and pushes noise into Tier 1.

## How this goes wrong

The failure modes below are the reason a trigger system produces either pipeline or busywork. Each is a specific way the method breaks, with a check that catches it.

- **Stored signals never expire.** Without decay logic, every account looks in-market. Check: enforce a review-by date per trigger and expire on schedule.
- **A single job post read as a surge.** One backfill req is not a hiring signal. Check: require 3 or more related roles in 30 days, or 20% quarter-over-quarter department growth.
- **Intent mistaken for buying.** Employees, students, and journalists all browse category content. Check: require an intensity spike plus ICP fit plus a second stacked signal before promoting the account.
- **The "congrats on the funding" spray.** It signals you are on a list, and funded execs are buried in press in week one. Check: lead with the problem the round creates, not the round.
- **M&A treated as an instant buying window.** The deal is announced but integration has not started, and an incumbent loyalist blocks the logical move. Check: confirm a named relationship and a real consolidation reason before pitching.
- **Refresh cadence mistaken for freshness.** A daily refresh can still deliver a weeks-old event. Check: demand event-to-alert latency, not database refresh rate.
- **Tier 1 overloaded.** If everything is urgent, nothing is, and engagement collapses. Check: cap Tier 1 at 10 to 15% of territory.
- **You are already too late.** With 85% of deals going to the day-one shortlist, closing before the deadline is not the bar. Check: measure whether your first touch lands before shortlist formation, not just before close.

The single most valuable of these is the last one, because it changes what you measure. Most teams measure response time against the deal timeline. The right measure is whether you touched the account before its shortlist formed, which is usually far earlier than the deal shows up in any pipeline report.

## Keep the watchlist current

A trigger watchlist rots faster than any other list you own, because its entire value is time-sensitivity. Treat maintenance as part of the system, not an afterthought. The cadence that works is continuous monitoring with a quarterly reprioritisation: reps who catch a leadership change in week one hold a three-month head start over those who wait for the quarterly refresh, so the monitoring cannot wait for the review.

Before you call the system done, run this check.

#### Trigger watchlist readiness

- [ ] Every trigger has a named public source and a buyer persona attached.
- [ ] Every trigger has an actionable window and a review-by date after which it expires automatically.
- [ ] Velocity thresholds are live, so single job posts and lone downloads never reach Tier 1.
- [ ] Tier 1 is capped at 10-15% of territory and each Tier 1 account has one named owner.
- [ ] You track event-to-alert latency per source, not just each source's refresh cadence.
- [ ] Intent signals older than 30 days are decayed to zero, with the last 7-14 days weighted most.
- [ ] Multi-signal accounts (three or more aligned signals) are configured to jump the queue.
- [ ] Your first-touch metric measures whether the touch lands before shortlist formation, not before close.

**Trigger-referenced first touch (hiring surge)**

```
Subject: the 4 AE reqs you posted this month

Hi [first name],

Saw your team opened four account-executive roles in the last three weeks. When sales headcount jumps that fast, ramp time and territory coverage usually break before the tooling catches up.

That is the specific gap I help teams close in the 60-to-120-day window between hiring and the tools landing. Worth 15 minutes to compare notes on how you are planning to onboard the new cohort?

[your name]
```

*Swap the role and the specific pattern for the real one you saw. Never send this without a concrete, dated observation in the first line.*

Two maintenance rules keep the whole thing honest over time. First, re-check any freshness claim you depend on by dating a signal against a source you can verify, such as a filing or a press release, rather than trusting a refresh label. Second, size your persona pool before you expand into a new geography or ICP, because the ceiling changes: a watchlist that works against 4,942 US CRO-buyers will starve against 669 in the UK unless you widen the persona net or add triggers per account. Both numbers come from Refolk's index and are the kind of ceiling you want to know before you commit a quarter to a trigger that cannot produce the volume you need.

## Frequently asked questions

### How long do trigger events last before they go cold?

It varies sharply by trigger. A new executive hire stays actionable for 90 to 180 days, with the strongest window inside the first 90. A funding round has an optimal outreach window of 45 to 90 days after the announcement. A hiring surge maps to a 60 to 120 day purchase window. Category intent from review sites has a half-life measured in days, so weight the last 7 to 14 days and decay anything older than 30.

### When should I reach out after a company raises a funding round?

The published optimal window is 45 to 90 days after the announcement, when initial hiring is done but vendor selection is still in progress. Reach out in week one and you interrupt planning and land on the same congratulatory list as everyone else. Wait too long and vendors are already chosen. If you do move early, lead with the problem the round creates, not the round itself.

### How do I tell a real buying signal from noise?

Require a pattern and stack signals. A single job posting is noise; a meaningful hiring pattern is 3 or more related roles within 30 days or 20% quarter-over-quarter department growth. Intent research alone is ambiguous because employees, students, and journalists all browse category content, so require an intensity spike plus ICP fit plus a second signal before you treat it as intent.

### Does a new executive really trigger vendor decisions?

Yes, though the load-bearing numbers vary in strength. New executives typically review existing vendors within their first 90 to 180 days. A widely repeated but second-hand LinkedIn figure puts 70% of new executives making a technology purchase within their first 100 days, and a vendor claim says new execs are 5 to 10 times more likely to evaluate new vendors in the first 90 days. Treat the 90-day window as the reliable part.

### How fast do I actually need to respond to an inbound signal?

Fast. HBR's 2011 study of 2,241 US companies found that contacting a lead within an hour made a firm seven times more likely to have a meaningful conversation with a decision maker, while waiting 24 hours or more made them 60 times less likely to qualify the lead. A separate figure holds that 78% of buyers purchase from the vendor that responds first.

### Why does my intent data make every account look in-market?

Because stored signals never decay unless you make them. Intent is among the most time-sensitive data types available, and if you keep historical buying signals without decay logic, your whole database eventually appears to be showing intent. Enforce a review-by date per trigger and expire signals on schedule. This is why adoption is near-universal (91% of marketers) but only 24% report exceptional ROI: the gap is decay discipline, not access.

---

*From the Refolk guide library. I revise these guides rather than replacing them, so the current version is always at https://www.refolk.ai/guides/outbound-trigger-reference*