All Walegold recipes
Recipe11 chapters

The Trigger

Reaching companies the week something actually changed

Account-based prospecting off an entity-resolved news feed: every company arrives already carrying the article that surfaced it — a funding round, a layoff, an expansion. The play is to let the event decide both the timing and the message, and to keep the internal-pain signal for the accounts where it changes the pitch entirely.

01The target

Who the campaign is aimed at

Companies with a fresh, dated trigger event. Not a static list of accounts that fit on paper — accounts where something changed this month that gives you a reason to write.

The signal
A funding round, a layoff or an expansion — with the article attached
Freshness
A self-renewing feed, filtered on the last few days
Pain signal
Weak employee-review ratings, on demand
Contact
The exec the event makes reachable
02The two profiles

The segments it splits into

A

Growth trigger

Just raised, just expanded, just opened a market. The budget landed this quarter, they're hiring against it, and the conversation is about spending the new money well.

B

Pain trigger

Layoffs in the feed, and weak employee-review ratings underneath. The trigger is internal strain — retention, culture, management load — and the conversation is about the thing that's actually hurting.

03Pull the news feed

Start from the event, not the org chart

The feed is filtered on what matters: topic, industry, event type, sentiment, country and article quality. Each company lands with the article that surfaced it, so the reason to reach out arrives attached — you are never guessing why this account, this week.

The filter that changes everything is time. Pulling on a rolling last-few-days window instead of a fixed start date turns the source into a feed that renews itself: the same query reruns and only ever hands over what's newly true.

04Resolve the industry first

Free text is not an industry code

The feed filters on industry codes, not on the loose phrase you have in your head. The free resolver turns "fintech" or "logistics software" into the codes the source actually understands, and it costs nothing to run.

Doing it first is the cheap-before-expensive rule again: resolve the codes, then pull, and every credit spent downstream is spent on companies that were in the right industry to begin with.

05Dedupe and keep the primary

One company, not one per headline

A single funding round is written up by a dozen outlets. Left alone, that is a dozen rows for one company and a pipeline that looks bigger than it is. Grouping articles and keeping only the primary mention collapses the noise back into accounts.

It also protects the numbers. A funnel built on article counts flatters itself; a funnel built on deduped companies tells the truth about how many real accounts the event actually produced.

06Read the event

Funding or layoffs, opposite conversations

This is the read the whole recipe turns on. A funding round or an expansion points one way — new budget, hiring, momentum to spend well. A layoff, especially with a run of weak reviews behind it, points the other — strain, retention risk, a team doing more with fewer people.

Same feed, same industry, completely different account. The event is not a tag to file; it is the decision about which of the two campaigns this company belongs to.

07Gate hard, then read the reviews

The expensive verb, run last and rarely

Aggregated employee-review ratings turn a layoff headline into a real internal-pain verdict — weak, strong or none against your threshold. It is by far the most expensive check in the block, so it runs only on the Profile B shortlist that already has a layoff or a strain signal, never on the whole feed.

A weak rating is the trigger when you sell anything that touches retention, culture or management load. Gate it hard: the point is to spend the credit on the accounts where the answer changes what you write, not to score everyone.

The trap

It is tempting to run the review check on the whole pull "to be thorough". Don't — at its price a broad sweep burns the budget before you reach the accounts that matter. The signal is only worth buying once the event already says the pain is plausible.

08Sort into Profile A or B

One event, two pitches

The growth trigger gets the spend-it-well conversation: the new budget, the hiring, the thing they can now afford to fix. The pain trigger gets the strain conversation: what the layoffs and the ratings say out loud, and the offer that speaks to it directly.

Cross the wires and the email is worse than ignored. Congratulate a company on momentum the week it cut a third of its team and the trigger you were so proud of finding is the reason you get blocked.

09Reject the bad fits

Say no to stale and off-target

An explicit gate: out go events too old to be a reason to write, companies whose article turned out to be about a namesake, and accounts whose only trigger is a topic you don't actually sell into.

The discards are read, not dumped. If a whole event type keeps importing off-target companies, that's a filter to tighten on the feed pull, not a recurring cleanup downstream.

10Find the contact

The person the event makes reachable

Only now is a human attached, and the event decides who. A funding round makes the founder or a new VP the natural recipient; a layoff and weak reviews point at whoever owns people and retention. The trigger is not just the reason to write — it is the map to the right inbox.

As everywhere in this catalogue, the person is last because they're the most expensive to find. The shortlist that reaches this step has already survived a fresh event, a clean dedupe and a matching profile.

11The funnel

Where the list thins out

Worked example — modelled figures

The numbers below are a worked example, not a single run: one month of a filtered news feed put through the seven qualification steps. The ratios are the argument — and the number to watch is the dedupe, where a headline count becomes an account count.

StageInKeptSurvival
News feed pull5,2005,200100%
Deduped to companies5,2001,90037%
Event readable1,9001,34071%
Profile A / B1,3401,04078%
ICP match1,04069066%
Contact found69056081%
News feed pull
100%
Deduped to companies
37%
Event readable
71%
Profile A / B
78%
ICP match
66%
Contact found
81%
What a raw feed gives you
5,200
articles to sift
What the recipe hands over
560
accounts with a reason and a name

The gap is the dedupe and the read: five thousand headlines are not five thousand accounts, and an event you can't act on is not a trigger. Run monthly on a rolling window and the pipeline never empties — the news keeps producing reasons to write, and you keep being the one who writes the week it matters.

Want to run this play on your market?

Every Walegold recipe is built and run on Walego — the sourcing, the enrichment, the profiling and the founder hunt. Bring your ICP and we'll build yours.

Try Walego