AI Is Eating SaaS

The interface layer will disappear. The infrastructure layer will compound.

Over the past few weeks, two things happened that, taken together, tell us exactly where enterprise software is headed.

First, OpenAI’s COO publicly acknowledged that enterprise AI has not yet penetrated business processes at scale. Despite explosive growth in usage, AI remains largely an individual productivity tool inside complex organizations.

Second, Anthropic demonstrated 16 autonomous Claude agents working in parallel for two weeks to build a 100,000-line C compiler capable of compiling the Linux kernel.

Those two facts sit in tension.

AI capability is accelerating rapidly. Enterprise penetration remains limited.

That gap is the story.

And it explains why the “SaaS is dead” narrative is deeply misunderstood.

If you care about where enterprise software is headed in the AI era, subscribe below. I write about AI, SaaS, and the evolution of enterprise infrastructure.

Capability Is Not the Bottleneck

Let’s start with the Anthropic experiment.

Sixteen agents. Nearly 2,000 sessions. Two billion tokens. Around $20,000 in compute. No internet access. The result was a clean-room Rust-based C compiler that can compile Linux 6.9 on multiple architectures and pass major compiler test suites.

That is not autocomplete. That is autonomous, multi-agent software production.

If anyone still believes AI is not capable of meaningful autonomy, that argument is over.

But here is the more interesting detail.

Most of the engineering effort did not go into improving the model. It went into designing the environment around the model.

The team built deterministic test harnesses. Continuous integration pipelines. Task locking systems to prevent agents from colliding. Structured logging so errors were machine readable. Oracle comparisons against GCC. Strict version control discipline. Feedback loops that allowed agents to orient themselves without human oversight.

The intelligence scaled. The environment made it usable. Autonomous agents did not eliminate infrastructure. They required it.

That pattern should sound familiar.

AI Is Reasoning. SaaS Is Execution.

To understand what is happening in enterprise software, we need to separate two layers that are converging.

The AI layer is probabilistic. It interprets intent. It reasons. It generates language. It proposes actions.

The SaaS layer is deterministic. It executes transactions. It enforces permissions. It maintains audit trails. It governs workflows exactly as designed.

Enterprise software requires both.

An AI agent without enterprise context is like a powerful smartphone without a network. It may be intelligent. It may be beautifully designed. But it cannot transact. It cannot close payroll. It cannot finalize procurement. It cannot approve a promotion. It cannot book revenue.

Execution lives somewhere.

And execution is where SaaS sits.

Even OpenAI Acknowledges the Gap

Despite the remarkable capabilities demonstrated by frontier models, OpenAI’s COO recently stated that AI has not yet penetrated enterprise business processes at scale.

Why? Because enterprises are not clean engineering environments. They are messy.

Multiple teams. Layered approvals. Regulatory requirements. Deep historical context. Interdependent systems. Embedded workflows that differ by geography and industry.

In other words, complexity. That complexity lives inside SaaS systems today.

AI works extraordinarily well at the individual level. Ask it to draft a memo, write code, summarize a document, or analyze a spreadsheet and it performs impressively.

But integrating into business processes is different. It requires understanding state, permissions, escalation paths, compliance boundaries, and transaction integrity.

The bottleneck is not intelligence. It’s workflow.

Not All SaaS Companies Are the Same

Part of the market’s confusion comes from treating all SaaS vendors as interchangeable.

They are not.

There are systems of record that own canonical enterprise data. Workday, for example, is not simply an HR interface. It encodes compensation models, payroll logic, compliance rules across jurisdictions, approval hierarchies, and years of employee history. It is deeply embedded in how a company operates.

There are systems of engagement whose primary value is interface layered on top of shared data. These are more exposed. If your moat is a better dashboard, AI compresses you quickly.

Then there are workflow owners. Platforms that encode mission-critical process logic, manage state transitions, and orchestrate interdependent tasks across teams.

Those platforms are not simply applications. They are execution engines.

As agents become more autonomous, execution engines become infrastructure.

The Real Counterargument

There is a serious counterargument that deserves respect.

It goes like this. AI agents will abstract away SaaS entirely. Users will interact only with orchestration layers. Systems of record will become dumb databases underneath intelligent interfaces. Value will move to the agent layer.

There is some truth here. Interface layers will compress. Orchestration platforms will capture value. But systems of record are not dumb databases.

Take a practical example. Imagine an AI agent that drafts job descriptions, screens candidates, recommends compensation bands, and prepares promotion packets.

Where does that data get written?

Where are compensation limits enforced?

Where are payroll calculations executed?

Where are permissions checked?

Where is the audit trail stored?

The hard part is not generating a new HR interface. The hard part is migrating and governing a decade of structured employee data across multiple countries while preserving compliance and transactional integrity.

AI can generate software rapidly. It cannot easily migrate enterprise history or assume execution liability without trusted infrastructure.

Execution liability lives somewhere. Enterprises will anchor it to systems they trust.

The Inversion: More Autonomy Requires More Governance

The Anthropic experiment revealed something else that is critical.

As agents became more autonomous, the need for guardrails increased. Merge conflicts multiplied. Bugs reintroduced previously fixed issues. Parallel agents overwrote each other’s work. Monolithic tasks like compiling the Linux kernel created coordination bottlenecks.

The ceiling was not intelligence. It was orchestration and structured constraint.

The more autonomous systems become, the more enterprises will demand deterministic execution, auditability, rollback capability, and permission enforcement.

Autonomy amplifies risk. Risk increases the value of governance. Governance is infrastructure.

This is the inversion that most “SaaS is dead” narratives miss.

The Shift From Interface to Infrastructure

What is truly happening is not the destruction of SaaS. It is the compression of the interface layer and the elevation of infrastructure.

Single-user data entry screens will decline. Time spent in dashboards will decline. Measuring success by time in app will look outdated.

But the underlying execution layer becomes more important.

SaaS companies that survive will expose deterministic workflows as atomic, permission-aware actions that agents can call safely. They will treat their platforms as headless infrastructure rather than click-based cockpits. They will combine structured data with contextual memory while preserving governance and compliance.

This is architectural evolution. And not every SaaS company will make it.

If your moat is UX alone, you are exposed. If your moat is structured truth, embedded workflow, compliance, and switching cost, you have leverage.

Monetizing the Move to Infrastructure

If SaaS becomes infrastructure for AI agents, monetization must evolve.

Per-seat pricing was built for a world where humans were the primary actors. In an agent-driven world, activity decouples from headcount. Ten agents may perform the work previously done by fifty employees. Seat-based economics strain under that model.

Even OpenAI has signaled that it intends to measure enterprise success based on business outcomes rather than seat licenses. The shift is already underway.

Three principles should guide monetization.

First, price the workflow, not the seat. If your platform governs payroll, procurement, revenue operations, or financial close, price based on transactions executed or value governed. Seats measure access. Workflows measure impact.

Second, monetize trusted execution. Enterprises will pay for safe autonomy. Guardrails, audit trails, simulation modes, and compliance enforcement are not optional features. They are premium infrastructure.

Third, align pricing with outcomes where possible. If AI layered on your platform increases productivity or reduces cost, structure expansion around measurable value creation rather than interface usage.

When the interface shrinks, pricing cannot anchor to the interface.

Infrastructure monetizes durability and trust.

A Simple Diagnostic for SaaS Leaders

The question for SaaS leaders is no longer whether to add AI features. It is where you sit in the stack.

Five questions clarify that quickly.

1. If someone cloned your interface tomorrow, what remains defensible? Canonical data ownership, deep workflow logic, embedded compliance, switching costs, or primarily user experience?

2. In an agent-driven workflow, are you the system that executes final transactions and enforces permissions, or an intermediary screen?

3. Can an agent safely call your core workflows as atomic, permission-aware actions?

4. Is your AI architecture converged with structured data and consistent permissioning, or bolted on as a wrapper?

5. If half your human users disappeared because agents automated their work, would your revenue collapse?

Execution engines survive. Intermediaries get abstracted.

The Forward View

AI capability is accelerating rapidly. That is undeniable. But enterprise adoption lags because integration into business processes is complex.

The bottleneck is not intelligence. It is workflow, governance, and execution.

That bottleneck is where SaaS lives.

Interface-centric SaaS companies will see valuation compression. Systems of record and workflow owners will remain central to enterprise architecture. Agent-native vertical SaaS companies that design with deterministic execution from day one will create new categories.

Value is not disappearing. It is relocating.

The interface layer will commoditize. The execution and governance layers will compound.

The future is not AI replacing SaaS. The future is AI sitting on top of SaaS.

The companies that recognize this and re-architect accordingly will not be casualties of the shift.

They will power it.