Content
Three situations can reshape a CS org almost overnight.
A layoff. An acquisition. A leadership transition. Most CS leaders will go through at least one of these in their career. A lot of them will go through all three.
They look different from the outside. From inside a CS org, each one creates its own specific kind of disruption that most CS leadership playbooks don’t cover.
A layoff in the CS team means workload redistribution overnight. CSMs who survived the cut absorb accounts they’ve never touched. Customers who had a dedicated contact suddenly don’t. Service levels get stretched. And the CS leader is managing coverage gaps, team morale, and customer relationships all at once, usually without enough information about what comes next.
An acquisition means the org chart is suddenly under review. If the acquiring company has its own CS team, someone has to figure out how to integrate two functions that were built completely differently. Tooling changes. Processes change. KPIs that mattered yesterday may not be the ones that matter tomorrow. And customers are asking questions about what happens to their contacts, their contracts, and the roadmap they were sold on.
A leadership transition means new direction and new priorities. What the previous leader valued about CS may not be what the new one cares about. Budget, scope, and positioning can all shift. The CS leader is rebuilding a relationship from scratch while still running the function, with no guarantee that the ground rules stay the same.
Across all three, the CS leader’s job in the first 30 days is the same: manage your own uncertainty, steady your team, protect your customer relationships, and make sure CS comes out of the disruption in a stronger position than it went in.
The foundation that applies to all three
Get clear on your own position before you manage anyone else’s
Every one of these scenarios puts the CS leader in an uncomfortable spot. You’re expected to have answers you ,ay not have yet. Your team is looking to you for steadiness while you’re quietly processing the same uncertainty they are.
Take the time to get honest with yourself first. What do you actually know? What don’t you know yet? What’s your read on what this means for CS and for your role personally? What are you worried about that you haven’t said out loud?
Do that work before you do anything else. Your team will feel it if you haven’t.
Talk to your team before they fill the silence themselves
In all three scenarios, the instinct is to wait until you have more information before saying anything. That instinct costs you more than it saves.
When people don’t have information they generate their own version of it. And the version they generate is almost always worse than reality.
The message doesn’t need to be polished or complete. It needs to be honest. “Here’s what I know right now. Here’s what I don’t know yet. Here’s what I’m doing to find out. I’ll keep you updated as things become clearer.” Repeat that as often as you have new information, even if the new information is just that nothing has changed yet.
What that message sounds like is slightly different depending on the situation.
After a layoff: acknowledge the loss directly. Don’t move immediately into workload logistics. Your team just watched colleagues lose their jobs. Give that a moment before you get into the operational response.
After an acquisition announcement: your team’s first concern is almost always whether their roles are safe. If you know, tell them. If you don’t, say that honestly rather than letting them wonder.
After a leadership change: be clear about what you know regarding the new leader’s direction and what you’re still learning. Your team will take their cue from how settled or unsettled you appear in those early weeks.
When your team gets laid off
Redistribute workload strategically, not just by availability
The default is to look at who has bandwidth and assign accounts accordingly. That approach produces coverage that technically works and actually doesn’t.
The right move is to triage the book first. Which accounts are highest risk, highest value, or mid-renewal? Those get assigned to your most experienced CSMs, even if that means their book is temporarily heavier than others. Lower-touch accounts can be managed digitally or held with lighter coverage for now.
Be explicit with the team about how you made those decisions and why. That transparency matters more than most CS leaders realize when morale is already fragile.
Reach the customers who lost their CSM before they notice the silence
When a CSM is let go, their accounts don’t immediately know it. There’s a window, usually a few days, before the silence becomes noticeable.
Use that window. Get to the high-value and high-risk accounts personally or through the covering CSM immediately. Acknowledge the transition. Tell them who their new contact is and how to reach them. And if the relationship was strong, acknowledge the change genuinely rather than glossing over it with corporate language.
Customers are more forgiving about change than most CS leaders expect. What they’re not forgiving about is finding out late or feeling like they weren’t worth a direct conversation.
Hold the team without pretending the situation is fine
Your remaining CSMs are doing more work, possibly grieving colleagues who left, and wondering if another round is coming. All of that is real and it will show up in their customer interactions if it’s not addressed.
Check in individually, not just in team meetings. Ask how people are doing with the workload, not just whether the accounts are covered. And be honest about what you know about the stability of the team going forward, even if that answer is that you’re still working to find out.
When you're being acquired
Get ahead of the customer conversation before the announcement does
Acquisitions become public. When they do, your customers will have questions before their CSM has had a chance to prepare answers.
Identify your most important accounts and reach out proactively as soon as you’re cleared to do so. Tell them what the acquisition means for them at the level of detail you actually have. What stays the same. What’s still being determined. And that you’ll keep them updated as things become clearer.
The customers who hear from you directly before they read about it somewhere else are the ones who trust that they’re being taken care of. The ones who find out another way start quietly assessing their options.
Figure out where CS sits in the combined org before assuming anything
If the acquiring company has its own CS team, your role and your team’s structure may not look the same six months from now. That doesn’t mean it gets smaller. It might mean it gets bigger. But assuming continuity without understanding the acquirer’s CS motion is how CS leaders get caught off guard.
Seek out your counterpart in the acquiring org early. Understand how they’re structured, what they own, and how they think about CS. That information shapes how you advocate for your team’s role in the combined entity.
Make the case for how CS should be structured going forward
Acquisitions create a window where org design decisions get made quickly. CS leaders who have a clear point of view on how the function should be structured in the combined org, and who bring that perspective to the right conversations early, have more influence over the outcome than the ones who wait to be told.
Have a clear answer to: what does a combined CS motion look like? What are the risks of not integrating well? What does the customer base need from CS in the next 12 months? Those are the questions the people making integration decisions need answered, and you are the most qualified person to answer them.
When leadership changes above you
Show up in the first 60 days with something useful
The first 60 days of a new leader’s tenure are when they form views about the people and functions around them. That window closes faster than most CS leaders expect.
Show up in that window with something useful. A clear picture of the customer base. Your honest read on the highest-risk accounts and why. Your perspective on where CS is strong and where there’s room to build. Not a polished deck designed to impress. A real, informed conversation from someone who knows the customers better than anyone else in the org.
A CS leader who helps a new exec understand the customer landscape faster than they could on their own gets treated as a thought partner. One who waits tends to spend the next year on the outside of conversations they should be part of.
Understand what the new leader cares about before assuming continuity
What the previous leader valued about CS may not be what this one cares about. The priorities may shift. The metrics that were front and center may move to the background. The strategic initiatives CS was leading may get deprioritized.
Have that conversation early and directly. What are the new leader’s priorities for the first 90 days? How do they think about the relationship between CS and revenue? What do they need from CS to feel like the function is delivering? Those answers shape how you position the team’s work going forward.
Protect CS’s budget and scope during the priority reset
Every new leader does a priority reset. Resources shift. Initiatives that were funded get revisited. CS is not immune to that.
Have the business case for CS ready before anyone asks for it. What revenue does CS protect? What would retention look like without the function? What’s the expansion contribution of the team this year? When that conversation happens, you want to be the one walking in with a clear answer, not building it in the room.
ACROSS ALL THREE SCENARIOS, ONE THING STAYS CONSISTENT
Be useful to the org, not just to CS.
The CS leaders who come out of disruption with more standing than they had going in almost always made that decision early. They offered honest customer health perspective when leadership needed it. They brought context on key relationships when the org didn’t have it. They showed up as a resource to the people above them, not just as a function waiting for direction.
CS’s influence in the org is tied directly to how useful CS is to the people making decisions. Disruption creates an opening to demonstrate that at a level the day-to-day rarely allows.
Most CS leaders don’t use that opening deliberately. The ones who do tend to look back on it as one of the more defining stretches of their career.
