Source
The a16z Show — How Bending Spoons Built a $20 Billion Compounder | Luca Ferrari (November 1, 2026) ·
at 35:33 ▸
When this applies
when benchmarking an organization's pace of adopting an available automation technology against peers
The takeaway
Set an explicit minimum adoption threshold for a proven, rapidly maturing technology and treat falling below it as a red flag, not a matter of taste.
Why it works
Because AI coding, support, and data-processing tools have rapidly matured to near-full task coverage within specific domains (support, data fetching/cleaning, coding), companies lagging far behind this adoption curve are leaving clear productivity gains unrealized.
One level up
Once a technology's capability curve has clearly outpaced an organization's usage, lagging adoption becomes a diagnosable failure, not a defensible caution.
Where it stops holding
This stops working for domains where AI has not yet reached comparable maturity, or for tasks with genuinely high stakes/low AI reliability where human-only execution remains justified.
Detail
rule: No good software company should be below 70% AI-written code today; everyone should be converging toward 100%.
threshold: 70% minimum; Bending Spoons itself is at 94% as of the interview, up from 0% two years prior.
rationale: Customer support and data science have already shifted to AI performing the bulk of execution work while humans shift to architecture/oversight roles, showing the ceiling is achievable.
In their words
Some companies, you know, depending on how aggressive you want to be, you could be, if you're a good company, you could be at 70 and 99, but no good company should be, I don't know, below 70 right now, in my view.