Aaron O'Leary

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

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.

794 views

Add a comment

Replies

Best
Tom Ideaxton

Hahaha, right on target 😂

Yeah! I buy the .com domain first and only then start building the MVP. Lol.

It often happens that I come up with a cool name for a project, but the domain is taken by resellers and costs $50,000. And it's so frustrating. And then I spend hours searching for a replacement name for the project.

Recently, I got lucky. I came up with a name for my horror streaming platform and wanted to buy the domain, but it cost $27,000 from resellers. And just a few days ago, it became available, and I bought it for $20. The Scaryx streaming platform will be!

Ryan Dean

@ideaxton these reseller prices are wild. Launchlist.com $345K lol. I've gotten lucky at times like you and scored the domain later for the lower price, but for now, I'll stick with DreamerMade.com.

Aaron O'Leary

@ideaxton That's wild that you got it for $20!!

Tom Ideaxton

@aaronoleary When I saw that the domain was available on the registrar's website, I didn't even think twice and bought it. I've never been so happy about buying a domain. Now the main thing is to finish the project 😂

Nick
@ideaxton How important is it nowadays to have a .com domain? Does it really help with anything other than people’s trust? Or does it depend on the type of company or product?
Tom Ideaxton

@nicksuccesslaunch Personally, I would trust a brand with a .com domain more than one with a .tech, .biz, or .com.net domain. Of course, there are AI services for which a .ai or .io domain is appropriate.

I love the .com domain and try to use it for my projects. For many people, it is the standard. What do you think?

Brad Simon

@ideaxton The one time I didn't buy it first, they wanted $10,000. I said, it was not worth it and bought similar with a dash in it. The STILL keep emailing me (annoying). I will occasionally reply, "is it $50? That is all it is worth to me." Hoping, that they will email me and eventually tell me is it $50. My hopes are not that high. It was just a side project for me to test AI with. One of my first vibe coded apps. Check-OneTwo.com

Piotr Kusiak

Depending if you have the name of the product figured out. It's so much easier to secure a domain than building an MVP. U usually also need the domain for email / workspace / setting up any legal stuff, terms of service / support. Having a small landing page with newsletter should be the first step when building a product.

Tom Ideaxton

@k_piotr agree with you!

Aaron O'Leary

@k_piotr Yeah this makes sense. The domain is a lot more than just the branding itself

Stefan Weiss

@k_piotr agreed! especially the email part for early feedback is key. Otherwise people will wonder what you are doing. For prototyping / testing, you will also need a domain imo.

Nika

Building a product first because many projects are abandoned and unfinished :D I know myself. Would buy a domain for a product that will not exist. :D

Tom Ideaxton

@busmark_w_nika Would buy a domain for a product that will not exist. How painful it is to read and realize that there are 18 such domains in my life.

Nika

@ideaxton 💔 It is a huge loss. I am trying to reduce costs and if the domain purchase is not speculative (like selling in the future for more money), they I will not buy a domain :D

Novicto H

@busmark_w_nika Took the words out of my mouth there Nika, I've done too many of those in the past, spent hours to get the name at the best price, but then in a few months, the project gets abandoned!

Nika

@novicto_herlistianto Yeah, I used to keep domains to projects that existed but didn't go anywhere, so I cancelled them too.

Philippe Bernard
I definitely buy my domains early. But I always choose cheap extensions. I never go for $50+ named unless the project is already viable.
Borja DR
Launching soon!

Build the product first. That said, I know a couple of successful founders who bought a domain early just because they liked the name. Later on, they built a product and ended up using that domain.

Csaba Zoltan Moldovan

let me drop the mic.

customers pay for the product not for the name (Unless you are Apple, but no, you are not, at least not today)

deliver the product harvest hard cash and buy any domain name you want.

idea = 1%
delivery = 99%

kiss kiss boom boom

Tom Ideaxton

@moldovan You may be right, but the name also plays an important role in the project.

People choose books by their covers.

In stores, people buy products with their eyes.

No matter how delicious a chocolate bar is, if it's called Sakharoladon, who will buy it?

And so on.

The name should be easy and memorable. So that you can type the website into the address bar of your browser from memory, rather than Googling it.

Csaba Zoltan Moldovan

@ideaxton Before you post to anything to any store you need to show to friendly customers to test ❤️ they will even give you feedback about the brand. something you use as a lamp shade in your country could be a fruit bowl in an other culture. brands are changing so the products. better to have fundaments

Novicto H

@ideaxton  @moldovan  hmmm a fruit bowl lamp shade, or was that a lamp shade fruit bowl, lols. Either one, I agree with you Csaba, delivery is more important!

Youssef Kacem

I always build the product first — for a few key reasons:

  • The product often evolves during development. Buying the domain too early locks you into a name that might no longer fit.

  • Sometimes the client changes their mind or pivots completely after payment or feedback — wasting the domain cost.

  • It's better to validate the core idea and get user feedback before committing to branding and domain.

Once the product works and shows potential, finding a domain becomes much easier (and more strategic).

MVP first. Domain later.

@youssef_kacem Totally agree with first point. Unless u clearly figure out the vision of the new product at start. Evolution always happens.

Youssef Kacem

@mickeyqiu Exactly thanks for the reply !

Ryan Dean

Buy the domain, get that dopamine hit. Just don't spend too much time on it. Pro tip: do a quick USPTO search to make sure the name isn't trademarked.

Aaron O'Leary

@ryan_dean See, I buy the domaine, get dopamine hit, forget about building, get a renewal notice a year later

Ryan Dean

@aaronoleary you figured out a subscription-based dopamine model lol

Sheau Woei Lin

We usually have the concept of the product and build the initial prototype before we buy the domain of the website (less than $20). If the domain wasn't available, we play with the replacement names until we find one that is available. Untimately the product itself is more important than the domain name. :D

Novicto H

@sheauwoei Yes, I so agree Sheau, we can always play with replacement names, but product comes first!

Christopher Robbins

I like buying the domain first! and creating the social pages.. just makes me feel more at ease.

Jordan
@christopherrobbins same I don't take any chances if I'm really serious about an idea
Hunter Barry

We had a cheap work in progress domain while we had most of the product built and then continued the (protracted and frustrating) process of negotiating for the domain we wanted. We started with www.health-studio.ai versus the current www.healthstudio.com we acquired months later. We redirected the old site once we had the new domain

Novicto H

@hunter_barry yup, I think domain redirections solve a lot of worry later! Nice insight Hunter!

AJ Batac

I have a controversial opinion about this, I build the product first, and then find a name for it. Just like everything else, cook the food first, open a resto, name the resto. Have a kid, name it after. Same :D

Holden Lewis
Launching soon!

Product first, domain later.

If I had a nickel for every time I've worked on a project whose story was clouded by a domain/product name they chose and committed to before PMF stabilized, I'd have, like, 4 nickels. I also see a lot where brand develops too far ahead of product and it ends up being vaporware.

Flipside, I have also seen companies put a placeholder as their company name, forget about it, and then get sort of stuck with a really lame name/brand that also works against the product.

Balance, I guess? Everyone on this thread has good POVs.

Sunny_K_S

I'll first build the product first. Still, some founders grab a domain they like early on—and it ends up being the perfect fit later.

Michael Schuchardt

Securing the domain name should be your top priority! If you’re unsure or find a better name later, no problem — but don’t risk using a name before you own the domain. If someone else registers it first, you could lose it or end up paying a hefty price. On the flip side, registering the wrong domain only costs around $10–$15. Worth the peace of mind!

Hussain Attari
Build the product first domain name ideas will prop up in my head while i code.
Samuel Anozie
yeah domain name comes first but idk if I spend 3 hours on it, maybe I should 👀
Jamie

I buy the domain about half way thru the project, when I think it's viable and not at risk of being abandoned. Now there are plenty of alternative TLDs, so if the .com get's snatched can pickup the .app, or .io, .ai or whatever.

Nick
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!