{"id":102388,"title":"Plena Health: The AI operating system for specialty medical practices","tagline":"The full stack AI operating system for specialty medical practices","body":"**TL;DR**\n\nPlena is the full stack AI operating system for specialty medical practices. We automate the administrative work that keeps clinics running — referrals, fax intake, scheduling, procedure compliance, records, and collections. Everything that isn't the medicine.\n\n**In 8 months, we've grown 17x and crossed seven figures in contracted ARR.**\n\nSo far we cover six specialties across eight states, all on annual or multi-year contracts, with 80% of our growth through word-of-mouth.\n\n\u003chttps://youtu.be/xWw9kNYckHQ\u003e\n\n**The Problem**\n\nMy mom is a doctor. Plena's office sits inside her clinic — she was our first user. I grew up watching her run a practice, and the pattern was the same in every clinic I later embedded in: a doctor's day eaten by everything that isn't medicine.\n\nIndependent specialty practices are squeezed. Staffing costs rising, reimbursements tightening, payers using automation to deny and downcode claims.\n\nMeanwhile, practices run critical workflows across EHRs, clearinghouses, portals, fax, spreadsheets, phones, and email. A single referral: read the fax, match the patient, extract clinical details, check insurance, update the EHR, attach documents, route tasks, chase missing info. That's one workflow. Practices run dozens daily.\n\nMost software adds another portal, another login, another vendor. Point solutions cover a slice. Staff stitch the rest together.\n\n\\\n**Why Point Solutions Can't Get You to Labor Replacement**\n\nThe real goal isn't automating one workflow. It's labor replacement — and you can't get there one feature at a time.\n\nNo single piece of software works for all specialty practices. Cardiology, GI, urology, ortho are too different from each other. Even two clinics in the same specialty are too different. Off-the-shelf can't cover the surface area.\n\nSo we took a Palantir-like approach: a base platform of reusable building blocks — workflow primitives, EMR integrations, agent harnesses — that lets us assemble exactly what each practice needs. Deep discovery, build to spec, stand it up in a day or two. Every engagement feeds the platform, so the next build is faster. That's the flywheel.\n\nAI is what makes this newly possible — final-mile customization at speed is exactly what AI is good at. And it's why we're an easy yes: no rip-and-replace, no retraining. We slot into what practices already run and take more off their plate over time.\n\n**How Plena Works**\\\nPlena automates workflows end-to-end across the systems a practice already uses — EHRs, fax, phones, clearinghouses, payer portals, patient communication. We don't replace those systems. We don't ask staff to learn a new one.\n\nSome competitors force practices to migrate into a walled garden — abandon the EMR, retrain the team, rebuild data flows. That's why their sales cycles are slow. We do the opposite: we live inside what's already there, and quietly take over the rote work end-to-end.\n\nCustomers start with one painful workflow — referrals, collections, scheduling — then expand as they see it work.\n\n\\\n**Where This Goes**\n\nWe start as an automation layer on top of what practices already have. Over time we cannibalize the rote work and the other vendors a practice is stitched together from — until the EHR is just a database we read and write to. From there, even the EHR becomes a turnkey switch instead of the migration nightmare it is today.\n\nThat's the system specialty practices end up running on.\n\n\\\n**Our Story**\n\nEyad and Ahmed were both raised in medicine — Eyad's mom and Ahmed's dad are doctors. The combination — engineers who grew up watching practices run — is why we kept seeing the operational problem when other founders saw something else.\n\nEyad is a Waterloo engineering grad — Datadog and Shopify before Plena, 3 years embedded in clinics. Ahmed built tier-zero infrastructure at AWS, with a background in nuclear systems before that. Specialty practices didn't need another lightweight tool — they needed infrastructure.\n\n\\\n**Our Ask**\n\nIntros to independent specialty practices, administrators, and physician owners — especially orthopedics, GI, dermatology, ophthalmology, ENT, urology, and multi-location groups. Best fit: high admin volume and disconnected systems.\n\n[eyad@plena.health](mailto:eyad@plena.health)\n\nEyad and Ahmed","slug":"QdQ-plena-health-the-ai-operating-system-for-specialty-medical-practices","created_at":"2026-06-01T19:17:08.692Z","updated_at":"2026-06-20T20:26:21.284Z","total_vote_count":52,"url":"https://www.ycombinator.com/launches/QdQ-plena-health-the-ai-operating-system-for-specialty-medical-practices","share_image_url":"//bookface-static.ycombinator.com/assets/ycdc/yc-og-image-c440a0ad1dacfb86eeeb343717479cc54d256614449b4ef719977a0a451f8bc8.png","company":{"id":31493,"name":"Plena Health","slug":"plena-health","url":"https://www.plena.health/","logo":"https://bookface-images.s3.amazonaws.com/small_logos/3904753c66e12d522cb76c36f26a8325b7a90c7e.png","batch":"Spring 2026","industry":"Healthcare","tags":[],"search_path":"https://bookface.ycombinator.com/company/31493"}}