Key Takeaways

  • Bending Spoons built an internal operating system of over 50 custom tools over ten years to automate AB testing, user lifetime value (LTV) prediction, and billing across its entire software portfolio.
  • Their proprietary design tool, Diagram, generates production UI code instantly from text prompts while strictly enforcing brand design rules, allowing non-designers to ship interfaces.
  • An internal Slack agent called Alt Spooner operates with individual employee permissions to pull data, inspect system logs, and write bug fixes in minutes.
  • The general manager of Evernote used Alt Spooner to diagnose and fix a live production bug in three minutes without engineering intervention.
  • Centralized tooling beats team autonomy when scaling software acquisitions: standardizing infrastructure lets tiny teams run massive legacy applications.

Building a Fifty-Tool Operating System

Most software rollups acquire companies, fire staff, and let the remaining team hack together spreadsheets to survive. Bending Spoons took the opposite path. Over the past decade, co-founder Luca Ferrari invested in building a proprietary software stack to run every app they acquire under one roof.

As Ferrari explained: “We have invested pretty heavily at Bending Spoons over this point over a decade to develop basically you could look at it as an operating system at this point over 50 proprietary tools that run almost everything that we do or at least supported through automation.”

Instead of each acquired app managing its own billing infrastructure, analytics pipeline, and conversion rate tests, every product plugs directly into this central engine. When Bending Spoons acquires an app like Evernote, the product adopts these automated systems immediately. The operational machinery handles LTV forecasting, paywalls, and user experiments automatically, freeing the core team to focus purely on product improvements.

Turning Every Employee into a Designer and Debugger

With recent advances in large language models, Bending Spoons expanded this internal operating system with specialized AI tools designed to eliminate organizational bottlenecks. One of these tools is Diagram, an automated UI generator.

“You can just tell the tool to pull up screens for the app you're working on, say it's Evernote for the relevant features, and then you guide it as it produces new versions of those interfaces,” Ferrari said. “And it will do so by automatically following the design guidelines that the head designer for that tool has laid out in some document somewhere.”

By encoding design system rules into the tool, Diagram removes the traditional handoff delay between product planning and visual assets. As Ferrari noted, “it enables doing design work for people who before couldn't, like product managers, software engineers, growth managers.”

They applied the exact same philosophy to technical operations with an AI agent called Alt Spooner. Built directly into Slack, the bot mirrors the user's specific system access levels.

“It's basically an agent that lives in Slack that has by design the very same access you do as an individual in the company,” Ferrari explained.

This architecture lets non-technical leaders troubleshoot code directly. Ferrari pointed out that the general manager for Evernote used Alt Spooner to pinpoint and resolve an error in real time: “And so she, the general manager for Evernote, in maybe 3 minutes essentially identified and fixed a bug, something that would have taken days before.”

Why Centralized Tooling Beats Team Autonomy

Silicon Valley dogma dictates that product teams need complete autonomy: pick your own tech stack, choose your own analytics vendor, and design your own workflow. That autonomy works well for zero-to-one exploration, but it creates massive overhead once you manage multiple products.

Ferrari's model proves that radical centralization unlocks efficiency that decentralized startups cannot match. When 50 core business functions run on automated internal systems, a single general manager can operate a massive app like Evernote with a lean engineering squad. The leverage comes from replacing cross-team meetings with shared software.

What to Do With This

Audit your team's most frequent cross-functional handoffs this week, specifically requests between product managers, designers, and developers. Pick one recurring task, like error log analysis or design variant generation, and build an internal script or agent with strict permissions to handle it. If an operational question takes more than five minutes of human coordination to answer, write software to answer it instead.