Support Voice of the Customer project
37signals maintains a dedicated project called 'Support Voice of the Customer' to capture unusually insightful customer language and unique scenarios.
Where this was said
Why writing down every customer request can work against you
At 2:25 · chapter starts 0:40
Jason Fried opens with a confident defence of deliberate forgetting: the signal worth acting on is whatever keeps coming up repeatedly without being written down. The moment you put something on a list, you've manufactured an obligation — and product decisions made from obligations rather than genuine signal rarely lead anywhere good. He's careful to distinguish between productive listening and obsessive documentation: the former sharpens your instincts, the latter creates noise. His one carved-out exception is the 'Support Voice of the Customer' project [2] — Jason Fried "Support Voice of the Customer project: 37signals maintains a dedicated project called 'Support Voice of the Customer' to capture unusually …" 02:25 , where particularly vivid customer language or unusual scenarios get captured — not for feature planning, but for vocabulary mining. He illustrates this with a charming anecdote: early Basecamp customers were organically calling their projects 'base camps,' an insight that eventually prompted 37signals to consider that naming convention in Basecamp 3. It's a story that shows what listening without writing down can still surface when you're paying real attention.
Don't Institutionalize Customer Feedback
Hearing the same request repeatedly is your signal — not a written list. The moment you write something down, you create an obligation. Most individual feedback reflects one person's scenario, not the product's true direction.
Customers called projects 'base camps'
Early Basecamp customers organically called their projects 'base camps,' a usage insight that led 37signals to consider renaming projects accordingly in Basecamp 3.
Similar snapshots
Zero users on launch day
Despite months of meticulous preparation, Starter Story's initial launch attracted zero users — a humbling reminder that building alone guarantees nothing.
First Reddit post: 100 users
A single Reddit link post quickly drove 100 visitors to the Starter Story website, igniting the founder's belief in social traffic.
Hundreds of upvotes on repackaged post
After reformatting content as a native self-post (no direct link spam), the post exploded with hundreds of upvotes and thousands of readers.
Millions reading his content on Reddit
By posting again and again with the native-content strategy, the founder's posts repeatedly hit Reddit's front page, reaching millions of readers.
Tens of thousands of email subscribers
Before Reddit banned his domain, the founder converted his viral traffic into an email list of tens of thousands — a self-owned audience independent of Reddit.
Reddit petition to ban domain
Redditors eventually organized a petition to ban starterstory.com posts, effectively ending the Reddit growth channel — but the email list was already built.
$1M business built on Reddit hack
The Reddit attention strategy ultimately served as the foundation for a million-dollar business, proving that free distribution channels can replace paid marketing.
Strategy: native content, small footer link
The key tactic was keeping content fully on-platform (no direct link spam), then adding a small link at the post's end for users who wanted more.
Quit 9-to-5 after email list built
With a thriving email list and a self-owned audience, the founder quit his six-figure New York City salary job to go all-in on Starter Story.
