The Health System Opportunity Stack: A Builder’s Guide to the Most Underserved Enterprise in America
Abstract
Health systems are operationally underwater and analytically blind across dozens of high-value domains simultaneously. The gap between what exists commercially and what these organizations actually need is enormous, and the window for building category-defining companies inside this gap is open right now for a specific set of structural reasons. This essay maps the opportunity stack, explains why now is the right moment, and gives builders and investors a prioritized view of where the returns are and why.
Key themes:
- The biggest health system software gaps are in financial operations, not clinical AI
- Data network effects compound faster in health system contexts than in any other enterprise vertical
- The entry point to most of these markets is a CFO conversation about quantifiable revenue loss, not a clinical champion selling upward
- Several of these opportunities have natural exit buyers already circling the category
- Sequencing matters enormously, starting with the cheapest and fastest builds funds the harder ones
Table of Contents
Why health systems are the most compelling enterprise software opportunity in the market right now
The financial operations layer that nobody has built
Workforce intelligence and what $29 billion in agency spend looks like when it’s solvable
The operating room problem and why 65% block utilization is basically embezzlement
Prior authorization as a regulatory forcing function
Clinical variation and what two surgeons doing the same knee replacement tells you about margin
The data monetization play hiding in plain sight
Where to start and why sequencing is the whole game
Why health systems are the most compelling enterprise software opportunity in the market right now
Health systems are, by almost any analytical measure, the most complex operating organizations in the American economy. A single large health system manages tens of thousands of employees across dozens of employee classifications with wildly different compensation structures, benefits, union contracts, and scheduling requirements. It negotiates multi-year contracts with dozens of commercial payers where 60-70% of net patient revenue depends on the outcome. It runs an OR generating 40-60% of its margin in a physical space that represents maybe 3-5% of its square footage. It processes hundreds of millions of dollars in accounts payable annually, manages pension obligations that would terrify a mid-size manufacturer, operates clinical research programs, employs thousands of physicians with their own productivity compensation models, and does all of this while trying to keep people alive.
The software that exists to support most of these operations was not built for health systems. It was built for hospitals in the 1990s and 2000s, adapted for health systems as they consolidated, and patched together in ways that leave stunning amounts of operational intelligence on the floor. The CFO of a billion-dollar health system negotiates payer contracts using anecdote and historical rate data while United sits across the table with actuarial teams, claims data on millions of patients, and benchmarks across every market they operate. The OR director gets utilization reports on what happened last month, not predictions of what is going to happen next week. The nursing director finds out about a staffing gap when a shift starts, not 30 days before when something could have been done about it.
This is not a problem of ambition or intelligence inside health systems. These are sophisticated organizations run by capable people. It is a problem of tools. The commercial software ecosystem that serves health systems has prioritized EHR depth, billing compliance, and clinical documentation over operational intelligence, financial analytics, and the kind of real-time decision support that actually changes outcomes. Epic is extraordinary at what it does. What it does is not run a business.
The timing argument for building in this space right now has a few components that stack on each other. The financial pressure on health systems is at levels not seen since the post-ACA adjustment period, which means CFO conversations about quantifiable cost reduction and revenue recovery are shorter than they have ever been. The AI infrastructure available to builders today makes products feasible that would have required armies of data scientists three years ago – the extraction logic that used to take a team of managed care attorneys can now run through an API call. And the regulatory environment, particularly around prior authorization and data interoperability, is creating forcing functions that compress enterprise sales cycles from 18 months to something actually manageable. When a mandate says you have to do something by January 2027, the procurement process gets motivated.
The counterintuitive insight is that the biggest opportunities are not in clinical AI. Clinical AI is genuinely important and the market for it is enormous, but the competitive intensity is also extraordinary and the sales cycles are brutal because clinical validation requirements are appropriately high. The most compelling near-term opportunities are in financial operations, workforce intelligence, and data infrastructure – categories where the ROI is quantifiable, the buyer is a CFO or COO rather than a clinical committee, and the competitive landscape is weak because everyone with a healthcare AI thesis has been chasing clinical documentation and diagnostic support.
The financial operations layer that nobody has built
