Customer Layoffs Counter-Play 2026
When a customer cuts staff, the goal is to keep the logo and an expansion path for when they rehire. Layoff news starts this play; the check compares seats and usage with the account's pre-news level and your successful customers. Real impact gets a right-size-and-retain offer and a revised forecast on the CRM record; no impact yet gets no move and a 30-day recheck.
When a customer cuts staff, the account you want on the other side is still a customer: the logo kept, the team that stayed running on your product, and an expansion path ready for when they rehire.
This play starts when layoff or restructuring news reaches you, and treats the news as evidence, not a verdict. Seat data decides: the right-size offer where usage has really moved, no move and a recheck where it hasn't.
Measure it on logo retention through customer layoffs, days from the news to a decision, and expansion on retained accounts once they rehire.
How it works9 steps
01SignalHear the news, with the account context attached
Point Clay at your customer list, not your prospect list. Turn on its news signal for each account, and refresh headcount each month through a provider whose collection and reuse rights you've checked. A formula flags a drop of 10% or more in a quarter (a default to tune); treat an estimated drop as a signal to verify, not proof of layoffs. In the US, pull public WARN notices from state labor departments into the same table. Attach the headcount change, the teams named in the news, ARR and the renewal date. By hand: a news alert on each customer's name, plus a monthly check of public reporting and the company's LinkedIn page, without scraping (the headcount trend there needs Premium Business or Sales Navigator).
02ScoreCompare seats and usage with peers and the pre-news level
Build the benchmark once, refresh it quarterly (how to build it):
- Comparison customers: same segment (plan tier, seat band), 12+ months as customers, renewed at the same or higher revenue. Aim for 20; with fewer, label it low confidence.
- What an active seat is: default, a user active in three of the last four weeks.
- The pattern: the median share of paid seats that are active, and the low end (the 25th percentile). Your CS lead approves it.
Then compare the account twice: active seats now against its own average for the eight weeks before the news, and seat use against the benchmark. Check the records too: is the champion still active, has the customer already asked to cut seats, and did the cut land on teams that use you? Under about a hundred accounts, do it by hand.
Say an account pays $48,000 for 60 seats and peers use 80% of theirs. The news reports a 25% cut; three weeks later active seats have fallen from 52 to 34. A plan at 40 seats is $32,000 – the $16,000 is a comparison, not a forecast. (The numbers are illustrative.)
03DecisionDecide on usage, not the headline
It's impact if either holds for two weekly checks in a row (defaults): active seats are down 15% or more on the pre-news average, or seat use is below the benchmark's low end. Everything else is no move yet. A customer can lose a fifth of its staff without touching your users. If the champion has gone, run the champion-departure play alongside this one.
04ActionNo impact yet: leave it alone for 30 days
Set Recommended move to No move, note the news in one line, and set Review date 30 days out: a cut can take weeks to reach seat data. If usage has moved by then, it takes the offer lane. If it holds, close it: no call, no email, no discount looking for a problem. Leave it alone covers the decision in full.
05ActionDraft the right-size-and-retain offer first
The offer below goes on the record: a plan at the seats they use, starting now rather than at renewal, and a written path back up when they rehire. Base it on active seats, not their guess or your hope, and trade for term where you can. The shelfware play covers the right-sizing mechanics.
06Human stepThe AM decides and runs the offer
The AM runs the offer as drafted, changes it, or passes, and owns every customer conversation. Aim to make it within ten business days of the check that confirmed impact (a default), while it still reads as help rather than a concession. Before acting, record the success measure and review date: usage steady in eight weeks is progress; a renewal, even a smaller one, is the result.
07ActionIf the team chooses, send the surviving team a value doc
The people who stayed inherit work set up by people who left. A one-page value doc shows them what their team runs in your product and who to ask. Send it by hand, or, once these have been right a few times, your team may choose to automate it in Customer.io, with the doc as a link (Customer.io automations can't attach files). A webhook step logs what went out to the record.
08ActionLog the revised forecast on the renewal
The day the offer goes out, update the renewal deal with the note below. A forecast that still shows the pre-news ARR is a miss reported late; the forecast play covers keeping the whole forecast honest.
09OutcomeReview what changed, then sharpen the benchmark
Eight weeks on, record in Review result whether usage held, and what else played a part. If nothing moved, change the move, stop it, or give it time; the eight-week review covers how. The renewal deal records the result. The rehire trigger (default: headcount back up 10%, or open roles in the teams that use you) sends the account to the seat-upsell play. Each quarter, compare retention on layoff-hit accounts with the rest, and update the benchmark. The low-end line will flag some customers who renew anyway, so each quarter count how many renewers and leavers crossed it.
Setup and templates
Sources: news and monthly headcount from Clay (signals run on Clay's paid plans, and headcount lookups cost Clay credits); active seats per account from a weekly saved query in PostHog, Amplitude or Mixpanel; seats paid for and ARR from billing; champion, renewal date and notes from the CRM. Account-level numbers need your analytics tool's account add-on (group analytics in PostHog, Accounts in Amplitude, Group Analytics in Mixpanel) and a group call in your app. Save the query, then subscribe to it (in Amplitude, add it to a dashboard and subscribe to that) so the result lands in your inbox or Slack on the schedule you set. By hand: news alerts, public reporting and each company's LinkedIn page, and a spreadsheet of active seats before and after the news.
Apply these checks to marketing emails sent by hand or automatically: permission to send, accurate sender details, required address information, an easy unsubscribe and shared suppression checks. Keep required service notices separate from marketing.
Company properties in HubSpot (Starter or above; free HubSpot allows 10 custom properties in total), or your CRM's account object:
| Property | Type | Filled by |
|---|---|---|
| Layoff news | Single-line text (date and link) | Weekly check |
| Active seats before news | Number | Weekly check |
| Active seats now | Number | Weekly check |
| Benchmark seat use | Number (%) | Weekly check |
| Recommended move | Dropdown select: Right-size offer · No move | Weekly check |
| Move reason | Single-line text | Weekly check |
| Value doc | Dropdown select: Sent by hand · Automated · Not sent | Account owner |
| Revised forecast | Number (currency) | Account owner |
| Rehire trigger | Single-line text | Account owner |
| Success measure | Single-line text | Account owner |
| Review date | Date picker | Weekly check, then account owner |
| Review result | Dropdown select: Usage steady · Still falling · Renewed · Renewed smaller · Lost · Too early | Account owner |
The automation here uses HubSpot workflows (any Professional hub). On Free or Starter, run the same saved view and create the tasks by hand. The weekly list is a saved view: Recommended move is known and Review date is this week or overdue. In HubSpot that's two filter groups: Review date is This week, or Review date is before Today. Each move creates a task for the owner, "Layoff news: [move]", with the draft in the body.
Right-size-and-retain offer:
Hi [name] – I saw the news about [company], and I'm sorry for the people affected. [Number] people on your team use [product] each week now. We can move you to a plan for [seats] from [date], at [price]. When you're hiring again, you can add seats by [date] at [price] per seat per [billing period]. That rate applies until [renewal date]; after that, [approved pricing rule]. Would that help?
Finance approves the scope and duration of the price commitment before you offer it. Send this offer under your marketing permission and opt-out rules unless its actual content qualifies as a service message.
Value doc (for the surviving team): what [team] uses [product] for · the three things run most, and who set them up · where the guides are · who to ask on our side, [name and email].
Forecast note: "Layoff news [date]. Active seats [before] → [now]. Revised to [amount]. Rehire trigger: [what we'll watch]."
No move: "No move – [news], usage steady. Recheck [date]."
How Accoil fits
Accoil is a customer-success consultancy with our own tooling, and this is a play we run with you, not for you. We build the benchmark with your team, and you approve it. Every week we check every account in the agreed segment, and the recommended move and its evidence land on the account record in your CRM – we recommend HubSpot – at a pace your team can actually run. Your team makes every call. Nobody from Accoil contacts your customers. After the agreed window we review what changed together, and you keep the playbook, the benchmark and the analysis.
Running it yourself? Swap HubSpot for Salesforce or Pipedrive, and Customer.io for Ortto (rebuilt as account journeys). The play stays the same. On Salesforce, the field writes need API access (Enterprise and up, or an add-on on Professional). On Pipedrive, automations and date triggers need the Growth plan. Already on UserGems? Its Public Filings signal flags layoffs that public customers report to the SEC.
Thirty minutes with Kate, Simon or Peter on one example segment: what a successful customer looks like, where the gaps are, and whether there's work worth doing this quarter.
Talk to a founder →Keep reading
Renewal-Risk Radar Playbook 2026
Renewals go best when the account already looks like your customers who renewed. From 90 days out, this play compares every renewing account with them each week – usage and revenue – checks the records, and puts one move on the account in your CRM: an expansion look, a value review, a save plan with the CSM – or no move, with the reason noted.
Churn-Risk Save Playbook 2026
Your customers who renewed show you what steady use looks like. This play checks every account against that benchmark each week, catches the ones drifting further away while the gap is still worth closing, and puts the move on the account in your CRM: a save conversation, a re-engagement sequence your team chose to automate – or no move, with the reason noted.
The Shelfware Confession Playbook 2026
Seats paid and seats in use drift apart. This play compares each account's seat use every week with customers its size that renewed at the same or higher revenue, checks the records before calling it a gap, and puts one move on the account in your CRM: a seat review with both paths, a reactivation plan, a right-size quote – or no move, with the reason noted.
Every playbook, one download
All 32 workflows as print-ready playbooks — diagrams included. Plus every new workflow as we publish it.