The Company Trigger-Event Reference: Proof and Shelf Life

This is a lookup table for anyone deciding which company-level trigger events are worth building outbound around, and for how long each one stays worth acting on. It is written for founders selling their own product, account executives, SDR leads, and partnerships teams. Jump to the row you need: each trigger gets what it proves, where to detect it from public sources, how long the window lasts, and the false positive that burns reps.

A trigger event is a dated change at a target company that implies a new need: a funding round, a new executive, a hiring surge, a departure, a renewal date approaching. The problem is not finding triggers. It is knowing which ones prove buying readiness, which only imply it, and how many days each stays actionable before the window closes. That is what the rows below answer.

What a trigger event proves versus what it only implies

A trigger event proves a change happened; it rarely proves a purchase will follow. The discipline is separating proof from implication per trigger, because the two decay at different rates and lie in different ways.

Funding proves budget exists. After a round, B2B spending increases 40 to 60% in the two quarters that follow, with the sharpest spike in the first 90 days. That is a strong proof of capacity. It does not prove the new budget is pointed at your category, and it is visible to every competitor at once, which is a separate problem covered below.

A new executive hire implies a stack rebuild. New leaders tend to reassess vendors in their first months, but no measured conversion share for "percent of new VPs who reassess vendors" is established publicly. Sources assert the behavior qualitatively and publish no number, so treat it as a strong implication, not a proof.

A hiring surge proves budget was approved for headcount. It is one of the few triggers where the company has already spent money to signal. That strength is also its weakness, because the same visibility that makes it readable makes it easy to fake.

Only about 3% of a market is actively buying at any time, with another 7% intending to change soon. Triggers are a way to find the 3% plus 7% without guessing. But a trigger that proves budget (funding, hiring surge) is worth more than one that merely implies receptivity (a new hire), and you should weight your queue accordingly.

The outreach window by trigger: how long each stays actionable

Each trigger has a decay window after which the implied need has been met, the buyer has moved on, or the noise has saturated. The table below gives the window quoted by named sources, so you can look up a trigger and know the clock.

Sources disagree on executive hires in particular, and the disagreement is informative. One source sets a 24 to 48 hour response window for a VP hire but describes a 90-day period in which new leaders rebuild the tech stack. Another puts the useful window at 30 to 60 days after the start date, because the leader needs time to assess before buying. A third says 2 to 4 weeks, a fourth 2 to 12 weeks post-start. The spread tells you the real answer: the window opens at the start date and the buyer is most receptive somewhere in the first two months, not on day one.

Two windows run backwards from a future date rather than forward from a past one. Contract renewal is actionable 60 to 90 days before the renewal date, which means you have to know the date to use it. A key departure has the shortest forward window at 1 to 4 weeks, because the vacancy either gets filled or the work gets reassigned fast.

The two-week figure from Craig Elias, who originated Trigger Event Selling, is the reason most windows cluster around two to eight weeks. He was named the number one salesperson within six months of joining WorldCom on this method. Treat the 74% as a hypothesis to test, not a published fact.

Where to detect each trigger, and its refresh lag

The public source you read determines how fresh your signal is, and the best source is rarely the fastest. The table below pairs each trigger with a free public source and the lag that source carries, so you know how old a "new" signal really is before you act.

Form D is the single most valuable detection source in this guide. US companies file it within 15 days of the first sale of securities, and it appears on EDGAR weeks or months before press, LinkedIn, or Crunchbase. That gives a 2 to 6 week head start precisely while competitors still see nothing. The edge is structural, not effort-based: you are reading a legally forced disclosure, not racing to a news feed everyone else watches.

Hiring has a split you must respect. Job boards are near real-time but noisy, proving only that a posting exists. LinkedIn headcount is the most reliable picture of actual hiring but carries a 30 to 60 day lag. So if you detect a "new" executive from headcount, the person may already be a month or two into the job, meaning much of the 30 to 60 day assessment window has already elapsed. The highest-value triggers often have the longest detection lag, which inverts the "act in minutes" rule.

Layoffs are the structurally blind spot. Mass-layoff WARN notices account for only about 1 to 6 percent of total layoffs, and BLS JOLTS lands with a lag of several weeks. A cost-cutting trigger built on public filings will miss the vast majority of real events. The signal exists; it is just undetectable from the obvious source.

Detecting the event is half the job. Finding the named person who moved, inside the window, is the other half, and it is where the headcount lag hurts most. Refolk reads start dates and current titles across public LinkedIn and the open web, so you can ask for the people a trigger implies rather than scraping a board and guessing who the posting is for. Refolk's index returns the person, not just the company, which is what lets you verify the buyer is still in seat before you send.

How many people each trigger actually addresses

Pool scarcity should set trigger priority, because a trigger that addresses a small universe needs a far higher per-signal conversion to be worth equal effort. The counts below come from Refolk's index and tell you how large the addressable pool is for three common trigger-relevant roles.

In Refolk's index, the CTO and VP of Engineering leadership pool is 38,066 US people, which is the addressable universe for a "new technical exec" trigger. The Terraform engineer pool, a proxy for a tech-stack-change trigger, is only 3,889 US people, roughly one-tenth the size.

The 7.0x multiple between the CTO pool and the VP of Marketing pool is not a clean comparison, because the VP of Marketing count of 5,427 spans both the US and UK while the CTO count is US only. The 9.8x ratio against the Terraform pool is a clean single-geography comparison and is the one to trust. The practical read: a narrow-role trigger is not worse, but it demands a sharper angle and a higher reply rate per signal because there are fewer shots.

The procedure: from trigger set to measured lift

Build the pipeline once and it runs continuously. The steps below take you from deciding which triggers to watch through measuring whether they beat your cold baseline. Each step has a clear "done" condition so you know when to move on.

There is a real order disagreement baked into step seven. Speed-to-lead literature treats speed as paramount: 35 to 50% of sales go to the vendor that responds first, which argues for acting in hours. But trigger-event authors argue certain triggers need a 30 to 90 day assessment runway before the buyer is receptive. Fastest is not always best timed. Match the clock to the trigger: act in hours on a hiring surge, but pace a new-executive touch across their first two months.

Subject: [specific function] rebuild after [dated event]

Saw [company] filed its round [N] weeks ago and is now hiring [N] [function] roles. That pairing usually means [the specific problem your product solves] moves up the list in the first quarter.

One question: is [named buyer] owning [the decision area], or is that still being assigned?

Happy to share what [comparable company] did in the same window if useful.

How this goes wrong: the false positives that burn reps

Most trigger-event failures are not bad timing; they are trusting a signal that lied. Below are the documented false-positive patterns and the specific check that catches each one. This is the section to read before you build, because a clean filter is worth more than a faster feed.

Ghost jobs. A hiring surge can be talent-hoarding, not budgeted demand. In a 2024 survey, 40% of hiring managers said their company posted a fake job in the past year, and one analysis found 21% of postings meet ghost-job criteria, with one in five resulting in no hiring whatsoever. JOLTS shows US job openings have exceeded actual hires by over 2.2 million per month since early 2024. The check is concentration: five openings in one team at a 60-person company is a capacity gap; fifty across a 2,000-person company is a headcount plan. Also check reposting age, because a job reposted for months is not fresh demand.

Stale contacts. The trigger is real but the named buyer already left, so the email bounces. The documented case is an email to a new VP bouncing because the contact data is three months old and the VP left six weeks ago. The check is non-negotiable: re-verify the current title before you send.

Message saturation. Funding is visible to everyone at once, so its proof value is high but its differentiation value collapses. The check is a hard requirement for a differentiated, non-congratulatory angle before any funding-triggered message goes out.

Layoff under-detection. Relying on WARN misses 94 to 99% of events, since WARN captures only 1 to 6 percent of total layoffs. The check is to cross-reference hiring-freeze and backfill signals rather than WARN alone.

Detection-lag false freshness. LinkedIn headcount is 30 to 60 days old, so a "new" hire may already be past the assessment window. The check is to date-stamp from the announced start date, not the date you detected the headcount change.

Window-math error. Treating the detection date as the event date inflates remaining days and sends you after windows that have already closed. The check is to compute from the event date, such as the Form D dateOfFirstSale, not the detected date.

Backfill versus net-new confusion. A posting may be a replacement, not expansion, which changes what it proves. The check is to compare against the headcount trend before calling a posting growth.

Over-trusting vendor lift claims. The 3 to 5x reply-rate lift and the 74% win-odds figure are self-reported by interested parties. One funding-method table shows a 15 to 25% reply rate versus 3 to 15% for traditional prospecting, which is directional but still vendor-sourced. The check is to benchmark against your own cold control group before quoting any of these numbers internally.

The best public signal is the most degraded by abuse, so your filter matters more than your feed.

Keeping the reference current

Trigger windows and detection lags shift as sources change behavior, so re-check the mechanism, not the number. Below is what to verify before you call your queue clean, and how to keep it honest over time.

The windows in this guide are source-quoted, not laws of nature. Re-check them the way you would re-check any benchmark: run a per-trigger reply rate against your own cold control monthly, and when a window stops beating cold, shorten it or drop the trigger. Your own control group is the only lift number you can defend.

Detection lags move too. Form D's 15-day rule is statutory and stable, but LinkedIn headcount lag and job-board noise shift with platform changes and labor-market conditions. The way to stay current is to measure the gap between your event dates and detection dates per source, and watch whether it drifts.

One last structural point to internalize. Over 16,000 US venture rounds closed in a recent year per NVCA data, and Crunchbase captures only roughly 60 to 70% of US rounds. If you source funding triggers from press alone, you are blind to a third of the market and six weeks late on the rest. Reading Form D on EDGAR directly fixes both problems at once, which is why it belongs at the top of your detection stack rather than as a backup to the news feed everyone else refreshes.

Start with the two triggers that prove budget, funding and hiring surges, wire Form D and concentration-checked job data as their sources, and only add the implication-based triggers once your control group shows they beat cold. A short, well-filtered trigger set that you measure will outperform a long list you trust on faith.