SaaS
Reviving Neglected Software Is a Proven Market, the Tooling to Build That Factory Isn't
Published: 2026-07-05
The Problem
Neglected SaaS and apps sell for one to two times revenue everywhere, but there is no tooling that lets a tiny team run the whole loop, diligence, service migration, billing consolidation, pricing experiments, so the revive-and-run business stays open only to large acquirers like Bending Spoons.
Why Now
As AI strips out engineering and operations labor, one or two people can now run several products at once, and cash-starved small software keeps coming up for sale. Productize the shared operating OS that Bending Spoons keeps in-house and you sell it to a new buyer class: indie acquirers and micro-PE.
Recommended Talent
An engineer who has run several SaaS products at once and unified billing, auth, and support; someone fluent in software M&A diligence and valuation; and someone wired into the indie-acquirer and micro-PE communities.
The Problem
Bending Spoons started in Milan in 2013 and buys software that has stalled or been left to rot, then revives it. It has acquired more than 50 products, including Evernote, WeTransfer, Vimeo, AOL, and Eventbrite, and in July 2026 it went public on Nasdaq at a valuation above $18 billion. Read the IPO filing and the reporting together and the real weapon is not any one app but the method. Every acquisition gets folded onto a single shared operating platform in Milan that pools engineering, billing, marketing, and support; industry analysis puts the overhead it removes in that step at 70 to 80 percent. The catch is that the method is locked inside one company. Neglected SaaS and apps selling for one to two times revenue are everywhere, but the operating muscle to buy and revive them belongs to large acquirers like Bending Spoons. A solo developer or a team of two or three who wants to run the same playbook has no tooling that ties diligence, service migration, billing consolidation, and pricing experiments into one loop.
Why Now
Now is the moment because the targets and the ability to execute got cheap at the same time. The numbers in Bending Spoons’ filing compress the shift: the share of its code changes authored by AI went from under 10 percent in Q1 2025 to over 90 percent a year later, and revenue per employee jumped from $1.12 million in 2023 to $2.57 million in 2025. It runs dozens of acquired products with far fewer people than before. The same tools are now available outside big companies. As AI coding agents and managed infrastructure spread, operations that used to need a whole team can be carried by one or two people. On the other side, supply is flooding in. With the funding market frozen, software that stopped growing but kept its loyal users and revenue is coming up for sale cheap, and marketplaces like Acquire.com and Flippa have made that deal flow visible. The market itself is already proven by Bending Spoons’ $18 billion listing. What is missing is the tooling that carries the method outside the big acquirers.
How to Build It
The core move is to productize the shared operating OS that Bending Spoons keeps in-house. Let an acquired product, wherever it lives, migrate onto one stack for billing, auth, support, and growth experiments, then A/B-test price on top of it to convert loyal users into subscribers. Do not try to hold everything at once; start narrow. Pick one small B2B SaaS and build the migration tooling that moves its scattered payments, logins, and support onto the shared stack first. Then add acquisition sourcing and valuation (revenue multiples, churn, a technical-debt read), and finally a portfolio dashboard that shows every product’s metrics on one screen.
flowchart LR
A[Neglected software] -->|cheap buyout| B[Turnaround platform]
B -->|shared ops stack| C[Overhead cut]
B -->|pricing experiments| D[Subscription conversion]
C --> E[Cash flow]
D --> E
E -->|reinvest| A
Monetization splits two ways. You can sell only the tooling as a SaaS subscription, or you can acquire and revive products yourself as a micro-PE firm and take equity and fees on the outcome. The first makes every indie acquirer a customer; the second uses the tooling as a weapon to become a miniature Bending Spoons.
Success Criteria
First, migration friction. If moving an old codebase onto the shared stack becomes bespoke surgery every time, it will not scale; the team that makes that migration close to automatic wins. Second, real cost cuts. If the shared OS does not actually remove duplicated spend, acquirers just keep running products separately. Third, deal flow. Without sourcing that finds good targets cheap, even great tooling has nothing to run on. When tooling, sourcing, and operations lock into one loop, the revival factory turns.
Related Content
Build this together
Find collaborators