← all playbooks

Reach displaced talent in the week the layoff lands

The layoff events in your market this week, the people affected who match what you recruit, and personal contact details for them, with the surviving employer flagged as a business-development opening too.

use when
a company in your market has announced redundancies and there is a short window before everyone else calls
starts from
Just your niche

The prompt

Paste it into Claude Code or the Claude desktop app with Hyreflow connected. The first line tells your agent to use Hyreflow, so it reads the play, asks before it spends anything, and hands the work back to you.

paste this into Claude
Use hyreflow and sweep the layoff news from the last <DAYS> days, then show me
what happened in <INDUSTRY_OR_MARKET>.

For each event, give me the company, roughly how many people, which
functions were hit, where, and the source. Do not invent a headcount. If
the article says hundreds, say hundreds.

Then, for <COMPANY> specifically:
- Find the people who were in <FUNCTION_OR_DISCIPLINE> there.
- Qualify them against <ROLE_OR_BRIEF>.
- Get me personal email and LinkedIn only. These people are being
  approached about a new job, so a work address at the company that just
  cut them is worse than useless.

Also tell me whether the surviving company is worth a business-development
approach, and who I would write to.

Draft the outreach. Keep it human, these people have just had a bad week.
Do not send anything.

Replace every <PLACEHOLDER> with your own detail. Everything else can stay as written.

What you need first

  • Nothing, for the sweep itself, which is free
  • A Hyreflow workspace with credits for sourcing and contact details
  • A sequencer, if you want to work the list rather than just hold it

Tools it can reach for

The agent picks per step from what your workspace has. Nothing here is required by name.

What happens when you run it

Free steps are marked free. Anything that spends credits is marked, and the agent asks before the first paid run of any size.

  1. 1

    Sweep the layoff news

    free

    Public reporting is swept for redundancy announcements across a window you set, either broadly across the market or targeted at named employers. This step is free.

  2. 2

    Read the actual articles

    credits

    Headlines carry almost nothing. The full article body is fetched so the numbers, functions and locations come from the reporting rather than from a guess.

  3. 3

    Extract the facts

    free

    Company, headcount, percentage, date, location and which functions were affected, with the source attributed. Where reporting is vague, the vague wording is kept rather than sharpened into a false precision.

  4. 4

    Collapse duplicate coverage

    free

    One layoff generates a dozen articles. They are collapsed into a single event keyed on the company and the date, keeping the most specific reporting and the best source.

  5. 5

    Source the affected people

    credits

    For engineering functions, public developer profiles are a free and accurate starting point. For everyone else, a company-scoped people search finds those in the affected function.

  6. 6

    Find personal contact details only

    credits

    Personal email and LinkedIn, through the providers that actually carry personal addresses. Never work email: you are approaching them about leaving, and that inbox is often already switched off.

  7. 7

    Draft outreach, and flag the business-development side

    free

    Approach copy written for people who have just had bad news, plus the other half of the signal: the company that made the cuts is often restructuring and hiring elsewhere, which is a conversation worth having.

What a run costs

Credits are spent per candidate the play actually works, and a lookup that finds nothing usually costs nothing. The two figures are the run where the first provider answers and the run where every lookup walks its full chain.

candidatesif the first provider answersif every lookup walks the chain
25$3.535 credits$10100 credits
100$14140 credits$41410 credits
500$70700 credits$2052050 credits
1,000$1401400 credits$4104100 credits

Free before anything is charged

  • Sweep the layoff news
  • Extract the facts
  • Collapse duplicate coverage
  • Draft outreach, and flag the business-development side

What moves the number

  • The channel. This play buys personal email, because these are candidates, and a work inbox is the wrong place to approach one. A personal address costs more to find than a work one.
  • Coverage on people search and personal email. The chain stops at the first provider that answers, and only that provider bills.
  • How many candidates survive the free filters. Everything dropped before the paid steps costs nothing.
  • Providers you connect with your own key. Those calls bill your account, not your credits.

An estimate, not a quote, priced at the volume credit rate. Your agent sizes the run against your own workspace and tells you what it will cost before it spends anything.

Two opportunities in one announcement

A layoff is usually read as a candidate event. A group of people who fit your market became available on the same day, and there is a genuine window before every other recruiter gets to them.

The second half gets missed. A company that cuts one function is very often hiring in another, because most layoffs are restructuring rather than collapse. The survivors have more work and fewer people. That is a business-development conversation, and almost nobody makes it, because everyone is looking at the leavers.

This play produces both from the same signal.

What you get back

A table of layoff events: company, scale in the words the reporting used, functions, location, date and source. For the events you choose to work: the affected people who match your brief, with personal email and LinkedIn. And the other side, whether the employer is worth approaching and who to write to.

Tone is the whole game

Everything in this play is mechanically easy. The part that decides whether it works is the message.

Do not open with sympathy theatre. Do not pretend you found them by coincidence. Acknowledge the situation in a clause, not a paragraph, then be specific about what you have and why you thought of them. People in this position read a lot of messages that week, and the specific ones are the ones they answer.

Attribution matters

The sweep surfaces facts from public reporting. Attribute the publisher when you refer to the news, and do not reproduce article text or pass a compiled feed off as your own dataset. It is a trigger for your work, not a product.

Where this goes wrong

Waiting. The window is days. A sweep you run monthly will find events everybody already worked.

Volume over relevance. Two hundred displaced people is not two hundred candidates. Qualify against a real brief first, which is free, then spend on contact details for the ones you would actually put forward.

Assuming an automated sweep catches everything. Public reporting is incomplete and inconsistent, and smaller redundancies frequently go unreported. Widen the window when it matters, and treat the sweep as a strong signal rather than a complete record.

Questions

Is this not a bit vulture-like?

It depends entirely on how you do it. Someone who has just been made redundant is looking for work and would rather hear from a recruiter with a relevant role than not. What makes it grim is a templated message that clearly went to four hundred people, or an approach that pretends not to know what happened. Acknowledge it briefly, be useful, and be specific about what you actually have.

Why is the news sweep free but reading the articles is not?

The sweep reads public feeds, which costs nothing. Getting the full text of an article means fetching and rendering the page, which is a real operation and is charged for. In practice you sweep broadly for free, decide which two or three events matter to you, and only pay to read those.

The headcounts in the news are vague. Does that matter?

Not much, and the play deliberately does not fix it. Reporting says hundreds when it does not know, and turning that into a precise number would be inventing data you might repeat to a client. Keep the source's wording. What actually matters for sourcing is which functions and which site, and that is usually stated more precisely.

Why not use their work email while it still works?

Because it usually does not, and because it is the wrong channel. Post-announcement, corporate inboxes get locked down early and are monitored where they are not. Personal email and LinkedIn are where these conversations belong, and they are the channels people actually check while they are between roles.

Can I run this as a standing weekly sweep?

Yes. The free half in particular is well suited to running on a schedule: a weekly digest of what happened in your market, with the sourcing and contact steps triggered only when something relevant appears. That is how the play works best, as a monitor rather than a thing you remember to run.

Run this play on your own desk

Connect hyreflow to Claude or ChatGPT, paste the prompt above, and fill in the blanks. By default it shows you the cost before it spends.