When a company is in distress, restructuring professionals usually focus on the capital structure — debt, DIP financing, cash collateral, and who gets paid first. The systems that actually run the business day to day get much less attention. But in some industries, those systems are the real obstacle to a fast turnaround.
Senior living is a good example. Nursing homes and assisted living facilities are almost never run directly by their owners. A management company runs the building instead. That management company also usually owns every system the building depends on: payroll, HR records, the medical records platform, the accounts payable and receivable system, marketing and referral tracking, and the accounting system. This works fine when the manager is doing a good job. It becomes a serious problem the moment an owner needs to replace a manager who isn't.
Terminating a management contract is easy on paper. Terminating it in practice is not, because the new operator often inherits a building full of residents and staff — with no way to run payroll, bill a resident, pull up a medical chart, or even see how much cash is coming in. If the management company itself is in bankruptcy, the facility's systems may be tangled up in a separate case with its own timeline — one that has nothing to do with the residents and staff waiting on-site.
There is also a cost dimension to this that is easy to miss from the outside. Almost any multi-facility management company allocates its corporate-level costs down to the individual properties it runs — marketing spend, payroll processing fees, insurance premiums, and similar overhead items all show up as line items on a facility's financials, priced and structured at the corporate level rather than negotiated for that specific building. An owner reviewing those line items usually has no easy way to tell whether a given allocation reflects a fair, competitively priced arrangement or simply reflects what the management company negotiated for its portfolio as a whole. Separating a facility from its manager is, among other things, an opportunity to put every one of those allocated costs out to bid on its own terms.
The decision an owner actually faces
It is worth pausing on the choice an owner is making at this point, because it is easy to assume the obvious response to a failing manager is simply to hire a better one. That instinct is understandable, and it is also how the same lock-in problem tends to get reset rather than solved: a new management company arrives, and within a short period the facility is again running on that company's payroll platform, that company's EMR, that company's marketing infrastructure. The underlying dependency hasn't gone away — it has just changed hands.
Bringing in an Operating CRO to rebuild the infrastructure in-house is a different bet. The owner gives up the comfort of an established management brand and the assumption that someone else is minding the day-to-day systems, and takes on direct exposure to whatever happens during the rebuild itself. In exchange, the owner ends up owning its own systems outright, rather than leasing operational visibility from whichever manager happens to be in place. That trade only makes sense if the owner has reason to believe the rebuild can actually be executed at the speed described below; if it cannot, a phased transition to a new manager, with the old systems running in parallel for a period, is very likely the more prudent course. The decision is less about which model is categorically better than the other, and more about whether the specific team available to execute it can move fast enough to make direct ownership the lower-risk path rather than the higher-risk one.
A real example: an assisted living facility in Oxnard, California
This facility, with more than 50 employees, had been run by a management company. The operating company's parent had filed for bankruptcy to renegotiate its loan terms. In the months before the transition, the facility was losing about $70,000 a month.
Ownership brought in a Chief Restructuring Officer to take over operations. The main work wasn't a new business strategy — it was rebuilding every system the old manager had controlled, from scratch, in about two weeks. What makes this case worth discussing isn't the outcome so much as the pace: a full technology and operating infrastructure, rebuilt in-house, on a two-week clock. That pace is itself new. Ten or fifteen years ago, none of the following would have been realistic on this timeline. The facility turned an operating profit by its third month under the new structure — a timeline that is itself a function of how quickly the underlying systems were in place to manage the business.
Why this is possible now in a way it wasn't before
What's notable about this case is not any single system, but the fact that HR, payroll, marketing, AP/AR, medical records, cash management, and insurance were all rebuilt or renegotiated in parallel, in-house, in about two weeks, using contractors and brokers assembled for the specific engagement rather than a large outside vendor relationship. That is a fairly recent capability in restructuring work.
For most of the modern history of turnaround practice, operational systems were slow-moving by nature. Standing up a new payroll platform, a new medical records system, or a new accounting infrastructure was a months-long project even under normal circumstances, let alone in the middle of a distressed transition. A CRO's toolkit was built around that reality: stabilize cash, negotiate with creditors, manage the business with the systems already in place, and treat wholesale technology replacement as something to plan for later, if at all.
Modern software, and the contractor talent now available to configure and deploy it quickly, have changed that calculus. The systems used in this engagement were not custom-built from the ground up — they were existing platforms that a small, focused team could implement and populate with an organization's full operating data in days rather than quarters. That compression is what makes it possible to treat a full infrastructure rebuild as a first-week task in a turnaround rather than a second-year initiative.
This suggests a broader shift worth naming: restructuring is entering an agile age, in the same sense the term is used in software development — short cycles, fast deployment, and the ability to stand up working systems in a matter of days rather than months. A CRO engagement today can reasonably include not just financial stabilization but full operational rebuilding, on a timeline that would have been implausible a decade ago. What used to be a structural constraint on how fast a distressed operator could be turned around — the sheer time it took to build or migrate the systems a business runs on — is no longer automatically true. The constraint now is whether the right technology expertise is part of the team from day one.
The bottom line
Technology dependency is built into how senior living management agreements work, and that isn't going to change. What has changed is how quickly that dependency can be resolved. This case is one illustration of what's now achievable when a restructuring engagement treats technology rebuilding as core, same-week work rather than a downstream administrative task — and of how much faster a turnaround can move as a result.