Key Takeaways

  • Bending Spoons scaled from a failed AI startup with $40,000 in leftover capital into a tech conglomerate approaching a $4 billion revenue run rate.
  • Ferrari avoids early-stage product development because fixing a broken, mature asset takes the same operational effort as fixing a small one, but delivers vastly larger returns.
  • The company targets mature businesses that have operated for 10 to 20 years where founders want an exit, replacing legacy codebases with internal technology stacks.
  • Acquisitions require a minimum five-to-six-year directional visibility on earnings before deal teams commit capital.
  • Every potential acquisition must pass the Bending Spoons M&A Screening Criteria across scale, predictability, and operational upside.

The Bending Spoons M&A Screening Criteria

  • Scale: Target relatively few sizable companies rather than many small assets, because operational transformation effort does not scale linearly with revenue.
  • Earnings Predictability: Target businesses where financial earnings and cash flows can be directionally projected with confidence for at least the next 5 to 6 years.
  • Multi-Lever Value Creation Potential: Look for assets with clear opportunities to drive upside across technology migration, organizational restructuring, product improvements, monetization optimization, and marketing.

When This Works (and When It Doesn't)

This framework fits serial software acquirers who run centralized engineering and marketing operations. If you have built proprietary internal tech stacks and lean operational units, you can strip away decades of technical debt from an acquired asset. As Ferrari observed: “The amount of time and effort it takes to transform a business, we have found it doesn't really scale linearly with revenue. So, we're much better off acquiring relatively few sizable companies than a million small ones.”

It fails when an acquirer lacks deep operational talent and acts merely as financial engineering. If you cannot rewrite an application codebase or redesign its monetization funnels in-house, buying mature software assets turns into managing expensive decline. It also breaks down in hyper-nascent markets where product-market fit shifts every six months, making five-year cash flow projections impossible.

What to Do With This

If you are evaluating whether to build a new product line internally or acquire an existing one, run this filter on your target list:

First, check your target's operating history. Look for software tools that launched a decade ago, achieved product-market fit, but stalled because the original founders moved on or stopped shipping. Confirm whether you can model its subscription renewals over the next five years.

Second, list the exact operational upgrades you will execute within 90 days of closing. If your only plan is cutting hosting costs, walk away. You need at least three distinct levers, such as migrating off legacy database infrastructure, rebuilding the checkout conversion flow, and restructuring paid user acquisition. If the asset cannot support a multi-lever overhaul, leave it alone.