Competitive Landscape — a16z Infrastructure Taxonomy
How each company in a16z's healthcare infrastructure map relates to DaisyAI.
Relevance: Direct Competitor | Adjacent | Potential Partner | Customer's Vendor | Not Relevant
Payer Infrastructure Stack
Product Management & Engagement
HealthEquity — Not Relevant HSA/FSA administrator. Benefits account infrastructure. No overlap with UM.
HealthEdge — Customer's Vendor (important) Modern core admin platform for health plans. If a payer runs HealthEdge, our outputs (UM decisions, clinical reviews) need to integrate with their system. Understanding their data model matters for implementation. Could also be a partnership — they need AI-powered UM capabilities and don't build it themselves.
Pega — Customer's Vendor BPM/workflow platform some payers use for care management automation. We might encounter Pega-built workflows at payer clients that we'd either integrate with or replace. Less relevant than HealthEdge.
CAPS (Core Admin Processing Systems)
TriZetto (Cognizant) — Customer's Vendor (critical) If HealthEdge is the modern CAPS, TriZetto is the legacy one — and it's everywhere. Many of our potential payer customers run TriZetto for claims adjudication. Our UM outputs feed downstream into claims decisions made in TriZetto. Integration capability with TriZetto is probably a requirement for scaling.
Solutran — Not Relevant Benefits payment processing. No UM overlap.
Care Management
ZeOmega — Direct Competitor / Incumbent to Displace This is the one. Their Jiva platform is the legacy care management / utilization management / population health tool for payers. It's what sits in the seat we want. Workflow-based, not AI-native. When a payer says "we already have a UM system," they probably mean ZeOmega or something like it. Our pitch is: we're the AI-native replacement for what ZeOmega does with rules engines and manual workflows. Or we augment/sit on top of their system rather than ripping it out. Either way, need to understand ZeOmega deeply.
Risk Management
Cotiviti — Adjacent (expansion opportunity) Payment integrity, fraud/waste/abuse, risk adjustment. These are downstream from UM — once a clinical review is done, payment integrity is about making sure the claim is accurate. Natural expansion path: if we're already analyzing clinical data for UM, we have the data to flag payment integrity issues too. Cotiviti is a multi-billion dollar company — the market is huge.
Verisk — Adjacent Risk analytics and actuarial. More insurance-generic, less healthcare-specific than Cotiviti. Their health analytics could inform UM criteria (what's the risk profile of this population?) but they're not directly in our space. Less relevant day-to-day, more relevant strategically if we ever move into risk adjustment.
Provider Network
MultiPlan — Tangentially Relevant Network management and rate negotiation. UM decisions sometimes interact with network adequacy (is this provider in-network? is there an alternative?). Loose connection but not a priority relationship.
HealthStream — Not Relevant Workforce learning management and credentialing. No UM overlap.
Financial Systems (Payer)
No specific companies listed. Generic accounting/AP/AR infrastructure.
Provider Infrastructure Stack
Revenue Cycle
Solventum (3M spin-off) — Adjacent (provider-side mirror) CDI and coding. On the provider side, they help hospitals document and code better to maximize revenue. This is the other side of the UM conversation — providers using CDI tools to justify longer stays and higher acuity, payers using UM tools to challenge them. Understanding Solventum's outputs helps us understand what our payer clients are reviewing against.
Iodine — Cautionary Tale + Adjacent AI-powered CDI. Jeremy Friese's warning: first-principles approach worked until $100M, then flatlined. They avoided MCG/InterQual criteria but hit a ceiling. Directly relevant as a strategic lesson for our approach. Also relevant because their outputs (better clinical documentation) are what our system reviews on the payer side.
R1 RCM — Potential Customer (long-term) Outsourced revenue cycle for hospitals. If we ever move to the provider side of concurrent review (helping hospitals justify stays to payers), R1 could be a customer or partner. Large scale — they manage RCM for major health systems.
Availity — Potential Partner / Integration Point Real-time payer-provider information network. Handles eligibility, claims, authorizations, referrals. If we're building the clinical data exchange layer between payers and providers, Availity is already doing the administrative data exchange layer. Partnership potential: clinical intelligence on top of their existing connectivity. Also a potential competitor if they add AI-powered UM to their platform.
Zelis — Tangentially Relevant Payment and claims pricing. More about network pricing and payment optimization. Not directly in UM but adjacent in the payer payment flow.
Ensemble Health Partners — Potential Customer (long-term) Outsourced RCM. Similar to R1 — if we move provider-side, they could be a customer. They handle the hospital's revenue cycle, which includes responding to payer UM decisions.
Change Healthcare (Optum/UHG) — Customer's Vendor + Cautionary Example Massive clearinghouse. 15B transactions/year. Now part of Optum/UHG. Two angles: (1) our payer customers' claims flow through Change, so understanding their data formats matters, and (2) the 2024 hack exposed how fragile legacy infrastructure is — supports the "time to rebuild" narrative. Being owned by UHG is complicated — they're both infrastructure and a payer competitor to our customers.
Waystar — Tangentially Relevant Revenue cycle tech, claims/denial management. Provider-side. Their denial management tools are the provider's response to payer UM denials — we're on the other side of that transaction.
Inovalon — Adjacent Healthcare data analytics. Claims-based quality measures, risk analytics. Could be a data source or integration point. Their analytics might inform UM criteria or population health triggers.
Practice Administration
Phreesia — Not Relevant Patient intake and check-in. Ambulatory-focused. No UM overlap.
athenahealth — Tangentially Relevant Cloud EHR/practice management for ambulatory. Their clinical data could be relevant if we need to pull provider records for UM reviews, but this is more of a "down the road, if we integrate with provider systems" thing.
Epic — Important (data source) The dominant EHR. Most large health systems run Epic. When our payer clients do UM reviews, the clinical records they're reviewing come from Epic (and Cerner). Understanding Epic's data structures, FHIR APIs, and clinical document formats is operationally important for us. Not a competitor or partner — more like the terrain we operate in.
Workforce
UKG — Not Relevant Generic workforce management (scheduling, payroll). No UM overlap.
Symplr — Not Relevant Healthcare credentialing and compliance. No direct UM overlap, though provider credentialing data (is this doctor board-certified?) could theoretically inform UM decisions.
Supply Chain
Premier — Not Relevant GPO / supply chain. Hospital purchasing. No UM overlap.
Vizient — Not Relevant GPO / supply chain. Same as Premier.
Clinical Systems
Epic — Important (see above)
Oracle Cerner — Important (data source) #2 EHR. Same relevance as Epic — clinical records our payer clients review come from Cerner systems. Need to understand their data formats.
Nextgen Healthcare — Minor Relevance Ambulatory EHR. Relevant if UM reviews involve outpatient/specialty records, but less critical than Epic/Cerner for inpatient concurrent review.
TruBridge — Minor Relevance Rural/community hospital EHR. If our payer clients cover rural populations, their clinical data comes from TruBridge systems. Niche but relevant for certain markets.
Veradigm — Tangentially Relevant Health data network. Their EHR data aggregation could be a data source for UM analytics or population health triggers. More relevant if we move into data-driven UM (predictive models for which cases to review).
Surescripts — Not Relevant (for now) E-prescribing network. Medication data flows through Surescripts. Could be relevant if UM reviews need medication history (which they sometimes do for medical necessity), but not a priority.
Summary: What Matters Most
Direct threat:
- ZeOmega — the incumbent in our exact box
Must integrate with:
- TriZetto / HealthEdge — payer core admin systems where our outputs land
- Epic / Oracle Cerner — where the clinical data we analyze comes from
- Availity — payer-provider connectivity (potential partner or competitor)
Expansion opportunities (adjacent markets):
- Cotiviti's space — payment integrity / FW&A (data we already have from UM)
- R1 / Ensemble — provider-side UM (if we go bilateral)
- Iodine / Solventum's space — CDI on the provider side (the mirror of what we do)
Strategic lessons:
- Iodine — first-principles approach capped at $100M
- Change Healthcare — legacy fragility = our opportunity narrative