Asset-Light Healthcare Middleware
Foundation Health
Foundation is building the software layer around healthcare capacity, not the capacity itself. That means new volume can be added by routing work into outside physician groups, pharmacies, and labs instead of opening clinics, hiring full time clinicians, or carrying drug inventory. In practice, the company sells APIs and workflow tools, then earns recurring software fees plus usage fees as partners send more consults, prescriptions, and tests through the network.
-
The product is designed to replace labor heavy coordination work. A customer can embed intake on its site, trigger an async physician review, route the approved prescription into a pharmacy network, and let Paige AI handle benefits checks, prior auth packets, refill reminders, and patient outreach. That keeps Foundation concentrated in software and orchestration rather than service delivery.
-
The cleanest comparison is with more vertically integrated models. Amazon combines telehealth, 150 plus One Medical offices, and Amazon Pharmacy. Hims & Hers has acquired U.S. pharmacy and peptide manufacturing assets. Those models can capture more of the care stack, but they also carry higher fixed costs, more staffing complexity, and slower geographic buildout.
-
The tradeoff is dependence on partners. Foundation can move fast because it does not own pharmacies or employ clinicians directly, but that also means network relationships are the core asset. The Intermountain deployment shows where this model fits best, selling automation into existing pharmacy operations rather than replacing them with owned infrastructure.
This model points toward Foundation becoming healthcare middleware. If more brands, health systems, and drug makers want to launch pharmacy and telehealth programs without building their own clinical and fulfillment stack, the winner will be the company that becomes the default API and automation layer sitting between patient demand and fragmented care supply.