Give it a name
Episode
22 min
Read time
2 min
Topics
Remote Work, Marketing, Product & Tech Trends
AI-Generated Summary
Key Takeaways
- ✓Name-first development: Jason requires a product name before building begins, treating it as fuel for the project. Without an early name, he considers it a signal that something fundamental is missing from the concept. The name serves as an anchor to grab onto and pull through the development process, making it essential rather than optional.
- ✓Sound over concept: When choosing between Boxcar and Fizzy, the team prioritized phonetic appeal over conceptual tightness. Fizzy sounds more pleasant and fluid to say, even though Boxcar had stronger conceptual ties to Chicago train yards and the product's card-based interface. Pleasant pronunciation beats perfect conceptual alignment when names need daily repetition.
- ✓Domain flexibility strategy: 37signals launched four major products without exact domain matches: basecamphq.com, backpackit.com, campfirenow.com, and highrisehq.com. They waited ten years before acquiring basecamp.com. The lesson: avoid over-indexing on domain availability unless giving out email addresses like hey.com, where short domains matter. Pick the right name first.
- ✓Legal naming boundaries: David's open source tool Maersk triggered a trademark dispute with the Danish shipping company, resulting in police serving papers at Copenhagen Airport. The maximum penalty was seven thousand dollars under Danish law, revealing how different legal systems handle trademark conflicts. He renamed it Kamal, which became his preferred choice anyway.
- ✓Momentum makes names permanent: Instagram, Yahoo, Slack, and WhatsApp succeeded with names that would never pass a rebranding committee ten years later. Names become inseparable from products through momentum and familiarity. The takeaway: choose something you enjoy saying for your early-stage project, then let success make it legitimate rather than overthinking initial perfection.
What It Covers
Jason Fried and David Heinemeier Hansson explain their product naming philosophy at 37signals, detailing how names like Fizzy, Basecamp, and Kamal emerged. They emphasize that naming comes first, drives momentum, and matters more than securing perfect domains. The episode covers twenty-five years of naming decisions across products and open source projects.
Key Questions Answered
- •Name-first development: Jason requires a product name before building begins, treating it as fuel for the project. Without an early name, he considers it a signal that something fundamental is missing from the concept. The name serves as an anchor to grab onto and pull through the development process, making it essential rather than optional.
- •Sound over concept: When choosing between Boxcar and Fizzy, the team prioritized phonetic appeal over conceptual tightness. Fizzy sounds more pleasant and fluid to say, even though Boxcar had stronger conceptual ties to Chicago train yards and the product's card-based interface. Pleasant pronunciation beats perfect conceptual alignment when names need daily repetition.
- •Domain flexibility strategy: 37signals launched four major products without exact domain matches: basecamphq.com, backpackit.com, campfirenow.com, and highrisehq.com. They waited ten years before acquiring basecamp.com. The lesson: avoid over-indexing on domain availability unless giving out email addresses like hey.com, where short domains matter. Pick the right name first.
- •Legal naming boundaries: David's open source tool Maersk triggered a trademark dispute with the Danish shipping company, resulting in police serving papers at Copenhagen Airport. The maximum penalty was seven thousand dollars under Danish law, revealing how different legal systems handle trademark conflicts. He renamed it Kamal, which became his preferred choice anyway.
- •Momentum makes names permanent: Instagram, Yahoo, Slack, and WhatsApp succeeded with names that would never pass a rebranding committee ten years later. Names become inseparable from products through momentum and familiarity. The takeaway: choose something you enjoy saying for your early-stage project, then let success make it legitimate rather than overthinking initial perfection.
Notable Moment
David shares his pronunciation philosophy for Umachi, deliberately dropping the r sound despite how people naturally read it. He compares himself to the GIF creator who insists on JIF pronunciation, arguing that English and Danish contain many words where spelling and sound disconnect. He claims the right to define pronunciation for his own creations.
You just read a 3-minute summary of a 19-minute episode.
Get The Rework Podcast summarized like this every Monday — plus up to 2 more podcasts, free.
Pick Your Podcasts — FreeKeep Reading
More from The Rework Podcast
Clearing the decks for launch
May 13 · 28 min
My First Million
DHH: $100M+ Advice That'll Piss Off Every Business Guru
Mar 17
More from The Rework Podcast
Easy to leave
Apr 8 · 25 min
Deep Questions with Cal Newport
Why Do Better Tools Make Me Worse at My Job? (w/ David Epstein) | Monday Advice
May 4
More from The Rework Podcast
We summarize every new episode. Want them in your inbox?
Similar Episodes
Related episodes from other podcasts
My First Million
Mar 17
DHH: $100M+ Advice That'll Piss Off Every Business Guru
Deep Questions with Cal Newport
May 4
Why Do Better Tools Make Me Worse at My Job? (w/ David Epstein) | Monday Advice
My First Million
Mar 13
This guy names billion dollar brands for a living, here’s his exact 3-step formula.
This Week in Startups
Mar 6
Wisdom of the $TAO: the future is decentralized AI
Software Engineering Daily
Feb 26
Amazon’s IDE for Spec-Driven Development with David Yanacek
Explore Related Topics
This podcast is featured in Best Business Podcasts (2026) — ranked and reviewed with AI summaries.
You're clearly into The Rework Podcast.
Every Monday, we deliver AI summaries of the latest episodes from The Rework Podcast and 192+ other podcasts. Free for up to 3 shows.
Start My Monday DigestNo credit card · Unsubscribe anytime