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.
2K views
Replies
Best
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
Report
@sheauwoei Yes, I so agree Sheau, we can always play with replacement names, but product comes first!
Report
I like buying the domain first! and creating the social pages.. just makes me feel more at ease.
Report
@christopherrobbins same I don't take any chances if I'm really serious about an idea
Report
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
Report
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.
Report
unless the domain really cheap, otherwise surely build product MVP first...that's just my opinion...have wasted hundreds on domains including cheap domain names too...
Report
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.
Report
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!
Report
Build the product first domain name ideas will prop up in my head while i code.
Report
yeah domain name comes first but idk if I spend 3 hours on it, maybe I should 👀
Report
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.
Replies
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
@sheauwoei Yes, I so agree Sheau, we can always play with replacement names, but product comes first!
I like buying the domain first! and creating the social pages.. just makes me feel more at ease.
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
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.
unless the domain really cheap, otherwise surely build product MVP first...that's just my opinion...have wasted hundreds on domains including cheap domain names too...
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.
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!
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.