Market Frameworks
How the capital markets and healthcare ecosystem are thinking about AI, services, and the payer-provider dynamic. These are the intellectual currents investors are swimming in. Understanding them helps us speak the language of the conversation that's already happening.
Last updated: 2026-02-18 Sources: 9 investor calls, market research, podcast/media, direct observation
Active Frameworks
1. "No Successful AI Companies, Just Consulting Companies"
The idea: In healthcare, pure AI product companies will struggle. The winners will be services-first organizations that use AI as a capability, not a product. The value accrues to the people who understand the domain and can deploy, not to the software itself.
Who's saying this:
- Manatt Healthcare partner (via Seae Ventures / Karlos) — "There are no successful AI companies in healthcare, just consulting companies."
- Seae Ventures is using this as a diligence filter — they're looking for companies that match this thesis
- Thomas has been saying a version of this for months ("SaaS apocalypse")
Where DaisyAI sits: Dead center. This is our thesis. FDE is the operationalization of this idea. We are the consulting company that uses AI, not the AI company that does consulting. The distinction matters.
Implications:
- When talking to investors who hold this framework, lead with the services model and the domain depth. The AI is the enabler, not the product.
- Investors who DON'T hold this framework (who still believe in SaaS multiples for healthcare) are probably not the right investors for us.
- This framework is gaining momentum but is not yet consensus. We're early to this thesis.
Counter-argument: "If AI companies don't work, why would I invest in one?" The answer is: we're not an AI company. We're a healthcare operations company that's AI-native. The distinction is the FDE model — we deploy, we embed, we stay. That's a services business with technology leverage, not a technology business with services attached.
2. Silicon Valley vs. Healthcare (The Gap)
The idea: There's a fundamental disconnect between how Silicon Valley builds products and how healthcare actually works. SV thinks in terms of products, platforms, scale, network effects. Healthcare thinks in terms of relationships, trust, regulation, institutional inertia. Companies that try to apply SV playbooks to healthcare fail. Companies that bridge the gap succeed.
Who's saying this:
- Karlos (Seae) — talked about this gap explicitly. Define's founding thesis (Lynn left Kleiner because she saw this gap).
- Chuka (Define) — fund was "custom built" for companies that combine "Silicon Valley first principles" with "strong connectivity to the rest of the ecosystem."
- Deborah (NextGen) — pushed on differentiation because she sees too many SV-style AI companies that don't understand healthcare.
- Multiple investors have validated that "both founders build" AND "understand healthcare" is the rare combination.
Where DaisyAI sits: We are the bridge. Healthcare PE background + engineering capability + AI-native thinking. We don't come from SV and try to learn healthcare. We come from healthcare and learned to build.
Implications:
- This framework is nearly universal among healthcare-focused investors. Every call has validated it in some form.
- The risk is that generalist investors (who live in SV frameworks) may not get this. They'll ask "what's the moat?" and "how does this scale?" in SV terms. We need both languages.
- Our Wharton pedigree is actually a signal here — it says "we understand business and healthcare, and we also build." It bridges the gap credibly.
3. The SaaS Apocalypse / Services Revaluation
The idea: SaaS multiples are compressing. The market is recognizing that many SaaS companies don't have real moats — they're features, not platforms. Meanwhile, services businesses (traditionally dismissed as unscalable) are getting re-evaluated because (a) AI makes services more leveraged, and (b) deep domain services create switching costs that SaaS doesn't.
Who's saying this:
- Thomas — has been articulating this thesis directly in investor calls
- Sam (Tau) — engaged deeply on the revenue model, validated that SaaS + implementation + maintenance makes sense
- Chuka (Define) — "payers are far less likely to buy a wrapper or enterprise SaaS solution"
- Chris (Sorensen) — didn't challenge the services model at all, engaged on the problem space instead
- Broader market: public SaaS compression, Palantir's services-heavy model outperforming
Where DaisyAI sits: We're the embodiment of this thesis. We're not apologizing for being services-heavy. We're arguing that services + AI is the higher-value model in healthcare, and that the margin trajectory improves as the encoding compounds.
Implications:
- Investors who hold this framework will get us immediately. They're not worried about "are you just consulting?"
- Investors who are still anchored to SaaS multiples will struggle with our model. They'll want to see the "platform" and the "70% gross margins." For them, the Tau revenue breakdown (showing the maintenance/licensing as majority revenue) is the bridge.
- This framework is gaining but not yet dominant. We're making a bet that it becomes consensus within 2-3 years.
4. Provider AI Ahead of Payer AI
The idea: Provider organizations (hospitals, health systems) are adopting AI faster than payer organizations (health plans, insurers). This creates an asymmetry — providers are using AI tools for documentation, coding, appeals, and other workflows, while payers are still largely manual. The result: payers are getting overwhelmed by AI-generated provider output.
Who's saying this:
- Thomas — framed this directly in the Define and Seae calls (providers using bots to slam payers with appeals)
- Karlos (Seae) — Blues Plan LP confirmed payers "getting hammered" by provider AI tools + GLP-1s
- Battery — ambient scribes causing upcoding, making UM harder for payers
- Tau — Cigna contact says payer tech is "absolute trash," everything manual
- Chuka (Define) — resonated when Thomas described the appeals dynamic
Where DaisyAI sits: We're the payer response to this asymmetry. But — and this is where the clearing house vision matters — we're not trying to help payers win the arms race against providers. We're trying to resolve the arms race by getting the clinical answer right the first time, so neither side needs to fight.
Implications:
- This is the most compelling "why now" for the payer wedge. Every investor has accepted it.
- The risk: if we position too hard as "helping payers respond to provider AI," we're on one side of the arms race, not at the center.
- The clearing house vision reframes this: we're not the payer's defense. We're the shared intelligence layer that makes the arms race unnecessary.
5. FDE as an Emerging Category
The idea: Forward Deployed Engineering — sending technical talent into enterprises to build within their systems — is becoming recognized as a distinct go-to-market and delivery model. Palantir pioneered it. A new generation of companies is applying it to specific verticals.
Who's saying this:
- Seae Ventures — Manatt quote is guiding their diligence. They're specifically looking for FDE-model companies.
- Define — Chuka: "a lot of talk within our ecosystem right now around how do you take this forward deployed approach."
- Battery — identified Optera as "doing exactly what we're talking about" (FDE for payer risk/governance).
- Thomas — has been evangelizing this framework since early 2025.
Where DaisyAI sits: We're one of the earliest healthcare-specific FDE companies. The category is forming around us.
Implications:
- Being early to a category is powerful if the category takes off. The risk is that the category doesn't materialize, or it gets defined by someone else (e.g., Palantir just announces a healthcare vertical).
- Every investor who references FDE or "forward deployed" unprompted is a signal that the category is solidifying.
- We should be contributing to the category definition — content, conference talks, the way we describe ourselves. First mover in category definition has lasting advantage.
6. Platform vs. Point Solution
The idea: Healthcare enterprises (both payers and providers) are experiencing vendor fatigue. They have too many point solutions. They want platforms that touch multiple use cases and reduce the integration burden. The next generation of winners will be platform companies, not point solutions.
Who's saying this:
- Chuka (Define) — "more and more we are seeing what I'll call platform players in the market... both providers and plans are going to want folks that touch a number of different use cases."
- Olivia (Battery) — raised point solution / consolidation risk unprompted
- Deborah (NextGen) — pushed on deep vs. broad, which is another version of this question
Where DaisyAI sits: The FDE model is inherently a platform play — we go in and touch multiple workflows, not just one. But we start with a wedge (UM). The question is how to communicate "we're a platform" without sounding like vaporware.
Implications:
- The clearing house vision is the strongest platform story we have. "We're the shared clinical intelligence layer" is a platform, not a point solution.
- But we have to be careful — claiming platform too early when we have one client on one workflow feels premature. Better framing: "UM is the wedge. The deployment model is the platform. We expand within clients across their AI initiative roadmap."
7. Payer-Provider Adversarial Dynamic as a Structural Problem
The idea: The adversarial relationship between payers and providers is not just a business dynamic — it's a structural problem that creates enormous waste. Most healthcare AI companies pick a side and optimize for that side, which makes the adversarial dynamic worse. The real opportunity is at the interface.
Who's saying this:
- This is OUR framework. We haven't heard investors articulate it yet.
- Closest: Thomas's framing of the appeals dynamic (providers using AI to overwhelm payers) touches it
- The clearing house vision doc articulates this fully
Where DaisyAI sits: This is our deepest thesis. We're the company that refuses to optimize for either side and builds at the center.
Implications:
- This framework is NOT yet in the investor conversation. It's ahead of where the market is.
- We need to introduce it carefully — too abstract and it sounds like philosophy, too concrete and it sounds like we're just doing UM.
- The right entry point might be: "The appeals explosion you're hearing about? That's a symptom of the adversarial dynamic. We're not building the payer's defense. We're building the layer that makes the fight unnecessary."
- This is potentially the most powerful framework because no one else is articulating it. If it resonates, we own it.
Framework Interactions
These frameworks don't exist in isolation. They interact:
- "No successful AI companies" + SaaS apocalypse → Together they point to services-first, AI-enabled companies as the winners. DaisyAI fits perfectly.
- Silicon Valley gap + Provider AI ahead → SV-style AI companies are building for providers (easier to sell, more SV-compatible). Payer side is underserved because it requires domain depth that SV doesn't have. This is our opening.
- FDE as category + Platform vs. point solution → FDE naturally touches multiple workflows (platform) but delivers through embedded deployment (not SaaS). The deployment model IS the platform.
- Adversarial dynamic + Clearing house → This is the framework interaction that's uniquely ours. Nobody else is connecting the payer-provider structural problem to the AI deployment question. That's the vision doc.
How to Use This
In investor conversations: Listen for which frameworks an investor holds. Match your framing to their worldview in the first 5 minutes. Then expand.
| If they say... | They hold framework... | Lead with... |
|---|---|---|
| "We like the FDE model" | #5 (FDE category) | Deep on deployment methodology, Palantir comp, how we encode |
| "Payers won't buy SaaS" | #3 (SaaS apocalypse) + #2 (SV gap) | Services-first, domain depth, revenue model (Tau version) |
| "What's the platform?" | #6 (Platform vs. point) | UM wedge → expansion across AI initiatives → clearing house |
| "How's this different from Cohere?" | #4 (Provider AI ahead) | Concurrent ≠ prior auth, FDE vs. SaaS, payer response to provider AI |
| "Can you actually sell to payers?" | #2 (SV gap) | Premera proof point, payer-first rationale, relationship depth |
| "What's defensible here?" | Generalist skepticism | Three moat layers + accumulated translation + clearing house position |
For content and positioning: Write and speak in the frameworks that are gaining momentum (#1, #3, #5). Introduce the framework that's uniquely ours (#7) through content and conference conversations to shape the narrative before investors encounter it.
Open Questions
- Which market map did Define find us on? Who's producing healthcare AI market maps right now?
- Are there other companies being categorized as "healthcare FDE"? Battery mentioned Optera. Who else?
- How fast is the "no successful AI companies, just consulting companies" thesis spreading? Is it becoming consensus or staying niche?
- When does the clearing house / adversarial dynamic framework enter the investor conversation? Do we need to introduce it, or will it emerge from market dynamics?