Noyo

A quiet layer underneath your health plan

Somewhere right now, an employee at a 40-person company is clicking "enroll" on a dental plan. They will never think about what happens next. They should not have to. But for most of the history of employee benefits, that single click kicked off a slow-motion relay of spreadsheets, PDFs, and overnight files - the kind of data exchange that still smells faintly of a 1998 fax room.

Noyo is the company betting that nobody should ever smell that fax room again. It is a San Francisco-based benefits data platform that sits between insurance carriers, the software companies that manage benefits, and the HR teams who administer them. Its job is connective tissue: move member data accurately, in real time, through APIs instead of attachments. When it works, you don't notice. That is the entire point.

The industry it operates in is enormous and almost aggressively boring, which is precisely why it was left untouched for so long. Benefits administration runs on decades-old EDI 834 files and manual reconciliation. Errors are common, invisible, and expensive - a wrong digit can mean a denied claim at a pharmacy counter. Noyo's wager is that the boring layer is the valuable layer.

Benefits data was stuck in the mail

Here is the tension that runs through everything Noyo does: insurance is a real-time business pretending to be a batch-processing one. People get hired, get married, have kids, and switch plans every day - but the data describing those changes often crawls between systems on a weekly schedule, if it arrives correctly at all.

The cost of that lag is not abstract. A member change that takes weeks to propagate is a member who shows up at a clinic and isn't in the system. A discrepancy nobody catches is a billing problem six months later. The benefits world had learned to treat this friction as a law of physics rather than a bug.

Carriers wanted modern connectivity without ripping out the mainframes they'd run for decades. Benefits software wanted clean, reliable data without building a custom integration for every single carrier. Both sides were stuck, politely, waiting on each other. The gap between them is the market Noyo decided to live in.

Two people who'd seen the wiring up close

Noyo was founded in 2017 by Shannon Goggin and Dennis Lee, who met at the benefits-tech company Zenefits. Goggin built product there; Lee was a Carrier Integration Manager - which is a tidy way of saying he spent his days wrestling exactly the broken data pipes that Noyo would later set out to replace. They didn't hear about the problem secondhand. They lived in it.

The bet was unfashionable. While much of insurtech in 2017 chased shiny consumer apps, Goggin and Lee aimed at the plumbing - infrastructure that no end user would ever see or thank them for. Investors eventually agreed it mattered: Homebrew, Spark Capital, and Costanoa backed the early rounds, with the Cap Table Coalition joining to widen who gets to invest in startups like this.

An operating system for an industry that didn't have one

Noyo started as an API. It is now trying to be an operating system. In 2025 the company launched BenefitsOS - a deliberately grand name for the idea that the entire benefits lifecycle, from plan configuration to enrollment to ongoing QA, should run on one connected system rather than a patchwork of files and phone calls.

The more interesting trick is the recent pairing of AI with the APIs. Setting up a benefits plan correctly is fiddly, detail-heavy work - exactly the kind of task that breaks under human fatigue and shines under automated checking. Noyo uses AI to configure and QA plan data, catching the errors that would otherwise surface months later as a denied claim. Less glamorous than a chatbot. Considerably more useful.

The numbers behind the plumbing

Infrastructure companies are easy to doubt and hard to fake. The proof is in throughput. Ameritas - one of Noyo's earliest carrier partners - manages hundreds of thousands of lives through the platform, with most member changes processed in four days or less. Compared with the weeks-long status quo, that is less an improvement than a different category.

Then there is the network itself. Carriers on Noyo include Ameritas, Humana, Sun Life U.S., Principal Financial Group, Beam Dental, Angle Health and Brella; on the software side, partners span PlanSource, BambooHR and Workday. Each new connection makes the network more useful to everyone already on it - the unglamorous flywheel of a true data platform.

Make benefits data simply work

Noyo's stated mission is to transform how employee benefits data is managed and exchanged across the ecosystem - eliminating cost and complexity so people stay reliably connected to their benefits. Stripped of the press-release sheen, it is a promise about reliability: that your coverage is accurate, active, and there when you reach for it.

The culture reflects the problem. Noyo is product-led and customer-obsessed in a famously slow industry, remote-friendly with offices in San Francisco and Durham, North Carolina. It has been public about diversity and inclusion since its early funding days. None of that is unusual for a startup. What is unusual is the patience required to fix infrastructure nobody applauds.

The case for boring infrastructure

Benefits are not getting simpler. New plan types, more carriers, fertility and mental-health coverage, an aging workforce, a labor market that changes jobs constantly - every trend points toward more data, moving faster, with less tolerance for error. The manual status quo doesn't scale to that future. Something has to carry the load.

That is the long bet Noyo's investors are making: that the connective layer underneath benefits becomes as standard and invisible as payment rails became for commerce. If it works, an entire industry quietly reorganizes around APIs while nobody outside it notices.

So return to that employee clicking "enroll" on a dental plan. In Noyo's version, the click does what they always assumed it did. The data moves in real time, gets checked automatically, and the coverage is simply correct. No fax room. No six-month billing surprise. No clinic visit that ends with "you're not in the system." Just the quiet, ordinary feeling that the thing worked - which, in benefits, has always been the hardest thing of all to deliver.