Ask HN: Is having two brand names a dumb idea?
I'm guilty, I've fallen in love with two names and can obtain both domains. They have a very different feel to each other, and halfway in between is the feel I want to achieve.
I am the cofounder of a cloud computing start up and we are developing an application to assist in managing cloud deployments.
The two domains are in the format: XXXXXXXcloud.com YYYYYapp.com
I'm not dumb enough to use both just because I love both, but the first one sounds perfect for a company name and the second for the app name.
Is it foolish to use both as we only have one product? Should the company name and the app name be the same?
8 comments
[ 2.9 ms ] story [ 28.7 ms ] threadIn my own case, my company name is "Fogbeam Labs" and I fully intend to name the product(s) something very specific when we have something to ship. http://www.fogbeam.com will always just be a link to the main company website... any hosted / SaaS apps will have their own domain. I should probably point out, though, that our primary focus is on the B2B / Enterprise Software market, and my biases are towards thinking in those terms. Any or all of this may have absolutely zero relevance to your situation. :-)
How would your strategy change if you only planned to have one product in the next few years?
A couple of companies from our industry are good examples here:
http://newrelic.com/ - Company name and single product name are both the same.
http://www.3tera.com/AppLogic/ - Company name and product name different (ignore their acquisition by CA for this example).
To me, 3tera's AppLogic sounds more suitable for B2B than New Relic. It also leaves us open to producing other products in the future, should we wish to.
I'm not sure that the initial plan is to have lots of products, but the current plan is for a suite of products that work in concert with each other, but also deliver some value independently. There would be a specific brand to cover those products, for sure. Any future products might come out under a different brand name, but that's looking ahead an awful lot for us right now.
I will say that, in general, I think IBM have struck a good balance, for a company that has a broad product line... they have lots of products, but the fall nicely into the various divisions: Lotus, DB2, Tivoli, WebSphere, etc.
How would your strategy change if you only planned to have one product in the next few years?
Good question. This is an area that I've only recently started doing a lot of thinking, and it's all still a bit "up in the air."
Better phrased, my question should have been "Should a startup with one product, and no near future plans to add another, use the same name for the company and product?"