Minimizing Luck: The Bending Spoons Playbook for Small Teams
Bending Spoons hit an $18B IPO by treating luck as a bug to engineer around. Here's what that mindset means if you're building software from Sri Lanka.
Minimizing luck is a strange thing to build a company around, but that is exactly what Bending Spoons co-founder Matteo Danieli credits for a $18 billion Nasdaq debut. In an interview with TechCrunch, he argued that talent and success are only loosely correlated, and that the smart move is to design your business so luck matters less.
I find that framing more useful than the usual "hustle harder" advice, especially if you are building software from a small team in Sri Lanka. So let me unpack what it actually means and where it holds up.
🎲 The luck vs. skill split that matters
Danieli's key claim is a distinction, not a slogan. He splits business outcomes into two phases and treats luck differently in each:
| Phase | How much luck matters | What you can control |
|---|---|---|
| Finding product-market fit (zero to one) | Very high | Which bets you place, how fast you learn |
| Operational excellence (running the thing) | Close to zero | Retention, margins, headcount, execution |
In his words, "Luck plays a big role in finding product-market fit," but it "is irrelevant when pursuing operational excellence."
Key takeaway: You cannot manufacture the lucky break that makes a product click. You can guarantee you run the machine well once it does. Most people obsess over the first half and neglect the second.
That split is the whole insight. It says: stop pretending the risky part is controllable, and stop treating the controllable part as boring.
🛠️ How Bending Spoons actually minimizes luck
The company's method is unglamorous on purpose. Instead of chasing a viral new app, it buys existing subscription products that already have paying users, then runs them tightly. The brands it has acquired include:
- Evernote
- WeTransfer
- Vimeo
- Meetup
- Eventbrite
- AOL
Buying a product with real revenue removes the single biggest gamble in software: whether anyone wants the thing. The product-market-fit lottery is already won by the time Bending Spoons arrives. Its job is the part it can control, which is execution.
The playbook borrows from private equity: acquire an ailing subscription app, cut headcount, and lean on a strong engineering team to keep operations lean. You can argue about the human cost of the headcount cuts, and you should. But the strategic logic is consistent with the "minimize luck" thesis. Every move targets the phase where skill, not chance, decides the result.
The numbers back the discipline up:
| Metric | 2023 | 2025 |
|---|---|---|
| Revenue per full-time employee | $1.12M | $2.57M |
More than doubling output per person in two years is not luck. That is what operational excellence looks like on a spreadsheet.
💡 The failure that taught them this
The philosophy did not come from a business-school textbook. It came from getting burned. Before Bending Spoons, the founders, Danieli, Luca Ferrari, Francesco Patarnello, and Luca Querella, built a social network called Evertale that generated automated life diaries using machine learning. It failed.
The lesson they took from it was blunt: being talented and being right about the tech does not guarantee anyone will care. As Danieli put it, "you don't always find perfect correlation between how talented entrepreneurs are and the success they have, especially from zero to one. Luck is a very big component."
Out of that failure came what he calls "an obsession for finding a strategy that would, as much as possible, reduce the role that luck plays in growth and success."
I like this because it is honest. The founders did not conclude they were geniuses who got unlucky. They concluded that the game itself is luck-heavy at the start, and redesigned their next company to play a different game.
🌐 What this means for a builder in Sri Lanka
You are not going to raise a private-equity war chest and buy WeTransfer. That is fine. The transferable part is the mindset, and it fits a small team better than you might expect.
- Separate your bets from your operations. Treat "will this product find users" as a bet with real odds against it. Do not bet your rent on it. Keep the risky exploration small and cheap.
- Once something works, get ruthless about running it well. Retention, response time, and cost per user are all skill, not luck. This is where a disciplined two-person team can out-execute a distracted twenty-person one.
- Measure output per person. Bending Spoons tracks revenue per employee for a reason. If you bill clients in USD, run your own version of that number. A quick sanity check with our Freelancer USD-LKR Calculator tells you what your effective LKR revenue per head actually is after fees.
- Let failure narrow your strategy, not your ambition. Evertale did not make the founders quit. It made them pick a better game. A dead side project is tuition, not a verdict.
The trap for solo builders is spending months polishing operational excellence for a product that never had fit, or shipping ten half-baked bets and running none of them well. The luck framework tells you which failure you are committing.
📊 What this means for you
Bending Spoons is a controversial company, and cheering an $18B IPO built partly on layoffs would be lazy. But the underlying idea survives the controversy: know which part of your work is a coin flip and which part is a craft, and pour your discipline into the craft.
For most of us, that translates to something small and doable this week. Pick your one thing that already has users, however tiny. Then ask what "operational excellence" would look like for it, and go do that instead of chasing the next lucky idea.
Bottom line: You can't schedule your lucky break. You can decide to be undeniable once it arrives. That choice is available to a one-person team in Colombo just as much as a company ringing the Nasdaq bell.