Social Media
USA

Nouncer

Seed Stage / Bootstrappedlost
1 Year
April 2008
Multiple Factors
Founded by: Eran Hammer

Nouncer (originally "Announcer") was an early microblogging and status-update platform that launched during the same era as Twitter. It aimed to be a more feature-rich, "serious" version of the microblogging concept, offering more control over privacy and how updates were distributed. The company shuttered after the founder realized that Twitter had already achieved the "network effect" required to dominate the category, making Nouncer's technical superiority irrelevant.

The Autopsy

SectionDetails
Startup Profile

Founders: Eran Hammer

Funding: Primarily bootstrapped

Cause of Death
The Critical Mistake

Underestimating the Power of "Simple": The founder admitted he over-engineered the product. He was building a "communications protocol" while the market just wanted a "shouting into the void" tool. By the time Nouncer was "perfect," Twitter was already a cultural phenomenon.

Key Lessons
  • Community > Code: In social networking, a "perfect" product with no users is a failure, while a "broken" product (Twitter's early 404 errors) with a thriving community is a success.
  • Identify the "Winner-Take-All" Early: If you are in a category driven by network effects (like social media), being 20% better is not enough. You have to be 10x better or completely different.
  • Focus on the "Hook": Nouncer's hook was "privacy and control," but it turned out the early microblogging audience actually wanted "publicity and chaos."

Deep Dive

In the reflective post-mortem, "The Last Announcerment," Eran Hammer provided a deep look at the philosophical differences that led to Nouncer's demise. The API Dilemma Eran Hammer was a protocol expert (he later became a lead author of OAuth). He built Nouncer to be a robust, secure way to handle data. However, while he was focused on the "plumbing" of microblogging, Twitter was focused on the "furniture." Users didn't care about the security of the API; they cared about who was replying to their tweets. The "Twitter is Down" Opportunity There was a period where Twitter was frequently crashing (the "Fail Whale" era). Nouncer tried to capitalize on this by being the "stable alternative." However, Hammer discovered that users would rather wait for Twitter to come back online than move to a new platform where they had to rebuild their follower count from zero. The Legacy Nouncer is a textbook case of a "technical success but a business failure." Its legacy is preserved through its founder's subsequent work on OAuth and other open standards that now power the modern web. The failure of Nouncer taught the developer community that "shipping early and capturing the network" is more important than "finishing the spec."

Key Lessons

1

Community > Code: In social networking, a "perfect" product with no users is a failure, while a "broken" product (Twitter's early 404 errors) with a thriving community is a success.

2

Identify the "Winner-Take-All" Early: If you are in a category driven by network effects (like social media), being 20% better is not enough. You have to be 10x better or completely different.

3

Focus on the "Hook": Nouncer's hook was "privacy and control," but it turned out the early microblogging audience actually wanted "publicity and chaos."

Share: