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.
Building the product first instead of jumping straight into buying a domain for an idea that might never launch. 😄
Report
Used to be in the "buy the domain" camp, but recently switched my allegiance to "build the product first".
The reason is quite simple: I usually decide to rename the product in a few weeks anyways (which is frequently prompted by the change in feature scope based on user feedback)
A friend of mine has taken this to the extreme: He named his startup a completely ridiculous name which he knew wouldn't stick - on purpose - until he came up with a way better name down the road (e.g. when exiting the alpha phase etc.)
Report
IMO, it depends on the flavor 😄. If I’m 100% sure I’ll build the MVP, I grab the domain first 🛒. Otherwise, I build it first and grab a domain later 🚀.
Bonus: I’ve definitely parked a good domain before even knowing what I’d build 😅💡
The choice is based on what kind of product you're planning for. In my case, I'll ship the MVP first. Domain names are important, but I’d rather get the product out there and test the market. You can always work with what’s available for the domain later. And, no point in stressing over a domain when you haven’t validated the idea yet.
Report
I normally start with just building to see if the idea works out first, it’s easy to think you have got the best idea in the world to only realise it’s a no go! If I get in to the project and it’s good to go then I buy a domain.
Report
When I validated my idea, the first thing I did was buy the domain, not just the primary one, but similar ones too. Brand safety matters, especially when you spot a good deal. Don’t risk someone else grabbing it.
Report
With the SEO landscape changing because of AI… I would say Build First if it is more of a concept idea without current market validation. MVP’s are easy to spin up now, I think they can help you figure if you really want to go all in.
If it is something you know you will build regardless of market research/validation or website name, to the point where you are invested in researching launch strategies and you can envision the UI already, then Buy the domain First to make sure you get the one you need.
Report
Product first, cause I could change my mind and find a great domain cost lots of times.
At most of time, .com domain was taken, so you need more time of other domain.
Report
.com domain, totally, and all the time.
Report
Product is so much about the sentiment—getting the right name builds the confidence and some kinda momentum to get started with the product. :)
Replies
YourGPT
Building the product first instead of jumping straight into buying a domain for an idea that might never launch. 😄
Used to be in the "buy the domain" camp, but recently switched my allegiance to "build the product first".
The reason is quite simple: I usually decide to rename the product in a few weeks anyways (which is frequently prompted by the change in feature scope based on user feedback)
A friend of mine has taken this to the extreme: He named his startup a completely ridiculous name which he knew wouldn't stick - on purpose - until he came up with a way better name down the road (e.g. when exiting the alpha phase etc.)
IMO, it depends on the flavor 😄. If I’m 100% sure I’ll build the MVP, I grab the domain first 🛒. Otherwise, I build it first and grab a domain later 🚀.
Bonus: I’ve definitely parked a good domain before even knowing what I’d build 😅💡
Eternal AI
The choice is based on what kind of product you're planning for. In my case, I'll ship the MVP first. Domain names are important, but I’d rather get the product out there and test the market. You can always work with what’s available for the domain later. And, no point in stressing over a domain when you haven’t validated the idea yet.
I normally start with just building to see if the idea works out first, it’s easy to think you have got the best idea in the world to only realise it’s a no go! If I get in to the project and it’s good to go then I buy a domain.
When I validated my idea, the first thing I did was buy the domain, not just the primary one, but similar ones too. Brand safety matters, especially when you spot a good deal. Don’t risk someone else grabbing it.
With the SEO landscape changing because of AI… I would say Build First if it is more of a concept idea without current market validation. MVP’s are easy to spin up now, I think they can help you figure if you really want to go all in.
If it is something you know you will build regardless of market research/validation or website name, to the point where you are invested in researching launch strategies and you can envision the UI already, then Buy the domain First to make sure you get the one you need.
Product first, cause I could change my mind and find a great domain cost lots of times.
At most of time, .com domain was taken, so you need more time of other domain.
.com domain, totally, and all the time.
Product is so much about the sentiment—getting the right name builds the confidence and some kinda momentum to get started with the product. :)