|
|
|
|
|
by subpixel
2067 days ago
|
|
I took this approach in the e-commerce space a decade ago, and assumed that no serious merchant would ever dream of paying for an e-commerce solution that required them to link to a subdomain on another company's domain to take orders. I was wrong. In fact, a lot of merchants saw the third-party domain as a status thing. There were thousands of merchants in one tribe and thousands in another. They are still doing it today, including at levels of commerce that prove that I was not just off, but that I totally misread the market. |
|
An argument against custom domains being a "premium" feature, then? If you don't have a paid plan, then you have to bring your own domain. Paying gets you the *.example.com status symbol. Makes sense — a custom domain usually requires technical expertise and some amount of inconvenience for users (not unlike a services company that publishes their source code to GitHub, which you can always set up and maintain for yourself, but if you want to use the company's hosted services, then you have to pay). Another part of the value proposition would be, "You're gonna have to spend money one way or another — either to a registrar or to us — so why not let it be us?"