
Health enterprise API for data on doctors, insurance, costs, & quality
Turn this teardown into a decision-ready prompt for ChatGPT, Claude, or your agent.
If you only have a few minutes to spare, here’s what investors, operators, and founders should know about Ribbon Health (S17).
Ribbon Health turned one of healthcare's least glamorous problems into a valuable infrastructure company. Its API helped health plans, navigation services, and digital-health products answer basic questions that are surprisingly hard to answer: Where does a clinician practice? Which insurance networks do they accept? Are they taking patients? What do they specialize in, and how much might care cost? Ribbon assembled and corrected those records, then exposed them as software infrastructure.[1]
H1 acquired Ribbon in a cash-and-stock deal that closed in late December 2024. The price was not disclosed. Ribbon had more than 50 customers, tens of millions of dollars in revenue, and data that reached more than 20 million patients a year. H1 chief executive Ariel Katz said Ribbon was not running out of money and described a competitive sale process.[2] The exit consolidated Ribbon's health-plan and patient-navigation data with H1's pharmaceutical and clinical data.
That makes Ribbon useful as a case study in a successful pivot. The founders began with care navigation, learned that bad provider data undermined every recommendation, and rebuilt the company around that underlying constraint. Their internal data tool addressed a broader market than the navigation service that required it.
Nate Maslak's interest in healthcare came from his family. After immigrating from Russia to Cleveland, his mother developed severe joint pain. The family received referrals to the wrong specialists, accumulated medical debt, and nearly went bankrupt before learning that yoga had probably caused the injury.[3] Co-founder Nate Fox had his own experience with care coordination. Born with a severe hearing impairment, he credited access to the right specialists with allowing him to hear and speak almost perfectly.[3]
The two met at Harvard Business School. Maslak had worked in healthcare consulting, where he analyzed claims in spreadsheets. Fox had studied engineering at MIT, worked at Microsoft, and helped build advertising technology at Unified.[4] Y Combinator dates the company's founding to 2016.[14] Its first product was a care-navigation service for employers; members could search for care themselves or receive proactive help finding and booking a clinician.[3]
The service ran into the same defect that had frustrated Maslak's family: directories could not reliably say where a doctor worked or which insurance they accepted. Maslak later put the apparent contradiction plainly: “At first glance, provider data shouldn't be that hard to maintain. We've had YellowPages forever.” He said even contact details in a typical health-plan directory were 50% accurate or less, before accounting for changing insurance participation.[5]
Fox said the mission stayed stable while the method changed: “Our mission is to help make every healthcare decision be cost effective, high quality and convenient. That's never changed, but what has sort of evolved is that how.”[6] The team stopped treating provider data as an internal dependency and began selling it. In 2018, it rebranded the resulting data platform as Ribbon Health.[3]
Read the complete post-mortem, the rebuild playbook, and the exact reasons Ribbon Health is still worth studying now.