Case

An international shutdown closed out clean in 45 days, with zero lawsuits and no spectacle.

An operations team, about ten people, had to be shut down in an international jurisdiction with strong labor protections. I ran the legal coordination, the vendor exits, and the internal messaging. Forty-five days, zero lawsuits, no spectacle.

The situation

The department was operations, and there were about ten people on it. The underperformance case wasn't in question. The numbers made the decision for leadership. What made it hard was where it was happening: an international jurisdiction where labor protections are strong enough that a shutdown done wrong doesn't just cost severance. It costs months of legal exposure and a reputation in that market that follows the company into its next hire there.

Nobody on the leadership team had run a shutdown in that jurisdiction before. That is normal. Most operators do this once, maybe twice, in a career, and the rules are different every time. A process that closes a team cleanly in one country can trigger a legal claim in another, over the exact same set of facts.

Ten people is a small number on a spreadsheet. It is not a small number to manage well. Each person needed a real conversation, fair compensation, and proper notice, all on a timeline that a foreign legal system, not a company calendar, was ultimately going to judge.

What a mess would have cost

Without someone who had done this before, the stakeholders would have gone straight to local legal advisors themselves, unprepared, and that rarely goes well. Every legal culture handles employment matters differently: the pace, the documentation, the expectations around what gets negotiated and what gets stated as fact. Someone walking in cold, expecting the process to work the way it does at home, ends up on the back foot immediately.

That back foot is expensive. It shows up as slower timelines and worse terms, exactly the kind of dispute that strong labor protections exist to give leverage over. The cost was never the shutdown itself. It was the version run by people who didn't know how the local legal system operates.

There is also a cost that never shows up on the incident report: the company's standing in that market afterward. Handle a shutdown badly in a jurisdiction with strong labor protections and word travels through the same professional and legal circles you will need the next time you hire there. Handle it well and it barely registers.

Compliance, exits, messaging

The hardest part, and the part most people get wrong when they try to run an international shutdown themselves, is coordinating with local legal advisors, not simply hiring one. That means knowing what pace to move at, what to put in writing, when to push and when to wait. I ran that coordination directly, and I kept internal stakeholders briefed the whole way through instead of handing them a finished decision with no context.

Then came the people. Ten employees needed to hear this delivered in a way that was direct and compassionate at the same time, and they needed to receive compensation that was fair, not the legal minimum padded with good intentions. Getting that balance right protects the people leaving and it protects the company from the exposure that comes from getting it wrong.

The part that surprised everyone was vendors. I expected the legal side to be the fight. Instead, vendors turned out to be harder than anticipated, mostly because their standard policies are not built for a full shutdown and most account managers simply are not trained to handle one. Every vendor conversation started from a script that did not fit the situation, which meant every exit took more explaining and more escalation past the first point of contact than a routine account closure ever would.

A standard cancellation policy assumes the company on the other end is still operating and just wants to switch providers. It does not assume a full exit from the market. So the first answer from almost every account manager was the wrong one, built for the wrong scenario, and every vendor relationship needed to be walked up to someone with the authority to close it out on terms that matched reality.

45 days, zero lawsuits

Forty-five days, start to finish. Zero lawsuits. No spectacle. The ten employees affected were compensated appropriately and heard the news directly, not through a rumor or a vague internal memo. Every vendor relationship closed out clean, even the ones that took extra rounds to get there. And the stakeholders never had to sit across from a local legal advisor unprepared, because that conversation ran through me.

What operators should watch

  • Local legal advisors are the hardest part of an international shutdown, not a formality you hire out at the end. Get someone who already knows how to work with them before you need one.
  • Do not let unprepared stakeholders walk into a foreign legal process cold. Different legal cultures negotiate differently, and getting that wrong costs more than the shutdown itself.
  • Pay people appropriately and document it well. It protects them, and it protects you from the exposure strong labor protections are designed to create.
  • Do not treat vendors as a formality. Budget extra time. Most account managers are not trained for a full shutdown and will default to standard policy instead of your situation.
  • Internal messaging matters as much as anything happening outside the company. How you tell the people who are staying shapes trust just as much as how you treat the people who are leaving.

Got something like this on your plate?

← All cases