Not a coincidence.
Symptoms of a system.
The premise
The plan ran long. Now the bill comes due.
When a private equity firm acquires a software company, the intended playbook is clear: invest, grow, sell within a target holding period. But the average hold period hit 6.6 years in 2025, and more than 16,000 buyout-backed companies now sit in unsold portfolios with the original financial thesis no longer working. When the plan runs long, genuine investment can give way to extraction. Left Holding explains the financial mechanics behind that shift — and gives you the tools to recognize the patterns from inside or outside the company.
For employees
You're not imagining it.
- Decode the all-hands meeting and hear what leadership isn't saying.
- Read the company's trajectory before the trailing signals arrive — pricing, leadership turnover, project cancellations.
- Calculate what your equity is actually worth once the liquidation waterfall is paid.
For customers
The signals are observable from the outside.
- Spot the signs of vendor decay before the next renewal conversation.
- Resist extraction pricing — start building leverage two quarters out, not the week before.
- Negotiate from documented decline, not vendor goodwill.
What's inside
A primer, then two parts.
The primer
Chapter 1 stands alone. Read it once, and the patterns in Part I stop looking like coincidences.
-
01
How the Money Works
The Anthology bankruptcy — and the capital structure (debt, fees, dividend recaps, the maturity wall, the Monday tracker) that turned a profitable software company into a debt-servicing machine.
Part I — The patterns
Eight chapters, each centered on patterns you can recognize from inside or outside the company.
-
02
The Consultants Arrive
The war room on the third floor. The 200-slide go-to-market built in a month. The institutional knowledge that walks out when work that's core to the business gets outsourced.
-
03
The Story Changes
The user conference that stops teaching you anything. The "unified platform" that's three products sharing a login screen.
-
04
The Market That Doesn't Exist
The inflated TAM, the aspirational ICP, the upmarket pivot before the product is ready — and the Cloud Software Group story as the documented version.
-
05
The Checkbox Playbook
Harvey balls, 47 feature rows, and the forty to sixty percent of pipeline that ends in no decision.
-
06
The Numbers Game
NRR that masks churn, a Rule of 40 that rewards cutting, and the expansion-vs-extraction margin frame that lets you tell one from the other.
-
07
The Roadmap Slide
The same three features on three consecutive roadmap slides. The 2:47 a.m. incident. The tech debt the deck doesn't show.
-
08
The People Keep Leaving
The six-phase departure cycle. Three CROs in four years. The principal engineer who stays because unvested equity is a constraint, not a reward.
-
09
The Bill Comes Due
Renewal increases without value, features migrating to higher tiers, the CSM whose role has shifted to commercial terms — and the Broadcom/VMware story at scale.
Part II — The decisions
What to do about it. The diagnostic, with guidance for each audience.
-
10
The Diagnostic
Nine signals, a scoring system, the two-signal override, and worked examples of what each score looks like from the inside.
-
11
What Employees Should Do
The equity waterfall in plain language. Reading the all-hands. The information you need to evaluate your situation clearly — and the public sources that get you there.
-
12
What Customers Should Do
The two-quarter window for building visibility. The anti-reference, the documented decline, and the renewal conversation you walk into with alternatives in hand.
From the book
The cumulative stress shows up as slower releases, thinner support, a roadmap that quietly stops delivering — while the cockpit instruments still read green.
Before a single engineer was paid, a single support ticket was answered, or a single server was powered on, nearly half the company's revenue went to lenders. The company had ceased being a software provider and had become a debt-servicing machine that happened to sell code.
Software is hired to do a job, and when the conference stops speaking to the job holder, the vendor is redirecting attention away from the questions the job holder would ask.
Expansion margin improves gradually, because operating leverage takes time. Extraction margin improves fast — often several times faster — because cutting costs produces immediate margin impact.
The temporary pain of investment looks different from the permanent pain of extraction.
When your vendor starts describing itself in terms you don't recognize, it's rational to ask whether they still understand the problem they were hired to solve.
Now available.
In print and Kindle on Amazon. Ebook and audiobook on Google Play.
Audiobook also coming to Apple Books, Audible, and other platforms.