Lemonade (Detailed)
Lemonade promised AI would revolutionize insurance underwriting, but its loss ratios remained above 90% — far worse than traditional insurers — proving that technology alone can't fix insurance economics.
Lemonade (Detailed) was a InsurTech/Home startup founded in 2015 in undefined. It raised $480M before collapsing in 2025 — 10 years of runway burned. IdeaProof's AI Failure Score: 72/100, driven by unsustainable loss ratios & failed ai underwriting. The shutdown affected employees, investors, and the broader InsurTech/Home ecosystem. This case study breaks down the timeline, root causes, competitors that won, and replicable lessons for founders validating similar ideas today.
Why did Lemonade (Detailed) fail?
Lemonade (Detailed) failed in 2025 after 10 years of operation, losing $480M in raised capital. The root cause was unsustainable loss ratios & failed ai underwriting. Key lesson: Lemonade promised AI would revolutionize insurance underwriting, but its loss ratios remained above 90% — far worse than traditional insurers — proving that technology alone can't fix insurance economics.
2015 → 2025
$480M
InsurTech/Home
IdeaProof AI Failure Score
What Happened: The Timeline
Founded by Daniel Schreiber and Shai Wininger with AI-first insurance model
IPO at $29/share, market cap reaches $10.6B
Loss ratio exceeds 90%, launches car insurance product
Stock drops 90% from peak, loss ratio remains above 80%
Market cap below $1B, still unprofitable after 10 years
Root Causes
Causal Chain
This is our reading of the causal chain — separated from the verifiable facts above. Timeline dates, funding numbers and filings are facts (see methodology); root / proximate / terminal attribution is judgement based on public evidence.
A combination of demand-side, execution, and capital-market pressures that this record documents without isolating a single dominant driver.
- AI underwriting didn't outperform actuarial models
- Attracted adverse selection — high-risk customers seeking easy sign-up
- Loss ratios consistently above 80% vs industry 60-70%
- Expansion into car insurance multiplied losses
- Competitor "State Farm" captured the same market: undefined
2025: cessation of operations after failing to secure additional capital or a strategic buyer.
Base rates
A single failure is an anecdote. These base rates give you the denominator — how common this outcome is across all startups matching Lemonade (Detailed)'s profile. Sources are third-party; we do not restate them as our own claims.
of startups ultimately fail — including ~10% that fail in the first year and the rest across the following decade.
Startup Genome / CB Insights aggregate (2024)of new US employer businesses survive past their 10th year (Bureau of Labor Statistics BED series).
US Bureau of Labor Statistics — BED (2024)of Series A rounds ever graduate to Series B; the rest run out of runway or pivot without a follow-on.
CB Insights Venture Capital Funnel (2023)Key Lessons Learned
1. Insurance AI hype vs actuarial reality
Lemonade claimed AI would make better underwriting decisions than traditional actuaries. In practice, their AI approved too many high-risk policies because it optimized for growth, not risk selection.
2. Easy onboarding attracts adverse selection
Lemonade's frictionless sign-up (90-second policy) attracted customers who were rejected by or too lazy for traditional insurers — exactly the high-risk pool you don't want.
3. SoftBank valuations create zombie companies
At $10.6B peak valuation, Lemonade needed to become a top-10 US insurer to justify the price. Now trading at $1B, it's too expensive to acquire but too unprofitable to sustain.
Competitors That Won
State Farm
Why they won:
Progressive
Why they won:
Root Insurance
Why they won:
Frequently Asked Questions
Could This Failure Have Been Prevented?
IdeaProof's AI validates market demand, competitive positioning, and business model viability in minutes — catching the exact issues that sank Lemonade (Detailed).
Related Failures
Spotted a factual error?
Approved corrections are published in the public changelog with attribution.