The Hockey Stick Illusion: Why Chasing Infinite Growth Produces Finite Software

Somewhere in a conference room in San Francisco—or more likely on a Zoom call with a Sand Hill Road investor—a founder is being asked the same question that has shaped a generation of American software: how do you get to a billion users?

It is the wrong question. And the fact that it remains the central question of technology entrepreneurship tells us something important about why so much modern software is, frankly, not very good.

The Ideology of Scale

Venture capital is not simply a financing mechanism. It is an ideology. The model is predicated on a specific theory of value creation: invest in a small number of companies, expect most to fail, and structure the few successes to return multiples large enough to cover every loss and still generate outsized returns. This math requires that successful investments do not merely grow—they must grow exponentially, capturing markets rather than serving niches.

This logic made sense in an era when software distribution was genuinely constrained by physical media and geographic reach. Building a platform that could scale to millions of users required enormous upfront capital investment in infrastructure. The VC model was, in that context, a reasonable solution to a genuine problem.

That era ended some time ago. Cloud infrastructure, open-source tooling, and modern development frameworks have reduced the capital cost of building and distributing software by orders of magnitude. A two-person team today can build and ship a product to global users for a fraction of what it cost a decade ago. The financing constraint that justified the VC growth model has largely dissolved.

The ideology, however, persists.

What Scale Pressure Does to Software

When a company raises venture capital, it accepts an implicit obligation: deploy that capital to achieve growth metrics that justify the next round of funding. This obligation reshapes every product and engineering decision in ways that are rarely acknowledged openly.

Feature bloat is the most visible symptom. When growth is the primary metric, adding features is almost always preferable to refining existing ones. New features generate press coverage, attract new user segments, and justify product team headcount. The result is software that accumulates capabilities like sediment—layer upon layer of functionality that individually made sense at the time of development but collectively produces an experience that is slow, confusing, and difficult to maintain.

Slack is an instructive example. The product that launched in 2013 was genuinely elegant—a focused, fast messaging tool that felt like a revelation compared to the enterprise software it displaced. The Slack of 2025, burdened with Salesforce integrations, AI features, huddles, clips, canvas documents, and a navigation structure that requires orientation training, is a materially different product. Whether it is a better product is a question reasonable people disagree about. What is not in dispute is that the growth imperative drove its expansion.

There is also the matter of reliability. Software built to scale fast tends to accumulate technical debt at a proportional rate. Engineering resources that could address underlying architecture problems are perpetually redirected toward the next growth feature. The result, familiar to anyone who has spent time in a VC-backed startup's engineering organization, is a codebase that becomes progressively harder to maintain, debug, and extend—precisely as the company's ambitions are growing most aggressively.

The Counter-Movement Taking Shape

Not everyone has accepted this as the natural order. Over the past decade, a loosely affiliated movement of founders and developers has been quietly demonstrating that profitable, sustainable software businesses can be built without venture capital—and that the software they produce is often better for it.

Basecamp, the project management company founded by Jason Fried and David Heinemeier Hansson, has been the most vocal advocate for this approach. The company has operated profitably for over two decades, rejected acquisition offers, and built products used by millions of businesses—without ever taking a dollar of outside investment. Their public arguments against the VC growth model, articulated in books like Rework and It Doesn't Have to Be Crazy at Work, have influenced a generation of founders who were skeptical of the conventional playbook but lacked a credible alternative framework.

The bootstrapped software movement—companies that grow from revenue rather than investment—has developed its own infrastructure of communities, conferences, and media. MicroConf, a conference for self-funded software founders, has grown substantially over the past several years. Publications focused on indie software businesses have found engaged audiences. The narrative that VC funding is a prerequisite for serious software entrepreneurship is crumbling.

More recently, the concept of the "lifestyle business"—long used dismissively by venture investors to describe companies insufficiently ambitious to pursue exponential growth—has been reclaimed as a legitimate and even admirable model. A software company that generates $3 million in annual revenue, employs a small team well, serves its customers reliably, and never needs to raise a Series A is not a failed startup. It is a functional business.

What This Means for Software Quality

The connection between funding model and software quality is not absolute. Venture-backed companies have produced excellent software, and bootstrapped companies have produced mediocre software. The relationship is probabilistic rather than deterministic.

But the incentive structures matter. A company that answers to customers—whose continued subscription revenue is the only source of funding—is structurally more aligned with software quality than one that answers to investors whose primary interest is an exit event. Customers leave when software becomes unreliable or difficult to use. Investors, particularly in early rounds, are primarily interested in growth metrics that may be only loosely correlated with product quality.

This alignment problem is not a character flaw of venture investors. It is a structural feature of the model. And it produces predictable outcomes: software optimized for acquisition metrics rather than user experience, reliability sacrificed for feature velocity, and products that are retired or fundamentally altered when they no longer serve the growth narrative—regardless of how much their users depend on them.

A Different Question

The question worth asking in that conference room—the one that would actually produce better software—is not how you get to a billion users. It is whether the people who use your software find it genuinely useful, whether you can sustain building it over time, and whether the business you are building will still exist and still be serving its customers a decade from now.

Those questions do not produce hockey stick charts. They produce software worth using.