Phoenix
Phoenix was a digital "dead man's switch" that allowed users to write emails to be sent to loved ones after they died. Users had to "check-in" once a year; if they didn't, the app assumed they were deceased. The startup failed because the founder over-engineered the business (legal, logos, expensive domains) before validating if people actually wanted to pay for such a service.
The Autopsy
| Section | Details |
|---|---|
| Startup Profile | Founders: Enrique Benitez Funding: Bootstrapped |
| Cause of Death | Market Fit: Yes |
| The Critical Mistake | The "KISS" Failure: The founder failed to "Keep It Simple, Stupid." He spent 6 months coding, hired a lawyer, and opened a dedicated bank account before getting a single customer. Market Mismatch: Young people (the target audience for the tech) don't care about death. Old people (who care about death) don't trust or understand the technology. Friction-Heavy Onboarding: The sign-up flow was too long, didn't have social logins, and lacked a PayPal option, causing thousands of visitors to abandon the site before completing a "check-in." |
| Key Lessons |
|
Deep Dive
In his interview with Failory, Enrique Benitez reflected on the high cost of "playing house" as a founder. The Perfectionism Trap: Before he had a single user, Enrique bought an expensive .co domain, an SSL certificate, and a custom logo. He used high-end transactional email services and expensive servers. He was paying for "Enterprise-level" quality for a project that had zero revenue. The Metrics Don't Lie: Phoenix had thousands of visitors from Product Hunt and Hacker News, but only 45 sign-ups and $0 in revenue. The founder realized that "cool" doesn't mean "buyable." People found the idea interesting but were too "lazy" to actually write the letters or pay the $30/year subscription fee for something they hoped wouldn't be used for decades. The Legacy: Phoenix is a classic case of "Over-Engineering the MVP." It serves as a reminder that you should ship the smallest possible version of your idea immediately. Enrique learned this lesson so well that his next project, Spoil Your Enemies, took only 2 weeks to build and became profitable almost immediately because he kept the costs and the tech simple.
Key Lessons
Over-Engineering the MVP: You should ship the smallest possible version of your idea immediately.
The $30/Month "Ghost" Expense: Paying for "Enterprise-level" quality for a project with zero revenue.
The Metrics Don't Lie: Thousands of visitors but only 45 sign-ups and $0 revenue means "cool" doesn't mean "buyable."