I was telling the marketing director of a large hosting company that if I were him, I'd try to cross sell books from Amazon. If someone signs up to build an online store, don't you think they'd be interested in SEO? Or if they're getting a dedicated server, maybe they'd find the Linux Troubleshooting Bible helpful?
A few days after that conversation, I got an email from Amazon: "we noticed you purchased an ecommerce related book in the past and we thought you might be interested in an exciting new product from Amazon Services, WebStore by Amazon." Wow.
Coming soon: "we noticed you performed a search for Ruby on Rails; at EC2, you can get the entire Nginx/Apache/Mongrel/MySQL stack in one ready-to-deploy appliance." Or: "we noticed there's a disaster recovery book on your wish list. If you sign up for S3, we'll ship it out today at no cost!" Just you wait; it could happen!
So if you're one of the many people who've told me that Amazon is "not a hosting company", you might be right. At the same time, Amazon isn't a bookselling company either. Instead, it's kind of like a Möbius strip, which has one continuous outer surface. Amazon's core competency, I think, is in observing and learning from customer behavior, and using that knowledge to put whatever products people might want right on the counter.
In contrast, after Demand Media CEO Richard Rosenblatt's HostingCon keynote, I mentioned to someone that 1&1 ought to spin off its domain registration business, merge it with Sedo, Web 2.0-enable Sedo's antiquated domain parking service, and go after the secondary domains market big time. "But 1&1 is a HOSTING COMPANY," my friend said. "They do domain registration only so that they can sell hosting." But what if customers aren't registering domains so they can buy web hosting? I'm not sure you can make a product more relevant by giving it more shelf space.
BTW, I wouldn't be surprised if Amazon got into the domains business. Check out Fabulous.com CEO Dan Warner's "Aftermarket Value Innovation" presentation (PPT), where he discusses contextual domain search. For example, if a customer searches for "chicken risotto", Fabulous will show him available domains relating to recipes, restaurants, food, etc. Now imagine Amazon taking this contextual info and auto-populating each domain with an aStore. aStores-for-domains would feature top selling products from relevant categories (dynamically updated, of course), as well as items from each visitor's wish list and search history.
Some time ago, after Google published the Efficient Frontier/AdWords for Domains case study, many domain portfolio owners complained that Google's revenue sharing algorithm doesn't adequately account for the exceptionally high ROI that type-in traffic apparently delivers. It seems aStore-for-domains might offer better incentive alignment? Remember - Amazon's auto-recommendation technology is supposedly responsible for 30% of its sales. This means aStores can extract significantly more value than pay per click ads out of each direct navigation visitor - and pass on a % of such revenues to domain owners.