Kismet Health
A specialized telehealth toolset can be worth more inside a larger buyer than as a standalone SaaS. Recognize the tuck-in ceiling early.
Kismet Health was a Digital Health / Pediatric Telehealth startup founded in 2020 in USA. It raised $6M before collapsing in 2025 — 5 years of runway burned. IdeaProof's AI Failure Score: 54/100, driven by acquired by kooth for its telehealth platform, ending standalone operations. The shutdown affected employees, investors, and the broader Digital Health / Pediatric Telehealth ecosystem. This case study breaks down the timeline, root causes, competitors that won, and replicable lessons for founders validating similar ideas today.
Why did Kismet Health fail?
Kismet Health failed in 2025 after 5 years of operation, losing $6M in raised capital. The root cause was acquired by kooth for its telehealth platform, ending standalone operations. Key lesson: A specialized telehealth toolset can be worth more inside a larger buyer than as a standalone SaaS. Recognize the tuck-in ceiling early.
2020 → 2025
$6M
Digital Health / Pediatric Telehealth
USA
IdeaProof AI Failure Score
What Happened: The Timeline
2020
Kismet Health founded in USA. Positioned in digital health / pediatric telehealth.
2020-2022
Raises $6M from Undisclosed seed investors.
2024
Warning signs emerge: vertical telehealth saas lacks pricing power.
2025
Shutdown announced. Root cause: acquired by kooth for its telehealth platform, ending standalone operations.
Root Causes
Kismet Health was a virtual care platform designed specifically for pediatric and family telehealth, with age-adaptive UX for children, adolescents and older adults. Founded in 2020, it built customized clinician tools that differentiated it from horizontal telehealth stacks. In 2025 it was acquired by London-listed digital mental-health company Kooth for its platform IP; Kismet founders detailed the deal on the company blog. Terms were not disclosed but sources characterize the transaction as a strategic asset purchase rather than a growth-stage exit.
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.
- Vertical telehealth SaaS lacks pricing power
- Kooth needed pediatric UX for US market entry
- Independent sales cycle too slow
- Sub-$10M raised limits standalone runway
2024: Warning signs emerge: vertical telehealth saas lacks pricing power.
2025: Shutdown announced. Root cause: acquired by kooth for its telehealth platform, ending standalone operations.
Base rates
A single failure is an anecdote. These base rates give you the denominator — how common this outcome is across all startups matching Kismet Health's profile. Sources are third-party; we do not restate them as our own claims.
of digital-health startups fail to reach breakeven; reimbursement complexity + regulatory approvals extend runway needs beyond typical VC horizons.
Rock Health State of Digital Health (2023)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
Frequently Asked Questions
Sources & Confidence
Every data point is tagged with its source type and our confidence in it. How we grade sources.
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 Kismet Health.
Spotted a factual error?
Approved corrections are published in the public changelog with attribution.