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.
Episode Transcript
Welcome to Rework, a podcast by thirty seven Signals about the better way to work and run your business. I'm Kimberly Rhodes from the thirty seven Signals team joined by the cofounders Jason Fried and David Heinemeier Hanssen. If you have followed thirty seven Signals at all, you know we have many products, all with creative and unique names. I thought we'd talk a little bit about how some of those things have gotten their names. Not only our products, but then open source projects that we've worked on as well. Maybe we start with the most recent being Fizzy. That one has had a couple of names during the building process. Was Fizzy, was renamed, back to Fizzy. Let's start with that one, and then we'll kinda dive into some of our other product namings and kind of where this process comes from. Jason, do you wanna start? Sure. I mean, I'll just say that for me, it doesn't start until there's a name. I just, like, kinda have to find the name first. That actually is the the fuel that fuels the rocket for me. Like, at the very beginning. Like, I have this idea, and I wanna name it? Yeah. A name either comes first or in conjunction with the root of the idea. But if I can't find a name for something early, it's actually kind of a sign to me that, like, maybe there's something that's not here. Something's missing. That's just how it is for me. I just like finding that first name. And when you get the name, when the name feels right, it's just this really great anchor that you can, like, use to to step up or grab onto and pull yourself through. Right? So with Fizzy, it started out as Splat because the idea initially began as a bug tracker, and someone had brought up at a meetup that it'd be cool. Like, the bug tracking idea came after the name, actually, but the idea was bugs hitting a windshield. And then, like, oh, that's a cool way to think about, like, bug tracking is, like, looking at a windshield and having all these splats of dead bugs on the windshield. And so just splat came out of that naturally, and that sort of we got excited about it. Like, splat. That's a cool product name. And it also tied in with the design idea that we had initially with the bugs in the windshield, and that's where we started. Now at some point along the way, the Splat concept sort of ran out of legs because the Splat shapes literally is like splats, like shape. Like, you could imagine like throwing water at a window or or color at a window and, like, just paint splatters. Right? And the shapes were so complex. There wasn't enough room to write text, and it kinda got messy at a certain point. Or, like, this doesn't work anymore. So we've changed to, …
Get the full transcript (4,550 words) + summary by email — free
One-time email with the complete transcript and AI summary of this episode. No account needed.
One email, no spam. We’ll also show you what SignalCast does.
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
One-way Doors
Aug 26 · 18 min
David Senra
David Heinemeier Hansson (DHH), Co-founder of 37signals
Jul 26
More from The Rework Podcast
Competing with giants, the end of SaaS & other listener questions
Aug 19 · 26 min
My First Million
DHH: $100M+ Advice That'll Piss Off Every Business Guru
Mar 17
Books, tools, and gear mentioned in this episode
SignalCast may earn commission on purchases via these links. As an Amazon Associate, SignalCast earns from qualifying purchases.
Tools
- KamalBy guest
by David Heinemeier Hansson
“David's open source tool Maersk triggered a trademark dispute with the Danish shipping company, resulting in police serving papers at Copenhagen Airport. He renamed it Kamal, which became his preferred choice anyway.”
- UmachiBy guest
by David Heinemeier Hansson
“David shares his pronunciation philosophy for Umachi, deliberately dropping the r sound despite how people naturally read it.”
Products
More from The Rework Podcast
We summarize every new episode. Want them in your inbox?
Similar Episodes
Related episodes from other podcasts
David Senra
Jul 26
David Heinemeier Hansson (DHH), Co-founder of 37signals
My First Million
Mar 17
DHH: $100M+ Advice That'll Piss Off Every Business Guru
a16z Podcast
Aug 17
Stripe’s AI Strategy: Build More, Not Less
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.
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 one show.
Start My Monday DigestNo credit card · Unsubscribe anytime