Bending Spoons Shared Stack Strategy

This is a rollup model where shared plumbing matters more than a shared brand. Bending Spoons is not trying to turn Evernote, WeTransfer, Vimeo, and Meetup into one app. It is moving each product onto the same internal systems for login, billing, analytics, experimentation, and AI, so a small central team can run many very different apps faster and at lower cost while still preserving the user job each app is already known for.1 2 3 4

• The common stack is concrete infrastructure, not a vague platform story. Bending Spoons says Spoon Engine includes more than 50 shared services such as authentication, payments, A/B testing, analytics, and AI inference, and its IPO filing says the portfolio reached 500 million monthly active users.1 2
• Evernote shows what this looks like in practice. The app kept note taking, OCR, web clipping, and tasks, but its sync layer was rebuilt after the acquisition. Evernote later said a new metadata sync system made sync 3x faster, which is the kind of invisible back end upgrade this model is built to repeat.1 5
• The portfolio mix creates reuse opportunities across adjacent workflows. FiLMiC helps capture video, WeTransfer moves big files, StreamYard handles live production, and Vimeo and Brightcove handle hosting and distribution. That lets one AI and infrastructure layer support features like captioning, transcription, translation, and editing across multiple products.1 3 4 6

The next step is less about merging brands and more about standardizing operations, then selling higher priced features on top. As more acquired apps are rewritten onto the same stack, Bending Spoons can ship the same AI feature set, pricing tests, and reliability improvements across the portfolio, which should make each additional acquisition easier to absorb and monetize.1 2 6