Hey.com and the Indie Hacker's Playbook: Building Big Without Spending Big

The Opening Question

What if email actually served the user instead of marketers, bosses, and algorithmic manipulation?

Hey.com’s emergence tells a larger story: an ambitious effort to fundamentally rethink digital communication, rejecting Silicon Valley’s accepted practices. Basecamp’s project represents something beyond typical software—it’s a manifesto declaring “your inbox, your rules.”

The Problem: Modern Email Chaos

Contemporary email creates predictable frustration. Notifications demand urgent attention. Newsletters accumulate uncontrollably. Reply-all chains multiply endlessly. Inboxes overflow with algorithmic noise, mailing lists, and extended work conversations.

Basecamp, built on minimalist software principles, confronted this crisis firsthand. Years of managing emails and rescuing messages from spam filters led founders to ask the forbidden question: What if email actually respected user time, attention, and privacy?

Hey’s development wasn’t incremental—it happened publicly. Announcements, demonstrations, and launches matched Basecamp’s transparent, open approach. Public changelogs, tweets, and podcast discussions explained not just features, but the reasoning behind every decision.

The Screener: User Control Returns

The “Imbox” (intentional—“Important Box”) forms the system’s core: a protected space containing only emails you explicitly allow.

New senders don’t automatically enter your Imbox. Instead, you receive a single choice: accept future messages, or decline. No algorithmic guessing. No “intelligent” sorting. Users become gatekeepers of their own digital space.

The outcomes: noise diminishes significantly, mental clarity improves, marketers cannot bypass your filters.

Organizational Features: Rituals Over Functions

Hey’s interface reimagines email fundamentally:

• The Feed — newsletters bypass Imbox, collected separately for deliberate consumption
• Paper Trail — receipts and confirmations arrive silently here
• Reply Later — messages needing substantive responses stage here, resembling a task manager

This separation acknowledges authentic email usage patterns—communication as both historical record and active work, information as both passive reading and urgent action.

Privacy as Principle

Hey’s core commitment centers on protecting user privacy. The platform eliminates tracking pixels, prevents open-rate detection, and blocks marketers from accessing device and engagement data.

When Apple demanded in-app purchase requirements for iOS approval, Fried and DHH responded publicly—through blog posts, social media, and transparent discourse. The dispute transcended fees; it involved the right to develop uncompromising products without accepting platform restrictions.

Building Transparently, Growing Through Community

From inception, Hey developed openly. Initial users influenced attachment capabilities, team-based features, and reading experience refinements. This public-building strategy resonated with independent developers. Like comparable platforms (Beehiiv, Llama Life, Notion), Hey succeeded through transparent iteration and community input.

Core Lessons for Builders

Hey’s narrative distills into practical guidance:

1. Challenge established practices when they fail users
2. Construct transparently—invite criticism, celebrate input
3. Defend privacy with unwavering standards
4. Design rituals, not merely features—build for authentic workflows
5. Advocate for users, even against powerful platforms
6. Price honestly—build trust through respecting data and communication

Products achieving lasting impact aren’t engineered for maximum reach—they’re crafted for deep, meaningful resonance.

Hey demonstrates that you can launch modestly, maintain independence, and meaningfully transform how people work daily.