A Promising Rescue That Set Everything in Motion

In Episode 68 of Client Horror Stories Paul Byrne, founder of a digital agency operating in the Magento e-commerce development space, sat down with host Morgan Friedman to share one of the most layered, bizarre, and financially threatening experiences of his professional career. It was a story that unfolded across multiple acts — a death, an inheritance, a corporate looting, a deposition, and ultimately, a hard-won recovery. What made it especially compelling was not just the drama of the events themselves, but the quiet lessons buried within each twist: about risk, about trust, about knowing when to be patient and when to draw a hard line.

The story began, as many agency horror stories do, with a rescue. A startup operating in the e-commerce space had been building a Magento-based website through another development firm — one that Paul knew personally, as the Magento world at the time was a relatively small and collegial community where agencies collaborated more than they competed. The original firm, however, had failed to even begin the project within the timeframe the client had been expecting. Fed up and behind schedule, the startup cancelled their contract and came to Paul’s agency looking for someone who could actually deliver.

Paul and his team stepped in immediately. The project was genuinely exciting. The startup sold high-end, expensive products to designers in a B2B model — a niche but well-defined market. What made the work particularly engaging was that the client team knew their customers exceptionally well. They had clear ideas about the user experience they wanted to create, they were innovative in their thinking, and they brought real energy to the collaboration. Paul and his team got along with them naturally. The website launched, orders began coming in, and the agency was deep into the next phase of development — building out more complex user experiences and custom features that pushed the boundaries of what had been done before on similar platforms. Multiple team members were heads down on the project. Everything appeared to be going well.

The First Sign of Trouble — and the Hidden Risk Nobody Warned About

Then the payments slowed. Paul was not immediately alarmed. The client had always paid on time — or at least within their terms after a single reminder. The CEO had been on vacation. These things happen. Paul made the judgment call to keep his team working while he began reaching out to understand what was going on. Within six to eight weeks, however, the picture had become considerably more complicated.

The startup, it turned out, had been funded primarily by a single wealthy businessman based in Texas — the same state where Paul’s agency was located. This investor was the financial engine behind everything. And he had died.

When Paul asked the CEO directly whether there would be any trouble collecting the outstanding receivables, the answer was not reassuring. The CEO had been advised by legal counsel to halt all payments until the estate situation had been clarified. The money was still in the bank. Nobody was disputing that it was owed. But the lawyers had put everything on hold while they sorted out what came next.

Morgan Friedman paused here to introduce a concept that doesn’t get nearly enough attention in business planning discussions: keyman risk, or in modern terminology, key person risk. The idea is straightforward — what happens to your business, or to a deal you are depending on, if one critical individual suddenly disappears? Most entrepreneurs think about this in terms of their own team. What if a key employee leaves? What if a founder gets sick? But Paul’s situation illustrated a far more insidious version of the same risk. The person who died was not Paul’s client. He was not even someone Paul had met or had a direct relationship with. He was the investor funding the client. He was two levels removed. And yet his death had the power to freeze everything — payments, decisions, development, and ultimately the future of the entire company.

This is what makes key person risk so dangerous in practice. It is not always visible. You can do your due diligence on the client in front of you and still have no idea that the entire financial foundation of their operation rests on a single individual whose health and longevity you have no way of assessing. Paul had seen the investor appear in a video. He seemed to be in reasonable health. There had been no warning signs. And yet, as Morgan observed with grim simplicity, it comes for us all.

The Son Takes Over — and Everything Gets Worse

Paul responded to the situation with measured caution. He slowed down development, redirected his team members to other projects where capacity allowed, and waited for the legal situation to clarify. He stayed in close contact with the CEO, who remained straightforward and honest throughout. The CEO confirmed that money was still in the bank and that the hold was genuinely a legal formality rather than an attempt to avoid payment. Paul believed him. He also had a practical safety net — his agency owned the codebase and hosted the website, meaning he had real leverage if things deteriorated further.

What he did not yet know was how dramatically things were about to deteriorate.

The investor’s son had inherited control of the business. He was approximately forty years old — not a teenager, not someone who could be excused on grounds of inexperience due to youth. He had an advanced degree, either law or business. He was, by all external appearances, a fully formed adult. But the picture that began emerging through Paul’s conversations with the CEO — who himself barely knew the son — was deeply troubling.

The son had a well-known drug problem. He had been through rehabilitation multiple times. He was known locally as a playboy. He had no background in entrepreneurship, no experience in technology or e-commerce, and no apparent interest in learning. Morgan, cutting through the diplomatic language, asked directly whether the son was a cocaine user. Paul confirmed that was essentially the picture. Red flags, as Morgan put it, up the gazoo. Not the kind of subtle warning sign that requires careful interpretation — the kind that arrives with screeching violins.

To his credit, Paul tried to give the man the benefit of the doubt. He had worked with functioning alcoholics and drug users before. He knew that such people existed in larger numbers than most assume, and that functional performance was sometimes possible despite personal struggles. He was trying not to be judgmental. He was hoping that the responsibility of inheriting a company might motivate the son to step up and prove himself.

It did not.

The Looting — A Company Abandoned Overnight

The son arrived at Paul’s offices with what he described as his IT expert — a personal associate with no apparent technical credentials who was being offered equity or revenue share in exchange for his involvement. The son announced that he was considering changing the company’s strategy entirely and stopping all development work. Paul accepted this calmly and took the opportunity to raise the outstanding accounts receivable directly. When would the money owed be paid? The son deflected, pointing to the new IT expert as the person who would be taking over and promising that payment would be sorted within a couple of days.

Days passed. Nothing happened. The original CEO — the experienced, trustworthy professional who had been Paul’s primary contact throughout — was ousted. The son began communicating directly with Paul, and it quickly became clear that he understood nothing about web development, e-commerce, or technology of any kind. His new IT expert was supposedly flying in to manage operations on the ground, but the son refused to reimburse even his travel expenses. It was an absurdity that told Paul everything he needed to know about how seriously the son was taking any of this.

Then came the act that no one had anticipated. After a few more weeks of chaos and confusion, the son simply abandoned the company. He did not file for bankruptcy. He did not attempt to sell the business or find new investors. He did not formally wind down operations through any legitimate process. He sent an email declaring the company closed, and then — in the move that crossed every legal and ethical line imaginable — he withdrew all of the startup’s money into his own personal account.

Employees who had been working hard, who had genuine traction in the marketplace and believed in what they were building, suddenly found themselves unable to be paid. Vendors went unpaid. Orders were still coming in through the website, but there was no infrastructure left to fulfill them. The people who had built the company were in a surreal limbo — still showing up, still working for free, still taking calls from clients, trying desperately to keep something alive that the son had simply decided to abandon on a whim.

Paul’s Unlikely Path to Recovery

The team that remained — the CEO and his core colleagues — were not ready to give up. They began exploring whether they could reconstitute the company under new ownership. Paul consulted a lawyer to understand where things legally stood. The answer was surprisingly clarifying. Because the son had abandoned the company rather than declaring bankruptcy, the company technically ceased to exist in any meaningful operational sense. A company that no longer exists cannot hold assets. And because Paul’s agency had never been paid, they still owned the codebase — the software they had spent months building.

This gave Paul an unexpected but powerful option. The former team — the people he had worked alongside for months, people he trusted and respected — wanted to start fresh. They needed the software. Paul made a decision that was equal parts practical and generous. He sold them the codebase on a payment plan, structured around terms they could realistically meet. He did not simply forgive the debt or hand over his work for free. But he recognized that pursuing the son through litigation for the full amount was unlikely to recover anything meaningful, and that the people in front of him were worth betting on.

The new company was up and running within days. The former team reached out to every client they had previously served, explained the situation transparently, gave the new business a new name, and — in a gesture of genuine integrity — offered to fulfill any orders that had been placed with the old company at their own expense. Clients responded. Business came back. The startup, in a new form, was alive again.

The Deposition — Facing Down Expensive Lawyers

Paul believed the worst was behind him. He scaled back his involvement with the new company to maintenance tasks, bug fixes, and occasional feature requests. Things were calm. And then one day the call came that no one wanted to receive. The son, despite having looted the company and abandoned it entirely, had decided to sue the new team — claiming some form of ownership or entitlement over the company he had destroyed.

Paul agreed to be deposed. The lawyers for the son arrived at his office — he had offered his conference room to save everyone the commute — with all their recording equipment and the unmistakable air of people who charged by the hour and enjoyed it. They were, by Paul’s description, cut from the same cloth as their client: snooty, self-important, and fond of asking questions with embedded assumptions designed to put words in a witness’s mouth.

Paul was not having it. For two hours, every time a question arrived loaded with a false premise, he pushed back. He corrected the framing. He refused to accept the embedded assumptions. He answered on his own terms, even as the opposing lawyers objected repeatedly — objections that, he learned, did not prevent him from answering but simply flagged the exchange for potential exclusion if the case went to trial. He described the experience as exhausting but clarifying. He felt good about how he handled himself.

In the end, the case never went to trial. A settlement was reached. The son received some partial equity in the new company — a concession that galled everyone who had watched him destroy what others had built — but the new team retained operational control and continued moving forward. Paul never recovered the full amount of the original unpaid invoices. But over time, through the ongoing relationship with the new company, some of those losses were offset. The new clients paid consistently. Paul put them on tight payment terms from the start — a day late meant work stopped — and that discipline held throughout.

What the Story Teaches Us

Morgan and Paul closed the episode with a broader reflection on what the experience revealed about business, risk, money, and character. Several lessons emerged with particular clarity.

The first was the danger of invisible dependency. Paul had done everything right in terms of diversifying his own client base — ensuring no single client represented more than twenty percent of his revenue. But he had no visibility into the fact that his client was almost entirely dependent on a single investor whose health was unknown and whose estate planning was nonexistent. Key person risk is not always about your own team. Sometimes it lives several layers away, hidden behind relationships you cannot see.

The second was the importance of payment discipline. Paul acknowledged that under normal circumstances he would never have allowed receivables to accumulate to the level they reached with this client. The unusual circumstances — a death, a legal hold, a transition — had convinced him to extend grace. That grace cost him significantly. The lesson was not to be heartless, but to be clear. Terms are terms. The moment a client falls behind, the conversation needs to happen, regardless of the circumstances on their side.

The third was the value of practical thinking over emotional reaction. Paul could have refused to work with the new team on principle. Technically, they were associated with the situation that had cost him money. He chose instead to look at who those individuals actually were, how they had conducted themselves throughout the crisis, and what the realistic path forward looked like. His pragmatism paid off. The relationship that emerged from the wreckage became one of the strongest and most durable of his agency’s history.

And finally, there was the quiet lesson about character — both in recognizing it and in demonstrating it. The son had every advantage imaginable: inherited wealth, an education, a functioning company handed to him without effort. He destroyed it anyway. The team that built the company from the ground up had none of those advantages. They showed up anyway, worked for free, honored their clients’ orders, and rebuilt from nothing. Paul backed them. And in doing so, he demonstrated exactly the kind of judgment that separates professionals who thrive over the long term from those who don’t.

As Morgan observed at the close of the episode, life is not fair. The question is never whether unfairness will find you — it will. The question is what kind of person you choose to be when it does.