Hey folks,<p>We built a consumer facing app using <x>app.com domain and it's been successful and has grown quite a bit. A few business owners have asked us for an API access to our backend and we already have a few paying clients.<p>We're in the processing of negotiating for the <x>.com domain. When we get it, we need to decide if we keep <x>.com domain for b2b and <x>app.com separate for b2c only or if we combine them all under the same domain.<p>Wondering if HN community has any thoughts on which approach would be the best? The advantages of combining is to increase the new domain's authority and traffic right away by redirecting existing traffic. The disadvantages is we need to make sure we get navigation right, etc. Are there any examples of startups doing both b2c/b2b that get it right?
Model that a lot of saas seem to use is:<p>put your consumer marketing site front and center at x.com<p>sub-brand your enterprise offering, and have a section explaining it, i.e. x.com/pro<p>this way you're maximizing your seo juice and consumer reach<p>the actual apps themselves can live on a subdomain, i.e. app.x.com for the consumer and pro.x.com for the enterprise<p>if/when the enterprise version really takes off, you could always rename it something unique if desired
So you have an existing domain? That's B2C? That's served you well? And you're going to redirect them to another domain? And that new domain is expanding (?) to cover B2C + B2B? And then you're going to manage those two target markets on that one site?<p>I would say that unless you can make a strong case to combine them, don't do it. If you intend to grow the B2B audience then give it the focus and attention it deserves. (Which also means the site / market that isn't broken keeps printing money).<p>If B2B gets enough traction and in the future merging the two makes sense, well that's a good problem to have.