Disrupting the world with new gTLDs

The new gTLDs are coming (seven launched today,) and most of the...

Disrupting the world with new gTLDs

The new gTLDs are coming (seven launched today,) and most of the press I've read has been of a similar vein: Most people will be confused, and it's never going to work.

But don't fall down that trap. The second law of disruption is that most people are not the intended audience. It's the underserved minority that first adopts and propels forward the disruption. So rather than get tied up on the obvious confusion between .link and .click, .tech and .technology, .eat and .food, or dozens of other potential conflicts, think about the underserved minority. That's where the real opportunity lies.

A few possible ideas come to mind:

Internal security - I doubt .ibm has anything to do with email services or public-facing web properties. IBM.ibm? Not likely. Instead, since International Business Machines owns and operates the registry, the trust factor for services accessing other services with that common gTLD goes up significantly. 

Professionals with a common name - Did you mean Bob Smith the .attorney, .doctor, or .florist? Of course, this has built-in scarcity, so expect a land rush and turf wars over these.

Companies that want non-English characters - There's a host of gTLDs with international characters that roughly translate to the .com we're intimately familiar with. This one is probably the biggest disruptor of the three, simply because it eliminates (or reduces) the need for some to switch between language/character sets when typing. 

But that's just scratching the surface. What do you see as the biggest disruptions coming from the new gTLDs? And which one are you waiting on? Currently, I'm torn between beer.diet or diet.beer. So I'll probably buy both. Just to be safe.
 •  0 comments  •  flag
Share on Twitter
Published on February 06, 2014 09:20
No comments have been added yet.