App Store Private Equity

In a recent interview with TechCrunch following their $18 billion IPO, Bending Spoons founder Luca Ferrari stated plainly that the company's approach to software acquisition works because success comes from "minimizing luck." Instead of betting on the next major paradigm shift or hoping a feature goes viral, the firm focuses on algorithmic execution—buying assets that already have product-market fit and ruthlessly optimizing the underlying financial engine.

Over on Hacker News, the reaction to this philosophy is visceral. The consensus among developers and early adopters responding to the strategy is that minimizing luck is simply corporate-speak for cultural vandalism. The top comments in the thread serve as a furious public mourning for the destruction of beloved apps like Evernote and WeTransfer at the hands of a ruthless acquirer. Bending Spoons is accused of buying beloved tools that took a decade to build, firing the engineering teams that actually care about craftsmanship, and coasting on the remaining brand equity until it bleeds out. To them, minimizing luck is a betrayal of everything tech is supposed to be.

This reaction is entirely understandable. Software craftsmanship is a real and beautiful thing. Watching an acquirer methodically gut the engineering teams of foundational internet utilities feels like a profound betrayal of the Silicon Valley ethos, which assumes that continuous iteration is the highest moral calling of any technology company. To the engineers who spent a decade refining the granular user experience of a file-transfer protocol, slashing the workforce feels like the death of the product itself.

That ethos, though, is an artifact of venture capital, not an economic law. The fundamental issue is this: a utility application eventually solves the problem it set out to solve.

The Economics of Continuous Iteration

The venture model is explicitly designed to fund the search for product-market fit. It is a high-risk game of discovering a new market and iterating wildly until you capture it. Once product-market fit is achieved and organic growth stalls, the economic reality of the asset fundamentally changes. To understand what Bending Spoons is actually doing, we have to adjudicate between this romantic view of continuous software development and the cynical, follow-the-money reality of consumer software economics.

Software, famously, has a marginal cost of zero — distributing one more copy costs absolutely nothing — which means the theoretical financial upside is infinite. In the early days of a company's lifecycle, the dominant cost center is engineering and product development. You are spending heavily on operational expenditure (OpEx) to build the feature set that will attract users. The value of the company is entirely bound up in its potential to grow. Venture capital happily subsidizes the enormous upfront fixed costs of this engineering team because capturing a global market yields monopoly-type returns.

The financial primitive underlying this era is the top-line revenue multiple. Venture capitalists value a high-growth software company based on its revenue expansion; the assumption is that achieving absolute scale will eventually yield massive profits down the line. In the SaaS bubble of the last decade, this dynamic was papered over by free money. Companies with millions of daily active users were valued strictly on their top-line expansion, completely ignoring the underlying profitability of those users. If it cost three dollars in engineering salaries to maintain a user who generated one dollar in subscription revenue, the venture market applauded the scale. In this paradigm, a massive engineering team is an investment in future revenue multiples. The mandate is to keep building.

Consider the practical economics of an application like Evernote. In its golden era, Evernote was constantly adding integrations, launching new presentation modes, and trying to become a central operating system for work. This required hundreds of highly paid engineers, product managers, and designers. The thesis was that continuous feature development would drive a massive acceleration in paid subscriptions. For a time, it worked; the application became synonymous with digital memory.

The Diminishing Returns of Utility

But what happens when the market for digital note-taking is fully saturated? Once you have digitized note-taking, or built a frictionless pipeline for sending large graphical assets across the internet, the core utility is settled. The user base locks in. The switching costs become massive; exporting thousands of poorly-formatted HTML notes, or retraining a freelance client base to use a different file-transfer interface, is painful enough that churn naturally stabilizes.

At this stage of product maturity, the ongoing relationship between the developer and the user changes. Under the romantic view, the relationship requires continuous updates, new integrations, and user-interface refreshes. The cynical view, dictated by the balance sheet, recognizes that any additional feature is now subject to aggressively diminishing returns. Retaining a massive engineering team to tweak peripheral features does not drive new customer acquisition. If Evernote adds a slightly better tagging interface in year twelve, it does not meaningfully change its growth trajectory; the people who want Evernote already have it. The continuous product innovation has transitioned from a growth engine into a deadweight loss, effectively levying a permanent tax on the app's established lock-in.

This is where the valuation metric shifts from venture capital's revenue multiples to private equity's free cash flow — specifically, EBITDA (Earnings Before Interest, Taxes, Depreciation, and Amortization). Through the lens of EBITDA, that same massive engineering team is no longer a growth engine; it is simply an ongoing OpEx liability that degrades the cash-generating potential of the locked-in user base. If you can maintain the same steady-state revenue while slashing OpEx by 80%, the cash flow generation becomes astronomical.

The Software Maturity Matrix

We can visualize this dynamic by plotting a matrix of product maturity against operational expenditure strategy. On the Y-axis, we have the maturity of the software, moving from a bare-bones prototype searching for a market up to an entrenched utility with deep structural switching costs. On the X-axis, we have the scale of operational expenditure, moving from extreme austerity on the left to massive, continuously funded engineering hubs on the right.

The venture-backed romantic era lives exclusively in the bottom-right quadrant. Low maturity requires high expenditure to discover what works. As the software matures, moving up the Y-axis, the optimal strategic posture should logically shift to the top-left, pairing high maturity with aggressively low expenditure. Most technology companies, culturally hardwired by their founders to keep building, refuse to make this shift. They stay firmly on the right side of the graph, burning margin to fund the illusion of continuous innovation.

Enter Bending Spoons. When the Italian firm recently executed its massive IPO, the public market was underwriting a very specific mechanism: a financial machine designed to forcibly drag mature internet assets from the top-right quadrant into the top-left.

Private Equity for the App Store

This illuminates why the founder's focus on minimizing luck is so structurally revealing. Innovation is inherently lucky; a product team is placing highly expensive bets on unproven consumer behaviors, hoping a new collaborative workspace feature will juice subscription growth. Margin extraction, by contrast, is entirely deterministic. If an acquirer buys a company with predictable recurring revenue and immediately eliminates the vast majority of its fixed costs, the resulting profit materializes with mathematical certainty.

Notice how this operational leverage manifests in practice. When Bending Spoons acquired Evernote, they had zero interest in revitalizing the company's culture or pivoting its product roadmap to compete with modern upstarts like Notion. Rather, they simply laid off nearly all of the company's US staff, moving the minimal required maintenance to lower-cost jurisdictions. They are currently executing the exact same playbook at WeTransfer, announcing plans to slash 75% of the staff immediately after the acquisition closed.

The math is unforgiving. This aggressive reduction in headcount represents the literal translation of a fixed-cost user base into a pure cash-flowing annuity. Bending Spoons operates as a fundamentally different kind of entity: private equity built natively for the App Store. To put it another way, they correctly recognize that in a mature internet ecosystem, you don't build new products; you buy balance sheets and strip the deadweight loss.

It is easy to paint this strategy as villainous, particularly if you view the internet as a playground for perpetual creation. But the reality is that businesses exist to generate returns, and there is simply no money in paying elite software engineers to rearrange the deck chairs on a mature utility app. Bending Spoons isn't killing these products; they are acknowledging that the products are already finished.

This macro transition will undoubtedly accelerate over the next several years, as the definitive end of the zero-interest-rate policy era ensures that the venture capital subsidy for continuous iteration is definitively over. The internet is now old enough to have generated a massive inventory of finished utilities ripe for this exact optimization. Predicting exactly which beloved app will be next on the chopping block is inherently imprecise; as always, the timing depends entirely on the specific patience of the underlying cap table. What is structurally certain is that the migration of value from the product roadmap directly to the balance sheet is only just beginning.

The developers who built Evernote and WeTransfer did their jobs perfectly. They just didn't realize that in the business of zero marginal costs, a finished job means you are now the deadweight loss.

Nice business if you can get it!