A Note Before We Begin: I’ve been following Jason Fried and David Heinemeier Hansson’s work for years. Their books changed how I think about business. Their writing is consistently sharp, honest, and useful. I watch Jason’s posts on X not because I’m looking for flaws, but because I’m fascinated by what makes certain businesses connect so deeply with identity.

This piece isn’t a criticism. It’s pattern recognition.

I’ve spent considerable time researching 37signals, reading their content, analyzing customer language, and studying their evolution over 25 years. I’ve done my best to get the facts right. If I’ve misrepresented anything, that’s not my intention. It’s the inevitable gap between outside observation and inside experience.

Here’s what I know to be true: No one can read their own label. Jason and David have access to data, context, and nuance I’ll never see. They experience their business from inside, where every decision has history and logic. I’m looking from outside, where patterns become visible that can’t be seen from within.

They might read this and think “He’s wrong about why we did X” or “That’s not how we see it at all.” That’s fair. They’re probably right about their conscious reasoning. But sometimes the most powerful dynamics are the ones we can’t see because we’re living inside them.

This is my attempt to read their label, not to correct their story, but to reveal what might be working even better than they realize. The highest compliment to their work is taking it seriously enough to understand why it actually works, beyond the explanations that feel obvious from inside.

If you’re Jason or David reading this: I hope you see this as an act of respect, not critique. You’ve built something rare. This is me trying to understand what makes it rare.

PS: Monopoly uncovered all the insights you’ll read in this perspective.

Part 1: The Story They Tell

Jason Fried will tell you 37signals succeeded because they stayed disciplined. No venture capital. Small team. Simple products. Focus over features. Profit over growth.

David Heinemeier Hansson credits their technical credibility and contrarian positioning. They created Ruby on Rails and gave it away. They challenged industry orthodoxy on subscriptions, feature bloat, and meeting culture. They took controversial stances not for attention, but because they believed them.

Their narrative is coherent: “We’re successful because we executed principles consistently for 25 years.” They rejected hundreds of VC offers. Kept the team at 80 people while serving millions. Built profitable software from day one. Work 40-hour weeks, 32 in summer. Say no to complexity. Write books teaching what they practice. Be transparent about everything.

Jason frames their edge through operational excellence: “We’ve been profitable every month for 25 years. That’s not luck. It’s proof the model works.” He positions their advantage as philosophical clarity: “Most companies optimize for growth. We optimize for longevity. Different game, different rules.”

DHH emphasizes thought leadership: “We created Rails. That gave us developer respect. Then we challenged industry orthodoxy. We take controversial stances because we genuinely believe them.” Their public narrative centers on tactical discipline executed with unusual commitment.

When they explain Basecamp’s success, they list features: all-in-one simplicity, flat pricing, client-friendly collaboration, built-in chat so you don’t need Slack, and hill charts for progress visibility. When they describe their business model, they emphasize bootstrapped profitability, founder control, and values-driven decision-making.

The ONCE initiative fits this narrative perfectly: “We pioneered SaaS in the 2000s. Now we’re leading the way out. People are tired of renting software.” They frame it as a prediction. Subscription fatigue will create a massive opportunity for ownership-based software.

Ask them what differentiates them, and they cite principles: “We build half a product, not a half-ass product.” “We don’t sell you or your data.” “Small is not just a stepping stone; small is a great destination.” “It doesn’t have to be crazy at work.”

This story serves their identity needs beautifully. They’re the principled craftspeople who refused to compromise. The indie heroes who proved you don’t need VC funding. The thought leaders whose ideas shaped an industry. The disciplined operators who chose sustainability over hypergrowth.

It’s a compelling story. It’s also completely backward.

Part 2: The Hidden Position

Here’s what customers actually say when describing why they use 37signals products:

“My life is so much less stressed. Basecamp has increased my happiness exponentially.”

“It’s a godsend. Everyone’s on the same page.”

“Finally, sanity. No more drowning in a million emails.”

“I’m in control for the first time in years.”

“HEY solved email!!! I own my inbox again.”

Notice what’s missing? No one mentions features. No one cites pricing models. No one credits the bootstrapped story or philosophical manifestos. They talk about regaining control.

The concept 37signals owns isn’t calm, simplicity, or independence. Those are benefits, methods, or attributes; adjectives describing outcomes. The actual noun lodged in customer minds is CONTROL. Specifically: intentional control over how work happens.

This explains everything that confuses analysts:

Why do customers pay $299/month for “limited” features when competitors offer more for less? They’re not buying features. They’re buying the feeling of being in control. When you’re drowning in project chaos across five different tools, Basecamp’s deliberate constraints feel like relief, not limitation.

Why does HEY charge $99/year when Gmail is “free?” Because free means you’re not in control, advertisers are. HEY customers aren’t paying for email. They’re buying back control of their inbox from surveillance capitalism.

Why do ONCE products work despite self-hosting complexity? Because some customers value control over convenience so intensely, they’ll tolerate technical burden. “You should own that shit by now” isn’t about saving money. It’s about sovereignty.

Why does removing features strengthen rather than weaken their position? Because feature bloat is a loss of control. Every option added creates decisions, dependencies, configurations, and learning curves. Each one diluting control. Subtraction is control restoration.

The position creates a perceptual monopoly. When someone says, “I want control over my work chaos,” one answer dominates mental space: 37signals. Not Asana (too complex, requires extensive configuration). Not Monday.com (too many features that pull you in different directions). Not Slack (designed to interrupt you constantly).

37signals is control.

This isn’t what they claim. Scan their website and you’ll find “calm,” “simple,” “straightforward,” and “organized.” All adjectives describing benefits. But in customers’ minds, these adjectives point to a noun: control.