Quick Answer: Larry Ellison, Oracle's co-founder and chief technology officer, argues that AI will improve software rather than make it obsolete. He says companies with deep industry data and complete suites will benefit most. Critics worry that AI agents could shrink seat-based SaaS revenue, but Ellison's view depends on whether the value sits in the software or in the data and workflows underneath it.
Software stocks have spent the past year nervous about one question: if AI can write code, draft contracts, and answer support tickets, why would anyone keep paying per user for a SaaS product? That anxiety has a name now, the SaaS apocalypse, and Ellison has decided to push back on it. As Moneycontrol reported, he says AI will make software better, not extinct. His argument is worth examining closely, because it's partly right and partly a sales pitch from the CEO of a company that sells software.
What Ellison Actually Said, and What He Didn't
The core claim is simple. Ellison believes AI raises the ceiling on what software can do, and that established vendors with large data sets and mature suites are best placed to capture that value. Oracle, in his framing, isn't selling a single app. It's building complete suites for banking, retail, hospitality, and government.
The detail that stands out is the sequencing. Oracle chose to start with healthcare, which Ellison called the most complex industry in the world. That's a deliberate bet. Healthcare has dense regulation, fragmented data, and workflows that touch billing, clinical care, and compliance at once. A vendor that can handle that mess has a stronger argument than one selling a scheduling tool.
What he didn't say matters just as much. He didn't offer a detailed breakdown of how AI will change pricing, and he didn't address what happens to per-seat revenue if AI agents do the work that used to require a licensed user. Those are the questions that drive the fear, and they're still open.
Why the Apocalypse Thesis Gets the Mechanics Wrong
Here's where most commentary goes off track. The apocalypse argument assumes the value of SaaS lives in the user interface. If anyone can generate an interface quickly with AI, the reasoning goes, the moat disappears.
That's only half the picture. In regulated, high-stakes industries, the valuable parts of software are rarely the screens. They're the data models, the integrations, the audit trails, and the compliance logic. In healthcare, for example, a system has to speak standards like HL7 FHIR for data exchange, meet the privacy and security rules under HIPAA, and fit into clinical workflows that doctors won't abandon because a chatbot looks nicer.
So the counter-intuitive finding is this: AI makes the front end cheaper, which pushes the competitive question deeper into the stack. A startup can now build a passable interface in weeks. It can't easily replicate a decade of integrations, certifications, and customer-specific data pipelines. That's why the apocalypse framing fits consumer apps better than enterprise systems of record.
This next part matters more than it looks. The moat doesn't disappear. It moves.
The Seat-Based Pricing Problem Is Real
Ellison's optimism glosses over one genuine risk. Much of SaaS revenue is priced per user. If AI agents handle tasks that used to require ten analysts logging into a system, a vendor could see fewer paid seats even while delivering more value. That's the mechanism behind the fear, and it isn't imaginary.
Consider a claims processing team. Before AI, twenty adjusters each held a license to a claims platform. After an AI agent triages and drafts most routine claims, the same work might need five adjusters and a few agents. The software did more, but the seat count fell. Revenue follows the seats, so the vendor's income could drop even as the product improved.
Vendors know this, and the response is a shift in pricing. Some are moving toward consumption-based models, where you pay per transaction, API call, or processed record. Others are experimenting with outcome-based deals. None of these are settled, and buyers should expect contract terms to be in flux for a while.
When to Use a Suite Versus Point Tools
If you're choosing software, the apocalypse debate translates into a practical question: should you buy a broad suite from an established vendor, or assemble best-of-breed point tools? Ellison's pitch favors suites. The trade-offs are real in both directions.
| Factor | Broad Suite (e.g., Oracle, Epic) | Point Tools (specialized AI-native apps) | Build In-House on Cloud Infrastructure |
|---|---|---|---|
| Integration effort | Low; modules share one data model | High; you own every connector | Very high; you own everything |
| Compliance coverage | Usually certified across the stack | Varies; you verify each vendor | You carry the full audit burden |
| Speed to adopt AI features | Moderate; depends on vendor roadmap | Fast; often ships new AI features first | Fast in theory; slow in practice |
| Pricing exposure to seat decline | High if priced per user | Varies by vendor and model | Lowest licensing risk, highest staffing cost |
| Lock-in risk | High; migration is expensive | Moderate; depends on data portability | Low to moderate, depending on architecture |
For most mid-sized organizations, the suite wins on integration and compliance. The point tool wins on speed. The in-house build only makes sense if you have engineering depth and a problem that vendors genuinely don't solve. Ellison is right that suites carry real advantages. He's less candid about lock-in, which is the cost you accept in exchange.
The Caveats Ellison's Pitch Skips
Three caveats deserve attention before you accept the "AI makes software better" story at face value.
First, the source of the claim matters. Ellison leads a company that benefits commercially from customers believing in suites and in Oracle's AI roadmap. That doesn't make him wrong, but it means his optimism should be weighed against independent evidence, such as renewal rates, customer migration data, and pricing changes over the next few quarters.
Second, healthcare is a hard test case, not a proof. Oracle's health business traces back to its 2022 acquisition of Cerner, a deal valued at roughly $28 billion. Integrating a large acquisition into a modern cloud platform is slow work. Rivals like Epic Systems hold a large share of US hospital records, and switching costs cut both ways. Clinicians and IT teams have long memories of painful rollouts.
Third, regulation can slow AI adoption as much as it accelerates it. Any AI feature that touches clinical decisions raises questions about validation, liability, and explainability. Expect buyers to ask for documentation before they sign, and expect timelines to stretch.
Most people stop here, but this is the part that changes your decision. The apocalypse debate is less about whether software survives and more about who captures the margin. Vendors with proprietary data, certified integrations, and sticky workflows are better positioned than those selling a thin layer over someone else's model.
What to Do If You Buy or Build Software
If you're evaluating software in this environment, these steps will protect you regardless of which side of the debate turns out right:
- Map where your value sits. List the workflows, data sets, and integrations your business depends on. If the most valuable piece is a proprietary data model, that's a strong position. If it's a screen, expect it to be replicated.
- Ask every vendor about pricing under AI. Request their plans for seat-based, consumption-based, and outcome-based pricing. If they can't explain how AI changes their revenue model, that's a warning sign for your long-term costs.
- Test AI features on your own data. Run a 60- to 90-day pilot on a single workflow. Measure accuracy, exception rates, and time saved, not just the demo.
- Check standards support and exit terms. Confirm support for open standards like HL7 FHIR where relevant, and negotiate data export rights before you sign. Lock-in is easier to prevent at the contract stage.
Frequently Asked Questions
What is the SaaS apocalypse?
The SaaS apocalypse is the fear that AI will make traditional software-as-a-service products obsolete or sharply reduce their revenue. The core worry is that AI can build interfaces and automate tasks cheaply, which could erode both the product moat and the per-seat pricing model that many SaaS companies depend on.
How do I know if my software vendor is at risk from AI?
Look at three things: whether the vendor owns proprietary data and deep integrations, whether its pricing depends on per-user licenses, and whether it has shipped AI features that customers actually use. Vendors with strong data and workflow ownership are generally better positioned than those selling a thin interface.
Why does AI threaten seat-based SaaS pricing?
Seat-based pricing ties revenue to the number of people logging in. If an AI agent completes work that used to need several users, companies may buy fewer seats even while getting more value. That gap between value delivered and seats sold is what puts seat-based revenue under pressure.
Is Larry Ellison right that AI will make software better?
Partly. AI does improve many software products, and vendors with large data sets and regulated-industry expertise have strong advantages. However, Ellison leads a software company with a commercial stake in that outcome, and the pricing transition is unresolved. Independent evidence, such as renewal data and pricing changes, will be more reliable than any single executive's forecast.
When should I choose a suite over specialized AI tools?
Choose a suite when integration, compliance coverage, and a unified data model matter more than adopting the newest features. Choose point tools when a specific workflow needs faster innovation and you can manage the integration work. In regulated industries like healthcare, the compliance burden often tips the balance toward established suites.
If your team is reviewing software contracts this quarter, pick the one workflow that costs you the most time and pilot an AI feature on it for 60 days. Track the actual seat count and the output before and after. That single test will tell you more about the SaaS apocalypse than any headline. Pass this to someone wrestling with renewal decisions under AI-driven pricing, and ask them to run the same test.