Not Boring All articles
Business

The Suits Who Ate Silicon Valley

Not Boring
The Suits Who Ate Silicon Valley

Photo: Oakpont-au, CC BY-SA 4.0, via Wikimedia Commons

There's a formula, and once you see it, you can't unsee it.

A private equity firm acquires a profitable software company—often one with a loyal customer base, a solid product, and a small but genuinely ambitious R&D team. Within 18 months: the R&D budget gets trimmed, the moonshot projects get shelved, the engineering talent that was working on the next-generation platform quietly disperses to competitors or startups. The product gets maintained. Support tickets get answered, more or less. But the thing that made the company interesting? That's gone.

What's left is a cash machine. Efficient, optimized, and pointed squarely at the exit.

The Playbook, Explained

Private equity's involvement in technology isn't new, but its scale and ambition have grown dramatically over the past decade. According to data from PitchBook, PE firms acquired more than 3,400 technology and software companies between 2018 and 2023—a pace nearly double what it was in the prior five-year period. The targets have shifted too. Where PE once focused primarily on distressed or undervalued assets, firms like Vista Equity Partners, Thoma Bravo, and Francisco Partners increasingly target healthy, growing software companies that simply haven't maximized their margin potential.

The logic is coherent from a pure returns standpoint. Software businesses—particularly those with subscription revenue models—have predictable cash flows, low physical overhead, and customer bases that are expensive to migrate away. They're ideal candidates for financial engineering: lever up the acquisition, cut operating costs, raise prices, and sell the whole package to a larger acquirer or take it public in three to seven years.

The problem is that "cutting operating costs" in a technology company almost always means cutting the thing that made it a technology company in the first place.

What Gets Cut First

Talk to engineers who've survived PE acquisitions at software companies—and plenty of them have, given the volume of deals over the past few years—and you hear the same story with minor variations.

R&D headcount is the first lever. It's expensive, it's hard to justify on a quarterly basis, and its returns are uncertain by definition. Research into next-generation features or platform capabilities doesn't show up on a cash flow statement in a way that makes a debt service schedule look comfortable. So it goes.

Next come the experimental teams. The small groups working on adjacent product lines, the internal incubators, the partnerships with university research programs. These initiatives were often the source of the company's most defensible long-term intellectual property—but they require patient capital, and PE timelines are not patient.

What typically survives is maintenance engineering and customer-facing support infrastructure. The code keeps running. The existing product keeps getting patched. But the forward motion stops.

One former VP of Product at a mid-market HR software company—acquired by a major PE firm in 2021—described it this way: "We went from a company that was genuinely trying to build something new to a company that was trying not to lose customers while we got ready to sell. Those are completely different missions. You can't run them with the same team."

The Talent Exodus Problem

Here's what the deal models don't fully account for: the people who build genuinely innovative products are not primarily motivated by salary stability. They're motivated by the work itself—by the sense that what they're building matters and that there's room to push the boundaries of what's possible.

When PE ownership signals a shift from growth to extraction, those people leave. Not all at once, and not always loudly, but they leave. They go to startups. They go to larger tech companies. They go to competitors that are still in growth mode.

What remains, by a process of self-selection, is a workforce optimized for maintenance. That's not a criticism of the individuals—maintaining complex software systems is skilled, valuable work. But it's a fundamentally different capability than building new ones.

The downstream effect is that PE-owned software companies increasingly struggle to respond to competitive threats that require genuine product innovation. They can cut prices. They can improve support. They cannot easily reinvent their product architecture or launch a credible next-generation offering, because the people who knew how to do that took their institutional knowledge elsewhere.

The Broader Ecosystem Cost

Zoom out far enough and this starts to look less like a series of individual business decisions and more like a structural shift in how American technology development gets funded and organized.

For most of Silicon Valley's history, the dominant capital model was venture-backed growth: take risks, build aggressively, accept losses in exchange for the possibility of transformative scale. That model produced the internet, the smartphone, cloud computing, and the foundational infrastructure of the modern digital economy.

PE's expansion into tech represents a competing model—one that optimizes for return on invested capital over a fixed horizon rather than for technological possibility over an indefinite one. Neither model is inherently villainous. But when the PE model begins to dominate sectors that were previously driven by the venture model, the composition of what gets built starts to change in ways that matter beyond any individual portfolio.

Fewer moonshots. More margin expansion. Less foundational research. More debt service.

The Counterargument (And Why It Falls Short)

PE defenders—and there are articulate ones—make a reasonable point: many of the companies being acquired weren't actually innovating. They were burning capital on unfocused R&D while underserving their existing customers. PE ownership, in this reading, imposes a discipline that forces companies to deliver value in the present rather than chasing speculative futures.

There's something to that. Not every R&D budget is well-spent, and not every experimental team produces something worth the investment.

But the counterargument misses a fundamental asymmetry. The downside of killing innovation is often invisible—it's the product that never got built, the market that never got disrupted, the capability that never got developed. The upside of financial discipline shows up cleanly in the income statement. In a world where investors are measuring what's measurable, the invisible losses almost always lose the argument.

What Comes Next

The honest prognosis isn't great, at least in the near term. PE's appetite for software assets hasn't diminished, interest rate pressures have made some targets even more attractive, and the exit environment—whether through strategic sales or IPOs—continues to reward the financial engineering playbook.

But there are signals worth watching. The AI wave has created a new generation of genuinely innovative software companies that are, for now, too early-stage and too uncertain in their economics to be obvious PE targets. And some large technology acquirers are beginning to recognize that buying a PE-optimized software company means buying a product that's already been hollowed out—a problem that surfaces quickly in post-acquisition integration.

The suits ate a lot of Silicon Valley. Whether the next generation of builders finds a way to keep them at the door is a question that will shape American technological competitiveness for the next decade.

And that's about as not boring as it gets.

All Articles

Related Articles

You Bought the Robot, Now Your Team Moves Slower

You Bought the Robot, Now Your Team Moves Slower