Around 2008, Jason Fried and David Heinemeier Hansson were running a software company that had every reason to chase venture capital and build a sales team. They had a product people loved, a growing user base, and a market that was expanding fast. Instead, they hired slowly, kept the team in the dozens, and told investors no.
Investors thought they were leaving money on the table. They weren’t wrong, exactly. But they were measuring the wrong thing.
Basecamp, the project management tool, has never had more than around sixty employees. It has served millions of users. It has been profitable every year of its existence. And it has done all of this without a single round of venture capital. If you handed that outcome to most startup advisors before the fact and asked them to predict the path that led there, almost none of them would describe what Basecamp actually did.
The Setup
When 37signals (the company behind Basecamp) launched the product in 2004, the conventional wisdom was already calcifying: find product-market fit, raise capital, hire fast, grow faster. The SaaS playbook was being written in real time, and most people writing it assumed that scale was the goal. More customers, more features, more headcount, more funding.
37signals looked at that playbook and wrote a different one. Fried and DHH published it as a book called Rework in 2010, and it sold over a million copies, which tells you something about how many people were quietly skeptical of the growth-at-all-costs model but lacked a vocabulary to argue against it.
Their operating thesis was simple and, at the time, genuinely contrarian: a small company that makes a profit is not a small company that failed to become a big one. It’s a different kind of success, and in many cases a harder one to achieve.
What Happened
Basecamp didn’t stay small by accident. The constraint was intentional and actively defended.
When growth created pressure to expand the team, they pushed back. When feature requests piled up, they said no more often than yes. When Basecamp the product started competing for attention with their own newer tools, they spun things off cleanly rather than building an ever-larger platform. (They eventually renamed the parent company Basecamp, then Hey, then back again, but the underlying discipline held.)
The product itself reflects this philosophy in ways that frustrated some customers and earned fierce loyalty from others. Basecamp doesn’t try to be everything. It doesn’t have the granular time-tracking of tools built for agencies, or the complex workflow automation of enterprise project management software. What it has is a coherent set of features that work the way the company intended, built by a team small enough that everyone knows what the product is supposed to feel like.
That coherence is expensive to maintain at scale. Most companies find it easier to add than to hold the line. Deleting a feature is the hardest call in engineering, and the pressure to add features never stops. Staying small is partly what makes it possible to keep saying no.
The revenue picture is instructive without being precise, since Basecamp is private and doesn’t publish numbers. But the founders have been open about the company being profitable throughout its life, and profitable companies with millions of users and sixty employees are generating meaningful returns per person. The math is straightforward even without the exact figures.
Why It Matters
Basecamp is not a unicorn story. It will never be. That’s the point.
The venture capital model requires outlier returns because most investments fail. A fund that backs a hundred companies needs a handful of enormous exits to make the math work. That model is legitimate, but it has a side effect: it makes the entire startup ecosystem treat scale as a proxy for quality. If you’re not growing fast, something must be wrong.
What Basecamp demonstrated, over two decades of operation, is that this assumption is wrong. Fast growth is one path to one kind of outcome. Deliberate constraint is a path to a different kind of outcome. Neither is inherently superior. But the industry’s reflex to treat scale as the default definition of success causes real harm to companies that would be perfectly healthy if they just stopped trying to be something they’re not.
The companies that over-hire in pursuit of growth, then lay off half the team when the growth doesn’t materialize, aren’t failing because they lacked ambition. They’re often failing because they adopted a growth model that never fit their actual business. The metrics that got you to Series A will kill you at B is a problem, but the deeper problem is assuming that reaching B is the goal in the first place.
What We Can Learn
The Basecamp story has a few lessons that are specific enough to be useful.
First: constraint as strategy requires conviction. Staying small while a market is growing feels like losing. You watch competitors raise rounds and hire aggressively and get press coverage, and the social pressure to follow is enormous. Fried and DHH were vocal about their choices partly because they had to be. If you’re going to swim against the current, you need to know why, clearly enough to say it out loud when people push back.
Second: the product and the company size are connected. Basecamp’s product coherence is not separate from its headcount discipline. A team of sixty people building one core product has fundamentally different conversations than a team of six hundred building a platform. The focus shows in the work. This isn’t a universal argument against large companies, but it’s a real argument for thinking carefully about whether the thing you’re building benefits from the focus that smallness enables.
Third: profitability is a strategy, not just an outcome. Many early-stage companies treat profitability as the thing that happens after growth. Basecamp treated it as a constraint that shaped growth, which meant they never had to answer to investors or manage cash crises during downturns. That independence is worth something that doesn’t show up on a cap table.
Fourth, and maybe most practically: there is a real market for software that does less, better. The enterprise SaaS market trends toward more features, more integrations, more configuration. Basecamp found, and has kept for twenty years, a substantial customer base that specifically does not want that. Staying small let them stay focused on those customers rather than chasing enterprise contracts that would have required building a different product and a different company.
The startup that refuses to scale is often the one worth watching because it’s made a harder choice. Growing fast is hard, but it’s a known problem with known solutions. Staying deliberately small, staying profitable, and staying focused while everything around you tells you to do the opposite requires a different kind of discipline. It requires knowing what you’re building and who it’s for, and being willing to say no to everything that doesn’t fit.
Basecamp knew. Most companies, given the same opportunity, would have hired the sales team.
