Layoff Signal → Poach
A company cuts staff → poach displaced talent, open a BD angle with survivors.
Use when the trigger is "a company is cutting staff." Either a broad sweep ("who laid off in the last 7 days?") or a targeted employer ("Microsoft just announced layoffs — get me the displaced engineers"). A layoff is both a pool of available candidates to poach and a BD opening with the survivors.
Powered by the layoffsignal Hyreflow Native (free public news RSS) → fan into the
standard sourcing pipeline. The native is free (0 credits), no BYOK — natives are exempt
from the waterfall.
Where it runs
The extraction + dedupe + qualification is reasoning done by your own Claude — free. The feed pull itself is free too; credits are spent only on the downstream enrichment of passes only.
Inputs
- Mode:
broad(whole market) ortargeted(one or more named employers). whenwindow: default7d;30dfor a named company.- The client's
ICP.mdfor the qualify gate.
Steps
Sweep the feeds (layoffsignal native — free)
hyreflow tools execute layoffsignal layoff_news --payload '{"when":"7d"}' # broad
hyreflow tools execute layoffsignal layoff_news --payload '{"company":"Microsoft","when":"30d"}' # targetedExtract + dedupe affected employers
Free reasoning over the feed → a clean list of companies cutting staff in the window.
Fan into sourcing
For each employer, source the displaced roles you want (people-first), qualify against the role/ICP, enrich on the candidate channel (personal email + LinkedIn).
(Optional) BD angle with survivors
The same event is a BD opening — switch to the work-email channel for the decision-makers who remain. See Funding → BD for the BD-side mechanics.
Sweep broad, then narrow with the ICP gate before spending any enrichment credit — the feed pull is free, the reveals are not.