They just announced layoffs. Should we still reach out?
It depends on which function was cut and whether the work that function did went away with it. Layoffs are usually a cost decision, not a demand decision: the company still has the same customers, the same obligations, and the same month-end. If the team that was cut was doing work your product absorbs, the layoff is a strong buying signal, because somebody is now expected to produce the same output with fewer people and has just had budget freed to do it. If the team that was cut was your buyer, the account is closed for the quarter and reaching out reads as opportunism.
So the answer is a routing decision, not a moral one. Check what was cut, check whether the obligation survived the headcount, and then either reach out to the person now absorbing the work, or set a watch and leave them alone. The one thing never to do is send a cadence that mentions the layoff, since the people you are writing to have just watched colleagues leave and are not looking for a vendor's read on it.
Two questions decide it
First: did the work leave with the people? If a company shuts an entire product line, the work genuinely disappeared and there is no consequence to sell into. If a company cuts a support team while keeping the customers, the work did not leave, it redistributed, and the redistribution is the consequence.
Second: does the freed budget move? Cutting headcount frees salary budget, and in many organizations part of it becomes available for tooling that closes the capacity gap, precisely because the alternative is missing the obligation. This is the honest version of the vendor claim that layoffs create demand: they create it only where an obligation survives the people who were meeting it.
The decision table
Find the row that matches what was cut relative to what you sell. The window column is how long the consequence stays acute before the organization settles into its new shape and stops feeling the gap.
| Row | What was cut | Does the work survive? | Reach out? | Who, and when |
|---|---|---|---|---|
| 01 | The team that did the work your product absorbs | Yes, redistributed to fewer people | Yes, this is your strongest case | The surviving manager, 2 to 6 weeks after the notice |
| 02 | A support or operations function, customers retained | Yes, obligations unchanged | Yes | The VP now accountable for the same service level |
| 03 | Your buying committee or the function you sell to | Unclear, and your sponsor is gone | No, not this quarter | Set a watch for the backfill or the reorganization |
| 04 | An entire product line or business unit | No, the obligation went with it | No | Re-qualify the account entirely, the profile has changed |
| 05 | Broad cuts across every function | Yes, but nobody has capacity to evaluate anything | Wait 1 to 2 quarters | Watch for the first rehiring requisitions, which name the surviving priorities |
| 06 | Recruiting, enablement, or internal tooling teams | Yes, and the internal build option just died | Yes, carefully | Whoever inherited the roadmap those teams owned |
Where layoff notices are actually public
In the United States, the Worker Adjustment and Retraining Notification Act requires covered employers to give sixty days advance written notice of a plant closing or mass layoff, and the notices go to state dislocated worker units, which publish them. That publication is the most reliably dated layoff evidence available, and it usually appears before the press coverage does.
- The statute sets the sixty day notice requirement and defines the covered thresholds, so you can tell whether a given event should have produced a notice at all.
- The regulations spell out the definitions, the exceptions, and what the notice must contain.
- State labor departments publish the notices they receive, with the employer name, the location, the number of employees affected, and the effective date.
- Several states run notice requirements broader than the federal one, so smaller reductions are visible in some jurisdictions and invisible in others.
- Absence of a notice is not evidence of no layoff. Reductions below the thresholds, and reductions spread across sites, may produce no filing at all.
The effective date on a notice is the number to build your timing on, not the announcement date. The gap between them is exactly the period when the surviving managers are working out how the work gets done afterward, which is the moment your consequence becomes real to them.
Tone rules that keep you welcome
- Never reference the layoff itself
Reference the operational consequence instead. The recipient will make the connection and will appreciate that you did not make them read it.
- Never use urgency language
Nothing about acting fast or windows closing. The organization is already under pressure and adding to it is how you get remembered badly.
- Lead with the specific work, not the product
The month-end close, the onboarding backlog, the ticket queue. Name the thing that is now harder and let them decide whether it is worth a conversation.
- Give them a graceful exit
An explicit offer to come back next quarter costs you nothing this month and preserves an account you will want later.
This is what the category calls layoff signals, restructuring triggers, and WARN notices.
The category files this under layoff signals or restructuring triggers, and the underlying public source is the WARN notice, named for the federal Worker Adjustment and Retraining Notification Act. Vendors that sell layoff data are usually aggregating state WARN publications plus press coverage.
Two things about that are worth knowing before you buy a feed. WARN thresholds mean plenty of real reductions never generate a notice, so the coverage is systematically incomplete at the small end. And the notice tells you the employer, the site, the count, and the date, but not the function, which is the single field that decides whether the event matters to you. That has to be read from the company's own communications and hiring pages.
Questions people ask next
Is it ever acceptable to mention the layoff?
In a first touch, no. If the person raises it in conversation, follow their lead. The rule exists because a cold message that opens on somebody's worst month reads as opportunism regardless of how carefully it is written.
How long should I wait?
Two to six weeks for the row where the work survived and redistributed, because that is when the surviving managers have worked out what is now impossible. One to two quarters for broad cuts, where nobody has the capacity to evaluate anything.
Does a hiring freeze count the same way?
It is a weaker version of the same logic. Work grows, headcount does not, so the capacity gap opens more slowly. The consequence is real but the urgency is lower, so treat it as a watch trigger rather than a reason to call this week.
Where to check this yourself
Primary records and published research, not vendor blog posts. Every link was checked on September 1, 2026.
- WARN Act, 29 U.S.C. 2102, notice requirementlaw.cornell.edu
The statutory sixty day advance notice requirement and its conditions.
- WARN Act, 29 U.S.C. Chapter 23uscode.house.gov
The full chapter, including definitions and the covered employer thresholds.
- WARN regulations, 20 CFR Part 639ecfr.gov
The implementing regulations: definitions, exceptions, and what a notice must contain.
- California WARN notices, Employment Development Departmentedd.ca.gov
A state dislocated worker unit publishing the notices it receives, with employer, location, count, and effective date.
- New York WARN notices, Department of Labordol.ny.gov
Another state publication, useful for seeing how much the format and threshold vary by jurisdiction.
Intakra reads a restructuring against what you sell, keeps it only when the work survives the headcount and it can name the role now absorbing it, and attaches the dated public notice.
Free scan, no signup, no card