Key Takeaways

  • Law firm collapses function like classic bank runs because partner exits erase revenue overnight while massive fixed costs like office leases remain locked in.
  • When a rainmaker leaves, the remaining partners split a smaller profit pool while their market compensation at competing firms like Cravath stays unchanged.
  • Insolvency risk introduces fraudulent transfer liabilities, forcing partners who stay too long to face creditor clawbacks on prior profit distributions.
  • Cross-specialty dependence accelerates the spiral: if corporate dealmakers leave, specialist practices like tax find themselves stranded without internal deals to service.
  • Morley analyzes this self-fulfilling dynamic through Morley's Three-Part Leave-Stay Decision Framework.

The Morley's Three-Part Leave-Stay Decision Framework

Part 1: Relative Compensation Calculus

The partner evaluates their immediate compensation drop relative to external market offers: “Because that guy left and took revenues with him, and the costs of the firm are going to stay the same, we in the aggregate, me and my other partners, have to be paid less as a result. So I'm going to get paid less. But the amount I can get paid by moving across the street to Cravath is going to stay the same.” (play from 22:22)

Part 2: Bankruptcy and Clawback Liability Risk

The partner discounts expected end-of-year profit distributions by the probability of insolvency and creditor clawbacks: “If everybody follows the same logic I'm following, they might leave before me. And then one guy leaves and another guy leaves and all of a sudden we're in a run on the bank. And if the firm ultimately collapses, I'm going to have to give back all or a portion of the money I received from the firm between now and the date of collapse.” (play from 23:00)

Part 3: Viability of Practice

The partner assesses whether their own internal workflow remains viable without departure-affected colleagues: “What about the viability of my practice? Most law firms now, including Weil, have eat-what-you-kill compensation systems. You get paid according to your productivity. If I'm a tax lawyer and I'm in the business of servicing M&A deals brought in by M&A lawyers, then if all the M&A lawyers have left, I'm not going to look even to my own firm's managing partners as if I'm very productive.” (play from 24:13)

When This Works (and When It Doesn't)

Morley designed this framework to explain how individual risk-mitigation choices convert into an uncontrollable partner run inside professional partnerships. It applies whenever revenue-generating talent can walk out the door with their clients while the firm remains saddled with long-term fixed liabilities. “You often can't cut costs as quickly as you lose revenues,” (play from 16:25) Morley points out. “So when the partner leaves, you still got to pay the lease on that partner's corner office.” (play from 16:29)

The framework breaks down when applied to standard corporate entities where equity capital absorbs operating losses and employees cannot instantly port revenue to a competitor. In a software company, customer contracts belong to the enterprise rather than the account executive, and employees do not face personal fraudulent transfer claims on their ordinary salary if the business fails. The model only operates at full force when human capital, customer ownership, and equity risk reside in the exact same person.

What to Do With This

If you run an agency, boutique consultancy, or early-stage platform where key employees own customer accounts, run a vulnerability audit this week across all three components:

1. Calculate your fixed overhead ratio per key contributor. List your long-term leases, software seat licenses, and non-cuttable debt obligations. If your top account director generates $1.5M in margin but leaves behind $400,000 in unhedged annual overhead, map who absorbs that haircut the day they quit.

2. Review your non-compete, account handoff, and distribution covenants. Make sure departing managers cannot immediately offer clients identical terms elsewhere while your remaining staff takes a pay cut to service legacy commitments.

3. Identify inter-team workflow dependencies. If your data engineering lead depends entirely on the design director to scope and close enterprise packages, a sudden exit by the designer instantly leaves the engineer unproductive under eat-what-you-kill metrics. Cross-train service delivery so no single operator's resignation strands the specialists beside them.