Aaron O'Leary

✅ POLL: Do you buy the domain first or build the product first?

by

Let’s settle this once and for all.

Do you spend 3 hours trying to find a clever .com before writing a single line of code? Or do you ship the MVP and slap on whatever domain wasn’t taken at the time?

Cast your vote and tell us why.

Bonus points if you’ve ever changed your product idea because the domain wasn’t available.

1.9K views

Add a comment

Replies

Best
Nick Launches
Lately, I’ve been buying the domain first. It helps me fully commit to the project, plus it’s way easier to organize everything (docs, services, documentation, etc.) right from the start. Trying to rename everything after building an MVP is just a headache I’d rather avoid. Curious what I’m working on lately? Check out my profile I am always building something new!
Dmitrii 迪玛 Lunin

Domain and the logo!)

Tom Ideaxton

@dmitry_lunin yessss!! LOGO too!

Sergei Kovalev

First, domain. Code second. Financial reality comes third 😂

We grabbed .rent because .com was only available through an overpriced broker with no direct contact or negotiation.

At the time, it didn't make sense to spend money on a domain that wasn't being used, had no website or traffic, and had no response from the owner.

So, we made the call to secure the next-best domain, build the product, and earn the right to come back for the .com later — if the project takes off. Until then, aera.rent works 😁

Brad Simon

I want to make sure I can have a matching domain and company name. It would irk me if my company and domain name didn't match. Sometimes it makes it very hard to come up with a great company name

Jagriti Kumar
I did a bit of both. I created an absolute base version of my idea (just vibe coded for a couple of hours) and then bought the domain. I do think you should atleast do a quick search of domain ideas before fully just building out MVP and later struggling with domain names.
Ran

We built the product first. I mean, we had a tool live before I even checked if the name was taken. Our first domain looked like a phishing site, but it worked. People used it and then they told their friends and acquiantances. I've come to realise that merely having a good name won't build your business, but a working product will. The name can evolve but your product can’t grow if it doesn’t exist.

Timothy Brown

I named draiper.com after Don Draper the creative director from the popular TV series Mad Men. Since my product is creative AI content creation I couldn't believe my luck when I found the AI spelling of Draper was available. I pounced and then built the product.

Marcelo Cardoso

having a domain first just helps me dream better about what it can become....

Alisher Kabduakhitov

For sure domain, if project is serious. You gotta start thinking about branding and other stuff, which are heavily connected to your domain!

Furqaan

Definitely buy the domain first.

A great name sets the tone for your entire solution, and let’s be honest, thinking of a creative domain and making it yours is exciting. But don’t let it rot in the domain graveyard. Execution is everything ;)