In February 2014, a software company with fewer than 50 employees did something that most investors, most boards, and most founders would consider clinical insanity: it killed off every product it made except one, changed its name to match that surviving product, and told the world it was done growing. No new lines. No adjacent markets. No empire. Just a single project management tool called Basecamp, serving roughly three million accounts, run by a company that had been profitable for over a decade and had never taken a dime of venture capital — well, almost never. Jason Fried, the CEO, wrote a blog post explaining the decision. He could have framed it as strategic focus. Instead he framed it as relief. "We've strayed from the path," he wrote. "Now we're going back."
The announcement bewildered the tech industry not because the company was famous — it was, in certain circles, intensely so — but because the logic inverted every incentive that governed the rest of the software business. The prevailing wisdom held that SaaS companies should be multi-product platforms, that growth came from expansion, that employees were an asset to be accumulated, that capital was cheap fuel for an ever-accelerating flywheel. Basecamp — or 37signals, as it was still known at the time — had spent fifteen years arguing the opposite from a position of quiet prosperity: that small was a feature, not a bug; that profitability was a prerequisite, not a destination; that a company could say no to nearly everything and still matter.
What made the argument stick was the receipts. While venture-backed project management competitors burned through hundreds of millions of dollars chasing growth at any cost, Basecamp had been profitable since roughly its second year of existence. It had never laid anyone off. It paid its employees well, gave them four-day summer workweeks, covered their vacations, and still generated enough cash to fund not just itself but the development of a programming framework — Ruby on Rails — that would go on to power the first versions of Twitter, Shopify, GitHub, Airbnb, and over a million other web applications. All from a company that, at its peak, employed around 75 people.
This is the paradox at the center of the Basecamp story: a company that deliberately chose to be small became, through the software it gave away for free and the ideas it gave away even more freely, one of the most influential forces in the modern internet economy. Not the biggest. Not the richest. But arguably the most ideologically potent — a living, profitable, maddening counter-argument to the entire venture-backed growth model. And also, as events in 2021 would prove, a company whose own internal contradictions could blow up with a force that no amount of philosophical coherence could contain.
By the Numbers
37signals / Basecamp
25+Years in business (founded 1999)
~75Employees at peak
$0Venture capital raised (post-Bezos buyback)
$100M+Estimated annual revenue (reported range)
3.5M+Basecamp accounts created (by 2023)
1M+Web apps built on Ruby on Rails
5Books published by founders
~20Employees lost in one week, April 2021
The Web Designer Who Didn't Want to Be Embarrassed
Jason Fried grew up in the Chicago suburbs, the son of a gemologist — a trade that required discerning the real from the imitation, a skill his son would apply to business dogma with gleeful ruthlessness. Fried started 37signals in 1999, at 25, as a web design consultancy. The name was an homage to a list of thirty-seven candidate signals detected in a search for extraterrestrial intelligence — promising transmissions from deep space, none of which turned out to be aliens. The metaphor was accidental but apt: Fried would spend the next quarter-century transmitting signals about work and business that a certain audience found revelatory and a larger one found confounding.
The consultancy was small. Three, four people. They designed websites for clients — nothing exotic, nothing that required venture backing or a Stanford pedigree. But they had a problem that Fried later described with characteristic bluntness: they kept embarrassing themselves. Projects would slip. Deadlines would pass. Clients would ask for status and the answer was a shrug. Email threads multiplied. Spreadsheets diverged. "Born out of desperate necessity to stop embarrassing ourselves in front of our clients," the company's own origin story reads, "the story of how Basecamp was born is likely your story, too."
It was 2003 when Fried decided to solve the problem. Not by buying software — the existing project management tools were enterprise monstrosities designed for companies a hundred times 37signals' size, suffocated by Gantt charts and resource allocation matrices. Instead, he decided to build something. A tool that would let his small team share files, track milestones, and communicate with clients in a single place. Something simple enough that everyone would actually use it.
He needed a programmer. He found one in Copenhagen.
The Programmer Who Raced Cars and Hated Meetings
David Heinemeier Hansson — DHH, as the internet has long known him — was a Danish business student at the Copenhagen Business School when he discovered Fried's writing online. Before that, he'd been writing about video games on the internet since he was a teenager, had done cold-calling at a web design shop ("Hey, sir, would you like a website?" — this was 1997), and had worked briefly for a venture-backed startup during the dot-com bubble that left him with a visceral, permanent distaste for what he saw as performative business theater: the all-hands meetings, the hockey-stick projections, the burn rate as badge of honor.
He was studying Michael Porter's Competitive Strategy when he emailed Fried. He'd been reading 37signals' blog, Signal v. Noise, which was already developing a cult following for its contrarian takes on web design. Fried hired him — part-time, remote, from Denmark, in 2001. The relationship was improbable: a self-taught Chicago designer and a Danish business student who programmed on the side, collaborating across six time zones with no office, no formal process, and no venture capitalist telling them what to build.
What DHH built was not just Basecamp. In the process of building Basecamp, he created a web application framework — a set of programming tools and conventions — that he extracted from the project and released as open-source software in July 2004. He called it Ruby on Rails. The framework was opinionated, elegant, and ferociously productive. It allowed a single developer to build in weeks what had previously taken teams months. Rails was so good at enabling rapid web development that it became, arguably, the single most important open-source project of the Web 2.0 era. Tobias Lütke used it to build Shopify. Jack Dorsey and Ev Williams used it to build the first version of Twitter. Tom Preston-Werner and Chris Wanstrath used it to build GitHub. The framework powered Airbnb, Kickstarter, Hulu, Square, Zendesk, and Twitch in their early, formative iterations.
I worked partly at a web design shop, where I did such fun things as cold calling for a while. Just calling people up. Hey, sir, would you like a website? The wildest thing was that we actually sold some.
The irony was cosmic. Basecamp — the product — would remain a modestly scaled, deliberately small business. Ruby on Rails — the byproduct, the open-source offshoot, the thing DHH gave away for free — would underpin hundreds of billions of dollars in enterprise value across the technology industry. 37signals chose to be small. Its intellectual output was enormous.
The Bezos Investment That Wasn't Really an Investment
In 2006, something unusual happened.
Jeff Bezos — personally, not through Amazon — invested in 37signals. The amount has never been publicly disclosed, but reports have placed it in the low single-digit millions. It was, by any standard, a tiny check for a man building the world's largest online retailer. And it was the only outside capital 37signals would ever accept.
The investment was notable less for the money than for what it signaled. Bezos was not buying a growth-stage SaaS company with a path to IPO. He was buying a stake in a philosophy. Fried has said that Bezos was interested in 37signals precisely because it was profitable, because it was small, and because it was run by people who had strong opinions about how business should work. For Bezos, who famously told Amazon shareholders that he'd rather be misunderstood than follow the crowd, this was recognizable. For 37signals, it was validation without strings. The investment came with no board seat, no operational control, no obligation to grow.
Later, in a move that underscored the company's allergy to external capital, 37signals would buy back Bezos's shares. The precise timing and terms of the buyback remain private, but the message was loud: even the money of the world's richest man was, eventually, a constraint they preferred to live without.
Profitable on Arrival
Basecamp launched publicly in February 2004. It was not the company's first product — 37signals had previously built a few simple web-based tools — but it was the product that changed everything. Within weeks, paying customers started signing up. The pricing was simple: tiered plans based on the number of projects, starting at $24 per month. No per-user charges. No complex enterprise licensing. No sales team.
The growth was organic and immediate. By the end of 2004, Basecamp was generating enough revenue that 37signals could stop doing client work altogether. Think about what that means: a web design consultancy built an internal tool, released it to the public, and within a year was so profitable from subscriptions that the original business — the thing that paid the bills — became unnecessary. The entire company pivoted to being a software product company, funded not by investors but by customers who paid modest monthly fees because the product was useful.
This is the thing that made Basecamp different from nearly every other SaaS story of the era. There was no "pre-revenue" phase. No years of burning cash to acquire users at negative unit economics. No Series A, Series B, Series C death march toward an IPO that might or might not justify the burn. The product was profitable essentially from launch. The business model was a subscription. The marketing was the founders' writing.
Key milestones in 37signals / Basecamp history
1999Jason Fried founds 37signals as a web design consultancy in Chicago.
2001David Heinemeier Hansson hired part-time from Copenhagen; begins building internal project management tool.
2004Basecamp launches publicly (February). Ruby on Rails extracted and released as open source (July).
2005DHH moves to Chicago. 37signals stops client work entirely; becomes a product company.
2006Jeff Bezos invests (personal capital, undisclosed amount). Additional products launched: Campfire (group chat), Highrise (
CRM).
2010REWORK published; becomes a New York Times bestseller.
2014Company renames itself Basecamp; kills all products except the flagship. Highrise, Campfire, Backpack retired from active development.
The Publishing Company That Happens to Make Software
Most software companies have a marketing department. 37signals had a worldview, and the marketing took care of itself.
Between 2006 and 2018, Fried and DHH published five books:
Getting Real (2006), a manifesto on building web applications with small teams;
REWORK (2010), a New York Times bestseller that distilled the company's contrarian management philosophy into aphoristic essays;
Remote: Office Not Required (2013), which argued for distributed work years before COVID-19 made it a necessity;
It Doesn't Have to Be Crazy at Work (2018), an argument against the cult of overwork; and
Shape Up, a product development methodology book that codified their six-week build cycle. The titles weren't subtle. Neither was the advice.
REWORK sold millions of copies. It was the kind of business book that people either loved or hated — short chapters, declarative sentences, zero nuance. "Planning is guessing." "Meetings are toxic." "Workaholism is stupid." The prose felt like a manifesto written on Post-it notes, and for a generation of small business owners and bootstrapped founders, it was liberation theology: permission to be small, to be profitable, to say no to the growth-or-die imperative that defined Silicon Valley.
We don't like to look too far ahead. We work in six-week cycles. At the end of a cycle, you ship what you've got or you move on.
The books were marketing in the purest sense: they attracted customers who shared the philosophy. If you believed that work should be calm, that meetings were a waste, that 40 hours a week was enough — and you needed a project management tool — you bought Basecamp. The product and the ideology were inseparable. The company's blog, Signal v. Noise, functioned as a perpetual publishing machine, generating organic traffic and ideological allegiance simultaneously. DHH's technical writing on Ruby on Rails brought developers into the ecosystem. Fried's management writing brought business owners. Together, they created a content moat that no amount of paid acquisition could replicate.
The Shape of the Work
The most distinctive operational contribution of 37signals to the broader software industry was not a product but a process. Ryan Singer, who served as the company's head of strategy, codified it in
Shape Up: Stop Running in Circles and Ship Work that Matters, published in 2019. The methodology rejected both the waterfall and
Agile frameworks that dominated the industry.
The core idea was radical in its simplicity. Work was organized in six-week cycles — long enough to build something meaningful, short enough to prevent projects from spiraling into indefinite timelines. Each cycle began with a "pitch" — not a spec, not a user story, but a description of the problem and a rough solution, with explicit acknowledgment of what was out of scope. Designers and programmers worked in small teams of two or three. There were no standups, no daily check-ins, no sprints within the cycle. At the end of six weeks, you shipped what you had or you stopped. No extensions.
Between cycles, the company had a two-week "cooldown" period — time for fixing bugs, exploring ideas, and recovering from the intensity of building. The entire rhythm prevented the chronic problem of most software organizations: the project that was "almost done" for months, consuming resources and morale without producing value.
Fried explained the philosophy with characteristic impatience: plans were guesses, long-term roadmaps were fictions, and the only honest commitment a company could make was to the work directly in front of it. "We work in six-week cycles," he told the REWORK podcast. "At the end of a cycle, you ship what you've got or you move on."
The Shape Up methodology was given away free on the 37signals website — another instance of the company creating enormous value it never directly captured. Product teams at companies far larger than 37signals adopted the framework. It became an alternative gospel in product development circles, particularly among teams that had grown disillusioned with the ritualistic overhead of Scrum.
The Great Renaming, and the Products That Died
By 2014, 37signals had accumulated a portfolio of products: Basecamp (project management), Highrise (CRM), Campfire (group chat), Backpack (information organizer), Ta-da List (to-do lists), Writeboard (collaborative writing), and a few others in various states of maintenance. For a company that preached simplicity, the product sprawl was becoming its own kind of complexity.
Fried and DHH decided to kill it all. Not gradually, not through a slow sunset, but in a single, public declaration. They would focus the entire company on Basecamp — the core product, the thing that generated most of the revenue, the tool that had created the business in the first place. They would rename the company Basecamp. They would stop developing Highrise, Campfire, and everything else, keeping them alive in maintenance mode for existing customers but investing no further energy.
The decision was covered by the Harvard Business Review, which noted its rarity: "Unless you follow tech companies, you might have missed the startling announcement by collaboration and communications software maker 37signals that it has decided to refocus the entire company on a single core product." The HBR framing was characteristically restrained. The tech press was more blunt: this was a company deliberately choosing to be smaller than it could be.
What made the decision unusual was not that a company killed underperforming products — that happens routinely — but that some of these products were performing well enough to sustain their own teams. Highrise had loyal users. Campfire had pioneered real-time group chat before
Slack existed. (The irony of Campfire's premature retirement would sharpen considerably when Slack launched later that year and eventually sold for $27.7 billion.) The founders were not cutting losses. They were cutting possibilities.
HEY, and the Fight with Apple
In 2020, 37signals launched HEY, an email service. If Basecamp was a quiet rebellion against project management bloat, HEY was a loud one against email's capture by advertising surveillance. The product reimagined email from scratch: no tracking pixels, no algorithmic sorting, a screening process that let users decide who could reach their inbox, and a pricing model of $99 per year for personal email.
The product was good. The launch was overshadowed by a fight.
Apple rejected HEY's iOS app update from the App Store, citing a rule that required apps offering subscriptions to use Apple's in-app purchase system — which took a 30% commission. DHH was furious and public about it, turning the dispute into a broader argument about platform power and the "Apple tax." The timing was fortuitous: the European Union was already investigating Apple's App Store practices, and Epic Games was in the early stages of its own legal battle. DHH's complaints became Exhibit A in the emerging case that Apple's platform monopoly harmed developers and consumers.
Apple eventually allowed HEY into the App Store after 37signals added a limited free tier, satisfying the letter of the rules without conceding the principle. But the incident cemented DHH's reputation as the tech industry's most articulate and least diplomatic critic of Big Tech gatekeeping — a role he seemed to relish at 200 miles per hour. (He is, literally, a professional race car driver, having competed in the 24 Hours of Le Mans and the World Endurance Championship. The man's appetite for confrontation was not purely rhetorical.)
The Third That Left
The crisis came fast and from within.
In April 2021, Fried published a blog post announcing several internal policy changes at Basecamp: no more discussion of societal and political issues on company platforms; no more "paternalistic benefits" like wellness and fitness programs; no more committees (including one that had been working on diversity, equity, and inclusion); no more 360 reviews; and a refocusing on the company's core purpose — "we make software." The language was Fried at his most declarative: "It's become too much. It's a major distraction. It saps our energy and redirects our dialogue towards dark places."
The backstory, as reported by Casey Newton and others, was more complicated than the blog post suggested. For years, some Basecamp employees had maintained an internal list of customer names they found funny — many of which were ethnic names of Asian or African descent. When the list came to broader attention within the company in early 2021, it triggered an agonized internal reckoning. A committee was formed to address diversity and inclusion issues. Angry threads proliferated on the company's own internal Basecamp software. Emotions ran hot.
When I talked to employees, what they told me was all of those discussions that they'd been having internally were really about the company itself and how the company could be better and be a more just and equitable organization.
From Fried's perspective, as he later explained, the internal discussions had spiraled beyond productive disagreement into something toxic — "a lot of tension internally, a lot of people distrusting one another." He felt the company was getting away from its founders. The policy changes were, in his telling, an attempt to pull back control and refocus on the work. "I didn't get into this business for this reason," he said on the 21 Hats podcast. "I got into this business to build things, to make things with people who wanted to make things."
The response was seismic. Roughly 20 of the company's 57 employees — about a third — chose to leave, many accepting generous severance packages of up to six months' pay. The departures were public, emotional, and extensively covered. For a company that had literally written the book on calm workplaces —
It Doesn't Have to Be Crazy at Work — the irony was excruciating. The thing that blew up Basecamp wasn't a competitor or a market shift or a failed product. It was an argument about what kind of place it was supposed to be.
We certainly didn't anticipate what was going to happen, which is that about a third of the company decided to leave over this decision. The business didn't suffer at all, which is really interesting.
That last line — "the business didn't suffer at all" — was the most revealing detail. Revenue didn't decline. Customer churn didn't spike. The product continued to work. Within eighteen months, 37signals had hired 45 new people and was larger than it had been before the exodus. The episode demonstrated something uncomfortable about the relationship between culture and business performance: a company could lose a third of its workforce in a week, endure weeks of brutal press coverage, and emerge financially unscathed — perhaps even stronger, if you accepted the founders' argument that the departing employees were a poor cultural fit for the company they wanted to build.
Whether that argument was right or self-serving — or both — remains the central interpretive question of the Basecamp story. The company reverted to the name 37signals shortly after, a symbolic return to origins.
ONCE: Selling Software Like It's 1999
In 2022, 37signals announced something that seemed, even by its standards, willfully anachronistic: a new product line called ONCE. The premise was that instead of paying a monthly subscription for cloud-hosted software, customers would pay a one-time fee and run the software on their own servers. The first ONCE product was Campfire — yes, the same group chat tool they'd killed in 2014, resurrected as a self-hosted, pay-once application.
The ONCE model was a direct challenge to the SaaS business model that 37signals had helped pioneer. In a world where every software company was optimizing for annual recurring revenue, 37signals was selling downloadable software for a flat price. The logic was characteristically contrarian: SaaS subscriptions created vendor lock-in and recurring costs that compounded over time; a one-time purchase gave customers ownership and control; and for 37signals, the economics still worked because the development costs were low (small team, efficient codebase) and there was no customer support infrastructure to scale.
DHH framed it in cultural terms, arguing that the SaaS model had become extractive — that cloud-hosted software had made customers into renters rather than owners, and that the subscription treadmill enriched vendors at the expense of buyers. He linked it to a broader argument about "leaving the cloud" and running software on commodity hardware, a position informed partly by 37signals' own decision to migrate off Amazon Web Services and onto its own servers, reportedly saving millions of dollars annually.
The ONCE line was small. It was not going to dethrone Slack or Microsoft Teams. But it was symbolically potent — a signal (there's that word again) from the company that had helped define web-based SaaS that the model itself might be due for disruption.
The Cathedral and the Bazaar, or: What Ruby on Rails Actually Did
You cannot tell the Basecamp story without reckoning with the asymmetry at its center. The company itself generated somewhere in the range of $100 million in annual revenue — a remarkable achievement for a sub-100-person private company, but not a figure that reshapes industries. Ruby on Rails, the framework DHH extracted from Basecamp's codebase and gave away for free, catalyzed an ecosystem worth orders of magnitude more.
The list of companies that built their initial products on Rails reads like a roster of the modern consumer internet: Shopify (public market cap fluctuating in the range of $100 billion), GitHub (acquired by Microsoft for $7.5 billion in 2018), Airbnb (IPO'd in 2020), Twitter (in its earliest incarnation), Twitch (acquired by Amazon for $970 million), Kickstarter, Hulu, Square, Zendesk, SoundCloud. DHH created, in Rails, a tool that dramatically lowered the cost and time required to build web applications, particularly for startups with small teams and limited capital — exactly the kind of companies that 37signals argued should exist.
The decision to open-source Rails was philosophically consistent but economically irrational by conventional standards. 37signals could have kept the framework proprietary, licensing it for millions. They could have built a Rails-based platform business. Instead, they gave it away, bet that the resulting ecosystem would create demand for their product (Basecamp ran on Rails, proving it at scale), and settled for the reputational capital and developer community that the framework generated.
The bet worked — but not in the way a venture capitalist would have designed it. Rails made 37signals famous among developers, which made Basecamp famous among the kind of technical founders and small teams most likely to buy it. The open-source project was, effectively, the most successful marketing investment in the company's history — and it cost them nothing in direct revenue because it was never meant to generate any.
What Rails also did, less visibly, was establish DHH as a technical authority of unusual stature. His annual RailsConf keynotes became events. His opinions on software architecture, programming languages, and developer culture carried weight far beyond the 37signals orbit. When he criticized Apple's App Store practices, or argued against microservices, or advocated for server-rendered HTML over JavaScript-heavy frameworks, developers listened — not because he ran a large company, but because he had built a tool they relied on.
The Anti-Unicorn Thesis
What does Basecamp prove? This is the question that operators and investors have argued about for twenty years, and the answer depends entirely on what you believe about the purpose of a technology company.
The bull case for the Basecamp model is this: you can build a software business that generates tens of millions (eventually north of $100 million) in annual revenue, remains profitable from nearly its first year, requires no outside capital, never lays anyone off (the 2021 departures were voluntary resignations, not layoffs), provides excellent compensation and working conditions, and does all of this with fewer than 100 employees. The company is not just viable; it is durable. It has survived the dot-com bust, the 2008 financial crisis, the rise of Slack, the COVID-19 pandemic, and its own internal meltdown without existential threat. If the measure of a business is longevity, profitability, and independence, Basecamp is one of the most successful software companies ever built.
The bear case — and it is a real one — is that Basecamp left an astonishing amount of value on the table. The company invented the productivity software category that Asana, Monday.com, Notion, ClickUp, and others would colonize with venture-backed blitzscaling. Asana went public in 2020 with a market cap exceeding $5 billion. Monday.com went public in 2021 at a $6.8 billion valuation. These companies offered products that were, in many cases, more complex and more expensive than Basecamp — but they also captured markets that 37signals had no interest in entering: enterprise sales, platform ecosystems, AI integrations, developer APIs.
Did Basecamp choose not to compete for those markets, or did it lack the ambition? The answer from Fried and DHH has always been emphatic: it was a choice, and a proud one. They didn't want to run a company with thousands of employees. They didn't want to answer to public market investors. They didn't want to spend their lives in board meetings and earnings calls. They wanted to build software, write books, and live well. The company was a vehicle for the life they wanted, not the other way around.
Whether you find that admirable or infuriating says more about you than about the business.
The Calm Company That Wasn't Always Calm
The deepest tension in the Basecamp story is not strategic but philosophical: the gap between the company's public identity and its private reality. For years, 37signals projected an image of serenity — calm work, reasonable hours, thoughtful management, no drama. The books reinforced it. The blog posts reinforced it. The conference talks reinforced it. Fried literally wrote a book called It Doesn't Have to Be Crazy at Work.
Then, in 2021, it got crazy at work. The funny-names list, the diversity committee, the blog post edict, the mass resignations — all of it happened inside a company that had built its brand on being the antithesis of workplace dysfunction. The episode didn't invalidate the philosophy. But it revealed something the books never addressed: that a calm workplace requires either genuine consensus or authoritarian enforcement, and when the consensus breaks, the authoritarianism becomes visible.
Fried's post-crisis narrative was unapologetic. "I'm doing great. The business is doing great," he told the 21 Hats podcast a year later. "Losing a third of your employees in one fell swoop is difficult. But we've recovered. We've since hired 45 new people. We're actually bigger than we've ever been." The recovery was real. The lesson was ambiguous: either the company had pruned dead wood and emerged healthier, or it had traumatized loyal employees and replaced them with people who knew better than to dissent.
The truth is probably both, and the ratio is unknowable from the outside.
Still Transmitting
By the mid-2020s, 37signals — the name restored, the product portfolio expanded again with HEY and the ONCE line — occupied a peculiar position in the technology landscape. It was not a startup. It was not an enterprise. It was not a platform. It was a profitable, private, opinionated software company run by two co-founders who had been working together for over twenty years, who had written their own rules, who had been proven right about remote work and wrong about nothing they'd admit to, and who continued to transmit their signal — about calm work, about small teams, about profitability over growth, about owning your tools instead of renting them — to an audience that had never been larger.
DHH, in a 2026 interview, argued that AI coding tools could not yet match even the most junior human programmers — a contrarian position in an industry racing to automate everything. The stance was characteristically confident, characteristically early, and characteristically impossible to dismiss outright because the man saying it had, after all, built the framework that the industry ran on.
The company still had no plans to go public. Still had no outside investors. Still employed fewer than 100 people. Still sold software that cost less per month than a single lunch in the San Francisco neighborhoods where its competitors raised their venture rounds.
Thirty-seven signals, detected in a search for extraterrestrial intelligence. None of them turned out to be aliens. But someone is still listening.
The operating philosophy of 37signals — refined over more than two decades of building products, writing books, and arguing loudly with the rest of the technology industry — constitutes one of the most coherent and deliberately counter-cultural business playbooks in modern software. What follows are the principles extracted from that philosophy, grounded in the specific decisions and outcomes that gave them force.
Table of Contents
- 1.Charge from day one.
- 2.Build the tool you need, then sell it to people like you.
- 3.Give away the byproduct.
- 4.Ship the calendar, not the roadmap.
- 5.Kill your darlings before they kill your focus.
- 6.Write the company you want to run.
- 7.Keep the team small enough to trust.
- 8.Own the infrastructure, own the margin.
- 9.Say no to almost everything.
- 10.Survive the crisis by not needing to grow through it.
Principle 1
Charge from day one.
37signals never had a "pre-revenue phase." Basecamp launched with paid tiers in February 2004 and was generating meaningful subscription revenue within weeks. The company stopped doing client work within a year — not because it raised a round, but because customers were already covering costs. HEY launched at $99/year. The ONCE line charges a one-time purchase fee. In every case, the pattern is the same: price the product, ship it, and let paying customers fund development. No freemium conversion funnels. No years of subsidized growth.
This approach imposes discipline. When you charge from day one, you learn immediately whether anyone values what you've built. You don't get the luxury of vanity metrics — millions of free users who "might" convert. You get a binary signal: people pay, or they don't. For 37signals, people paid.
💰
Pricing Philosophy Over Time
| Product | Year | Pricing Model | Starting Price |
|---|
| Basecamp (original) | 2004 | Tiered SaaS subscription | $24/month |
| Basecamp (v3) | 2015 | Flat-rate subscription | $99/month (unlimited users) |
| HEY | 2020 | Annual subscription | $99/year |
| ONCE (Campfire) | 2023 | One-time purchase | $299 (self-hosted) |
Benefit: Revenue from day one eliminates dependency on outside capital and creates an honest feedback loop between product value and market demand.
Tradeoff: You grow slower. Competitors who subsidize with venture capital can undercut you on price, offer free tiers, and capture market share you'll never recover. Monday.com and Asana acquired millions of users this way.
Tactic for operators: Before building your freemium funnel, test whether 100 people will pay $50/month for your product. If yes, you may not need to raise a round. If no, the problem isn't your price — it's your product.
Principle 2
Build the tool you need, then sell it to people like you.
Basecamp was not designed by a product manager analyzing market gaps. It was built by Jason Fried to solve his own team's project management chaos. The first user was the builder. The first customer profile was the company itself. This meant the product had a clarity of purpose that market research alone rarely achieves: every feature solved a problem someone in the building had actually experienced.
DHH has made this point repeatedly: the best products come from people solving their own problems, because they understand the pain at a granular level that no survey can replicate. Ruby on Rails emerged the same way — extracted from the real work of building Basecamp, not designed in the abstract.
Benefit: Products built for the builder have an authentic point of view that's difficult to reverse-engineer. They're opinionated, which means they're not for everyone — but for the people they're for, they feel inevitable.
Tradeoff: You build for people like you, which means you don't build for people unlike you. Enterprise buyers with complex compliance requirements, large organizations with hundreds of team hierarchies — they needed something Basecamp never wanted to become.
Tactic for operators: The most powerful version of product-market fit isn't finding a market for your product — it's building the product you can't believe doesn't exist. If you're your own best customer, trust that instinct before you trust any TAM analysis.
Principle 3
Give away the byproduct.
Ruby on Rails — the framework DHH built while building Basecamp — has powered over a million web applications and underpinned companies worth hundreds of billions of dollars collectively. 37signals gave it away for free. Not as a loss leader. Not as an open-source-to-enterprise conversion strategy. Just... free.
The returns were indirect but immense. Rails made 37signals the most credible voice in web development. It attracted developers to the ecosystem, many of whom became Basecamp customers or evangelists. It generated speaking invitations, book deals, and a level of technical authority that no amount of advertising could have purchased.
Benefit: Open-sourcing the byproduct creates a developer community, reputational capital, and an organic marketing channel that compounds over decades. The cost is zero; the goodwill is infinite.
Tradeoff: You create value you can never capture. Shopify became a $100B+ company on Rails. 37signals captured none of that value directly. A venture capitalist would call this a catastrophic failure of appropriability. Fried and DHH would call it the point.
Tactic for operators: Identify the non-core asset in your business that others would find valuable — a process, a dataset, a tool, a framework. Giving it away can build more sustainable competitive advantage than selling it, because it positions you as the authority rather than the vendor.
Principle 4
Ship the calendar, not the roadmap.
The Shape Up methodology — six-week cycles, two-week cooldowns, no long-term roadmaps — was not just a product development process. It was a philosophy of organizational time. 37signals refused to commit to features more than six weeks out. There were no annual plans, no quarterly OKRs, no multi-year product roadmaps. "Planning is guessing," Fried wrote in REWORK.
The six-week cycle forced prioritization. With a fixed time horizon and a small team, the only honest question was: what's the most important thing we can ship in six weeks? Everything else waited. If a project wasn't done at the end of the cycle, it was abandoned — not extended, not carried over, not given "just two more weeks." This brutal cutoff prevented the sunk-cost fallacy from consuming resources.
Benefit: Fixed cycles create shipping discipline, prevent scope creep, and keep the team focused on impact rather than activity. The two-week cooldown prevents burnout and creates space for exploration.
Tradeoff: You can't make long-term commitments to enterprise customers. You can't build features that require six months of sequential development. You optimize for shipping speed at the expense of architectural ambition.
Tactic for operators: Try one six-week cycle before committing to the full methodology. Pick the highest-impact project your team can scope to six weeks, assign a team of two or three, and enforce the hard stop. The constraint itself generates clarity.
Principle 5
Kill your darlings before they kill your focus.
In 2014, 37signals retired Highrise, Campfire, Backpack, and every other product to focus exclusively on Basecamp. Some of these products had loyal users. Campfire, in particular, had pioneered real-time group chat before Slack existed. The company killed them anyway.
The decision required confronting a specific kind of loss aversion: the sunk cost of products that were working but not central. Each product demanded attention — bug fixes, customer support, server maintenance — and each stole cognitive bandwidth from the flagship. The rename to Basecamp was not just branding; it was a declaration that the company was its core product.
Benefit: Radical focus concentrates all resources — technical, creative, and managerial — on the thing that matters most. It eliminates the organizational tax of maintaining products that are "good enough" but not great.
Tradeoff: You abandon optionality. Campfire's retirement left a vacuum that Slack filled to the tune of a $27.7 billion acquisition by Salesforce. The opportunity cost of killing a product early is invisible but potentially enormous.
Tactic for operators: Audit your product portfolio not for profitability but for attention cost. The product that generates 10% of revenue but consumes 30% of your mental energy is the one to kill — or spin out.
Principle 6
Write the company you want to run.
37signals published five books, maintained Signal v. Noise as one of the most-read business blogs on the internet, produced a podcast, and generated a steady stream of essays, talks, and social media commentary. This was not a content marketing strategy in the conventional sense. It was closer to a public intellectual project: Fried and DHH articulated a comprehensive philosophy of work, and the audience that agreed with the philosophy became the customer base.
REWORK sold millions of copies and was translated into dozens of languages. It functioned as a Trojan horse: readers came for the business advice and left knowing about Basecamp. The books' sales figures were large enough to constitute a revenue stream in their own right, but their primary value was as customer acquisition — acquisition at negative cost, since the books themselves were profitable.
Benefit: Content-as-philosophy creates the strongest possible brand moat — customers who don't just use your product but believe in your worldview. Customer acquisition costs approach zero because the content generates organic demand.
Tradeoff: Your brand becomes inseparable from the founders' personal views. When those views become controversial — as they did in 2021 — the company absorbs the reputational impact directly. There is no separation between the company and the people.
Tactic for operators: Don't hire a content marketing team. Write what you actually believe about your industry, your craft, your approach to building. If you don't have a strong enough point of view to write a book about it, you may not have a strong enough point of view to build a durable company.
Principle 7
Keep the team small enough to trust.
37signals never employed more than approximately 75 people. It was remote from before remote was fashionable — DHH was hired from Copenhagen in 2001, a full two decades before COVID-19 made distributed work standard. The company paid top-of-market salaries (Fried has said they benchmarked to the 95th percentile of San Francisco tech compensation regardless of where employees lived), offered four-day summer workweeks, funded vacations, and covered continuing education.
The small team was not a constraint to be overcome; it was a design principle. With fewer people, communication was simpler, bureaucracy was lighter, and individual impact was higher. There were no managers in the traditional sense — teams self-organized around projects during each six-week cycle.
Benefit: Small teams with high trust move faster, communicate more efficiently, and produce better work per person. The company avoids the coordination costs that plague organizations above 150 people (Dunbar's number).
Tradeoff: You cannot pursue multiple large initiatives simultaneously. You cannot enter enterprise markets that require dedicated account managers, implementation teams, and sales organizations. Your bus factor is dangerously high — losing a single key person has outsized impact.
Tactic for operators: Before hiring your next employee, ask: can we restructure the work so that the existing team can handle it? The most expensive employee is not the one with the highest salary — it's the one whose addition creates the need for a manager.
Principle 8
Own the infrastructure, own the margin.
In the early 2020s, 37signals made a decision that ran against the entire cloud-first orthodoxy of the software industry: it migrated off Amazon Web Services and onto its own servers. DHH reported that the move saved the company millions of dollars annually — money that went directly to the bottom line. The ONCE product line extended the logic to customers: instead of paying monthly for cloud-hosted software, buy it once and run it on your own hardware.
The argument was economic and philosophical. Cloud hosting, in DHH's analysis, was a convenience tax that compounded over time. For a company with stable, predictable workloads — which Basecamp was — the economics of owning hardware were dramatically better than renting compute from Amazon.
Benefit: Owning infrastructure at scale (for companies with predictable demand) eliminates the cloud margin and returns that capital to the business. For customers, the ONCE model eliminates subscription fatigue and vendor dependency.
Tradeoff: You need operational expertise to manage your own hardware. You lose the elasticity of cloud computing — the ability to scale up instantly during traffic spikes. And the up-front capital expenditure is significant.
Tactic for operators: Run the numbers on your cloud bill. If your workload is predictable and you're spending more than $500K/year on a single cloud provider, model the economics of owning or co-locating. The savings may fund your next product.
Principle 9
Say no to almost everything.
Fried has said that the most important word in the 37signals vocabulary is "no." No to enterprise features. No to complex integrations. No to features requested by large customers who threatened to churn. No to meeting requests. No to conference invitations. No to partnerships. No to acquisitions. The company's product philosophy was defined more by what it refused to build than by what it built.
This was not minimalism for aesthetic purposes. It was a resource allocation strategy. Every feature added was a feature maintained, and maintenance was a tax on future flexibility. By keeping the product simple — deliberately simpler than competitors — 37signals kept its team small and its codebase manageable.
Benefit: Saying no preserves optionality, reduces technical debt, and keeps the product simple enough that a small team can maintain it. It's also a competitive signal: customers who value simplicity self-select into your product, creating a user base aligned with your philosophy.
Tradeoff: You lose customers who need those features. Competitors build the things you won't, and some of those features become table stakes. The market can evolve past your product while you're saying no.
Tactic for operators: For every feature request, calculate not just the build cost but the perpetual maintenance cost (support, documentation, testing, interaction effects with other features). If the maintenance tax exceeds the revenue from the requesting customer segment, say no.
Principle 10
Survive the crisis by not needing to grow through it.
When a third of 37signals' employees resigned in April 2021, the company did not issue emergency retention packages, did not raise a crisis round, did not adjust pricing, and did not change its product strategy. Revenue held. Customers stayed. Within eighteen months, the company had hired 45 new people and was larger than before.
This resilience was not accidental. It was the structural consequence of every preceding principle: no outside investors demanding growth metrics, no debt service requiring a minimum revenue threshold, profitability providing a cash cushion, small team size meaning the company could function with reduced headcount, and a product simple enough that a skeleton crew could keep it running.
The 2021 crisis was, in a sense, the final test of the Basecamp model: could a company built on these principles survive a self-inflicted wound that would have been existential for a venture-backed company burning cash? It could. It did.
Benefit: A profitable, debt-free, bootstrapped company with no external obligations is nearly impossible to kill from the outside. Its survival depends only on customer retention and operational discipline, not on investor sentiment or credit markets.
Tradeoff: The same structures that provide resilience also limit upside. You'll never have the capital to make a transformative acquisition, enter a new market aggressively, or hire the 500-person sales team needed to compete at enterprise scale.
Tactic for operators: Stress-test your business model by asking: what happens if 30% of our team leaves tomorrow? If the answer is "we go bankrupt," you have a structural fragility that no amount of growth can fix.
Conclusion
The Signal in the Noise
The 37signals playbook is not universally applicable. It works for a specific kind of business — software products sold to small teams at modest price points, built by a company that values independence over scale. It does not work for companies that need to capture winner-take-all markets, that face capital-intensive R&D cycles, or that require massive sales organizations to close enterprise deals.
But within its domain, the playbook is devastatingly effective. It proves that a software company can be profitable from its first year, stay profitable for two decades, never take outside capital, employ fewer than 100 people, weather multiple economic crises and an internal meltdown, and still generate over $100 million in annual revenue. It proves that a company can choose not to grow — can actively refuse the opportunities that growth requires — and still be durable, influential, and rich enough to make its founders wealthy on their own terms.
The signal from 37signals was never about project management software. It was about what a business is for.
Part IIIBusiness Breakdown
The Business at a Glance
Current Vital Signs
37signals (Basecamp)
~$100M+Estimated annual revenue (private; not disclosed)
~75Employees (as of 2023)
3.5M+Basecamp accounts created over lifetime
25+Years of continuous profitability
3Active product lines (Basecamp, HEY, ONCE)
$0External debt or venture capital on balance sheet
37signals occupies a rare position in the software industry: a private, profitable, bootstrapped company with no outside capital, no debt, and no obligation to report financial results. Revenue estimates — drawn from the founders' public statements, industry analyses, and the company's scale of operations — place annual revenue in excess of $100 million. The company has been profitable for essentially its entire existence, a claim almost no SaaS company of comparable scale can make.
The team of roughly 75 employees operates remotely, with no physical headquarters. The company's infrastructure runs on owned and co-located servers after migrating off AWS — a decision DHH has said saves millions annually. With no sales team, no enterprise account management, and no investor relations function, the company's overhead structure is dramatically lighter than peers.
How 37signals Makes Money
37signals generates revenue from three product lines, each with a distinct business model:
37signals product portfolio and pricing models
| Product | Model | Pricing | Status |
|---|
| Basecamp | SaaS subscription | $299/month flat (unlimited users) | Core revenue driver |
| HEY | Annual subscription | $99/year (personal); higher for business | Growing |
| ONCE | One-time purchase | $299+ per product (self-hosted) | Early stage |
Basecamp is the dominant revenue source. The product has evolved through multiple major versions since 2004, with the current iteration offering project management, team communication, file sharing, scheduling, and to-do management in a single flat-rate package. The flat-rate model — $299/month for unlimited users — is unusual in SaaS, where per-seat pricing dominates. This means Basecamp's revenue per account is fixed regardless of team size, which simplifies billing but caps expansion revenue from growing customers.
HEY generates subscription revenue from individual and business users paying for a privacy-first email service. The product was launched in 2020 and addresses a niche market of privacy-conscious users willing to pay for email in a world where Gmail is free. Revenue scale is likely modest relative to Basecamp but contributes meaningfully to the portfolio.
ONCE represents an experimental revenue model — one-time purchases of self-hosted software. The line launched with Campfire (group chat) and has expanded. Revenue contribution is likely small but the line serves a strategic purpose: it positions 37signals at the vanguard of the anti-SaaS movement and attracts customers who share the company's philosophy.
Unit economics are exceptionally favorable. With no sales team (all acquisition is organic, driven by content and word-of-mouth), no significant customer acquisition cost, high gross margins (software delivery at scale with owned infrastructure), and a small employee base, the company likely operates at net margins that would be extraordinary by SaaS standards — potentially 30-50%+ given the absence of sales, marketing, and cloud hosting costs that typically consume 50-70% of SaaS revenue.
Competitive Position and Moat
37signals operates in the project management and team collaboration software market, a space that has become extraordinarily crowded since Basecamp's launch in 2004.
Basecamp vs. major competitors
| Company | Est. Revenue | Employees | Funding Model | Market Position |
|---|
| Monday.com | $972M (2024) | ~2,000 | Public (NYSE: MNDY) | Growth |
| Asana | ~$680M (2024) | ~1,800 | Public (NYSE: ASAN) | Mature |
| ClickUp | ~$200M+ (est.) |
By revenue, Basecamp is significantly smaller than Monday.com or Asana. By revenue per employee, it is in a league of its own — generating roughly $1.3M+ per employee versus Monday.com's approximately $486K per employee. This is the efficiency dividend of the 37signals model.
Moat sources:
-
Brand and philosophy. 37signals has cultivated a deeply loyal customer base through two decades of ideological consistency. Customers who value simplicity, calm work, and anti-enterprise philosophy are unlikely to switch to a complex, feature-heavy competitor. This is a cultural moat, not a technical one.
-
Content engine. Five bestselling books, a major blog, a podcast, and DHH's social media presence generate organic customer acquisition at near-zero cost. No competitor has a comparable founder-driven content machine.
-
Profitability as structural resilience. In a downturn, VC-backed competitors may face pressure to cut burn, raise at unfavorable terms, or shut down. 37signals is immune to these dynamics. It has survived every macro downturn of the last 25 years without altering its business model.
-
Ruby on Rails ecosystem. DHH's stewardship of Rails gives 37signals ongoing credibility and visibility in the developer community, though this is an indirect rather than direct competitive advantage.
-
Simplicity as product differentiation. In a market where competitors are adding AI features, integrations, and enterprise tooling, Basecamp's deliberate simplicity serves a specific customer segment that is over-served and overwhelmed by alternatives.
Where the moat is weak:
-
No network effects. Basecamp is a tool, not a platform. There is no marketplace, no ecosystem, no user-generated content that makes the product more valuable as more people use it. Every customer could leave tomorrow without affecting other customers.
-
No switching costs. Project management data is relatively easy to export and import. Migration to a competitor is inconvenient but not prohibitive.
-
No enterprise wedge. 37signals has deliberately avoided enterprise sales, which means it has no presence in the large-company market where contract values are highest and retention is strongest.
The Flywheel
37signals' flywheel is unusual in that it is driven by ideology rather than network effects.
1. Founders publish opinionated content (books, blog posts, podcasts, talks) that articulates a distinctive philosophy of work and business.
2. Content attracts an audience of founders, small business owners, and developers who share the philosophy — people who are exhausted by enterprise complexity, VC-driven growth culture, and bloated software.
3. Audience converts to customers at near-zero acquisition cost, because the content pre-qualifies buyers who value simplicity, profitability, and independence.
4. Revenue funds development with no external dilution or debt. The small team builds products that embody the philosophy — simple, opinionated, self-contained.
5. Product quality reinforces the philosophy, providing evidence that the approach works. Customers become evangelists. The company publishes more content about what it's learned.
6. Cycle repeats, with each turn strengthening the brand, deepening the community, and widening the ideological moat.
The critical observation about this flywheel is that it does not compound in the way that, say, a marketplace or platform flywheel compounds. There is no exponential growth mechanism. The flywheel generates steady, durable, profitable demand — but it is inherently linear. This is the structural ceiling of the 37signals model: it generates more trust and loyalty over time, but it does not generate more customers at an accelerating rate.
Growth Drivers and Strategic Outlook
Despite the company's anti-growth rhetoric, 37signals has identifiable vectors of expansion:
1. HEY email. The privacy-first email market is small today but may expand as consumer awareness of data surveillance grows and regulatory pressure (GDPR, potential U.S. privacy legislation) increases. HEY's $99/year price point is accessible, and the product's distinctive design differentiates it from commodity email.
2. ONCE product line. The pay-once, self-hosted model addresses growing fatigue with SaaS subscription sprawl. If the model proves viable, 37signals could release additional ONCE products — each targeting a common software need (chat, project management, document collaboration) with a one-time purchase option.
3. Cloud-to-hardware migration consulting/tooling. 37signals' public advocacy for leaving cloud providers and running on owned hardware has generated significant attention. There is latent demand among mid-size companies for guidance and tooling to make this transition.
4. International expansion. Basecamp's flat-rate pricing and remote-first model make it inherently global, but the founders' content is overwhelmingly English-language. Localization and international marketing represent an untapped vector.
5. AI-enhanced features — carefully. DHH has been skeptical of AI hype, but the integration of AI-powered features (summarization, search, writing assistance) into Basecamp or HEY could expand the product's utility without compromising its simplicity.
Key Risks and Debates
1. Founder dependency. The company's brand, philosophy, and content engine are inseparable from Fried and DHH. If either founder departs, the company loses not just leadership but its primary marketing channel and ideological anchor. There is no obvious succession plan, and the brand's value is tied to specific individuals to a degree unusual even among founder-led companies.
2. Category commoditization. Project management software has become a commodity. Features that were once differentiating — shared to-do lists, file storage, team messaging — are now table stakes in Microsoft Teams, Google Workspace, Slack, and dozens of free tools. Basecamp's simplicity, once an advantage, risks becoming indistinguishable from "basic."
3. AI-driven competitive disruption. Competitors like Notion, ClickUp, and Monday.com are investing heavily in AI features — automated project summaries, intelligent task assignment, predictive scheduling. If AI features become a primary purchase driver, Basecamp's minimalist approach could lose relevance with buyers who expect AI as standard.
4. The 2021 reputational fracture. The employee exodus and associated press coverage damaged 37signals' reputation as an employer, particularly among the demographic of progressive, values-driven knowledge workers who had been the company's most natural recruiting pool. While Fried reports full recovery, the incident may have permanently narrowed the company's talent pipeline.
5. Flat pricing cap on expansion revenue. Basecamp's $299/month flat rate means a 500-person company pays the same as a 5-person company. This eliminates per-seat expansion revenue — the primary growth driver for SaaS companies — and structurally limits revenue growth to new customer acquisition rather than account expansion.
Why 37signals Matters
37signals matters not because of its size — by revenue, it is a rounding error in the software industry — but because of its proof of concept. For twenty-five years, the company has demonstrated that a technology business can be built on principles that the prevailing industry wisdom considers naive: profitability over growth, small teams over headcount expansion, simplicity over feature parity, independence over institutional capital.
The proof is not theoretical. It is financial. A company with ~75 employees generating $100M+ in annual revenue with no outside capital, no debt, and no obligation to report to anyone beyond its founders and customers is not a lifestyle business. It is an operating system — one that happens to reject nearly every assumption the venture-backed software industry holds sacred.
For operators, the lesson is not that every company should be 37signals. Most cannot. The lesson is that the default path — raise, grow, raise again, grow faster, IPO or die — is a choice, not a law of nature. There is another path, and it leads, in the 37signals case, to a company that has outlasted most of the venture-backed competitors that once seemed poised to render it irrelevant. Whether it lasts another twenty-five years depends on whether the signals it transmits continue to find an audience — and whether the audience continues to pay for the privilege of listening.
