The Structural Distinction
SaaS versus Work as Services.
The distinction is not about technology. It is about where the work lands. In SaaS, the work lands on the human. In Work as Services, the work lands on the system. That is an architectural difference — and it changes everything for care.
The Old Paradigm
Software as a Service
Delivers a tool. Requires the caregiver to learn it, operate it, input into it, and extract from it. The software completes itself. The human does the work.
- Seat-based licensing — the seat occupies the caregiver
- Administrative burden transferred to the human
- Screen-forward: the interface demands attention
- Compliance-first architecture
- The technology is the deliverable — you do the rest
The New Architecture
Work as Services
Delivers the completed outcome. The caregiver receives the result, not the tool. Administration is performed autonomously. The human delivers the care — the system delivers everything else.
- Outcome-based — you pay for what gets done, not for access
- Administrative burden absorbed by the system
- Screen-dark: the interface is invisible because it is unnecessary
- Care-first architecture
- The completed work is the deliverable — the system does the rest
External Validation
Four sources. One convergence.
Independently and from different vantage points, four institutions arrived at the same structural conclusion. The industry is moving toward outcomes. The care sector needs it most urgently.
Satya Nadella
"The business logic is all going to these agents. The SaaS application as we know it may well collapse."
BG2 Podcast · December 2024
IDC
By 2028, pure seat-based pricing models will be largely obsolete. 70% of software vendors will have refactored their offerings around outcome delivery.
IDC FutureScape · December 2025
Bain & Company
Routine rules-based digital tasks will move from "human plus app" to "AI agent plus API" — shifting the unit of work from the human to the system.
Bain Technology Report · 2025
General Catalyst
Customers care about outcomes, not products. The next generation of enterprise software is measured on what it accomplishes, not what it provides access to.
General Catalyst · 2025
Introduced in This Episode
Autonomous Caring.
Work as Services expressed specifically in the care context. Not AI as a new screen. Not AI as a new interface. AI as the absence of both — performing administrative work in the background, invisibly, so that the caregiver's full presence is returned to the person in front of them.
Dark
The screen is dark because the system is working. No input required. No interface to navigate. The work is done.
Principle: Screen-Dark Architecture
Background
Administration performed without caregiver interaction. Documentation, compliance, coordination — completed in the background, in real time.
Principle: Autonomous Operation
Outcome
The deliverable is not software access. The deliverable is the completed administrative task. The outcome is what is paid for.
Principle: Outcome-Based Delivery
Present
The caregiver's attention is returned to the patient. Full presence, not divided. The technology is invisible because it is doing what it was always supposed to do.
Principle: Restored Human Presence
Episode Summary
The full case.
The pivotal fourth episode of Defending Care delivers the architectural verdict and solution that three episodes of indictment were building toward. Opening with Satya Nadella's December 2024 BG2 podcast statement — that business applications in the agent era are "essentially CRUD databases with business logic" that will collapse — the episode positions Work as Services as the paradigm Anand Chaturvedi arrived at years earlier for care.
The precise structural distinction is drawn: SaaS delivers a tool and requires the human to do the work; Work as Services delivers the completed outcome and the human delivers the care. External validation arrives from IDC (by 2028, pure seat-based pricing will be obsolete; 70% of software vendors will refactor around outcomes), Bain (routine rules-based digital tasks moving from "human plus app" to "AI agent plus API"), and General Catalyst (customers care about outcomes, not products).
Autonomous Caring is introduced as Work as Services expressed in the care context — technology operating in the background, performing administrative work without caregiver interaction, the interface invisible and the screen dark. This is not an AI argument. It is an architecture argument. And the architecture is available now.
"Technology that works. So that caregivers can."
Highlight
The sharpest two minutes.
The moment the distinction between SaaS and Work as Services is drawn with surgical precision.