Cheap Code Redefines Which Startups Are Buildable
A fundamental shift in software development costs is making previously unfundable businesses viable, challenging traditional venture capital metrics and
The relationship between a startup's headcount and its software output has broken. For decades, investors used team size as a key metric for progress, but small teams can now handle production backends, rendering engines, and multi-country commercial operations that once required staff several times larger.
This shift is not about improved engineer productivity. It is about the collapse in cost for writing ordinary code, wiring systems together, and repetitive implementations. The core change is which types of companies are now possible to build.
When software gets cheap, markets get smaller
The most affected category is products for niche markets of tens of thousands, rather than tens of millions of users. Venture capital historically struggled with these businesses. They were not un-buildable but un-fundable, because the high engineering cost floor exceeded the potential market return. Funds need large outcomes to justify portfolios, so founders were steered toward bigger opportunities.
Lower that cost floor, and these niche products become viable. A team of four can now build one, reach profitability at a scale too small for growth investors, and serve its market for years. What such a business cannot do is generate the massive return a traditional venture fund requires.
Europe is structurally positioned for this shift. The region has fewer megafunds, more fragmented markets that reward specific solutions, and many technical founders who prefer owning most of a real business over a small slice of a speculative giant. These were disadvantages when costs were high but are not clear drawbacks now.
The changed calculus for founders and investors
For founders, the central hiring question has transformed. The useful inquiry is no longer how many engineers are needed to build the product. It is identifying which constraints were ever truly about headcount, because several were not and some no longer exist. Teams that hire primarily to signal progress to investors risk buying coordination overhead, a cost that has not fallen.
For investors, the adjustment is harder. If headcount no longer reliably signals capability, diligence becomes more demanding. Investors must look at what has actually shipped, what is in production, and how systems handle failure. These questions were always better indicators but were more expensive to answer than simply counting people.
The enduring costs of small teams
Advocates for lean teams must be honest about the trade-offs. Small teams have little slack, and slack is where unglamorous, essential work gets done. For instance, every consumer product has a known retention problem. In a ten-person company, the reason it goes unfixed is never a lack of diagnosis but that no one has a free week from more pressing tasks.
In a hundred-person company, that problem becomes someone's full-time job and gets solved. Cheap code does not solve this limitation; it may exacerbate it by making it easier to start the next project instead of finishing the last one.
The honest assessment is this. The lowered cost floor widens the field of possible companies but does nothing to improve focus, judgement, or the discipline to complete projects. These remain expensive, human traits. They now constitute a larger share of what separates successful companies from those that merely exist.
The measure worth watching is not employee count. It is what a company has shipped, what it has finished, and what it has chosen not to do.
