The Vendor-Owned Enterprise Is Ending
AI is breaking the SaaS bargain of rented logic, lock-in, and vendor-owned workflow.
AI is not killing software, but it is destroying the premium on vendor-owned workflow logic while making data, compute, and internal control layers more strategic.
Big SaaS vendors still have revenue inertia, but that is not the same thing as future pricing power or durable strategic control.
CEOs should stop buying software as a bundle of state, logic, and interface, and start asking who owns each layer and how easily it can be reclaimed.
There is a lazy story in the market right now:
AI writes code.
So SaaS is in trouble.
So enterprise software is about to get flattened.
That story is too crude.
But the comforting response has been too crude as well.
The comforting response says serious enterprise software is safe because it owns “coordination,” “governance,” and “operational depth.” That sounds reassuring. It is also how incumbents always describe the thing that is about to be abstracted.
The real issue is not whether software matters.
It is whether vendor-owned logic should still sit at the centre of the enterprise.
The old bargain was simple: rent the vendor’s logic, accept the lock-in, and call it operational maturity. AI is breaking that bargain.
That is the strategic shift.
Not “no software.”
Not “every SaaS company dies.”
But something more destabilising than either camp wants to admit:
the era of the vendor-owned enterprise is ending.
The market has felt that before it has fully explained it. Reuters reported on April 9 that the S&P 500 Software & Services index was down 25.5% year to date. At the same time, the BVP Nasdaq Emerging Cloud Index showed roughly $1.5 trillion in aggregate market cap, 18.6% average revenue growth, and a much lower 5.1x average revenue multiple. That is not software demand disappearing. It is the market charging much less for software whose right to own the workflow is suddenly in doubt.
The spending backdrop says the same thing in a different language. Gartner expects worldwide software spending to reach about $1.43 trillion in 2026, up 14.7%, while data-centre systems spending is expected to grow 31.7% to about $653.4 billion. The point is not that software vanishes. The point is that value is shifting toward the layers that make intelligence and data liquid, while application logic gets repriced.
Every cycle turns a moat into a migration
Every major technology cycle does the same thing.
It takes a former strategic asset and turns it into a rigid liability.
Server rooms were once a moat. Then cloud turned them into stranded complexity.
That is why the “SaaS as the new server room” analogy lands. It forces the right question:
What if fixed workflows, fixed schemas, vendor-controlled roadmaps, trapped data, and painful exits are not signs of software strength, but signs of a delivery model nearing abstraction?
That is not a fringe question. It is the central question.
Because some of what enterprise software has long called “depth” is just dependency with a better account team.
Yesterday’s moat often survives for a while as contractual inertia. Then it becomes a migration plan.
That is also why “revenue is still up” is a weak defense.
Salesforce reported fiscal 2026 revenue of $41.5 billion, up 10%, with current RPO up 16%. ServiceNow reported Q4 2025 subscription revenue up 21%, with cRPO up 25%. Atlassian reported Q2 FY26 revenue up 23%, with RPO up 44%. Those are real numbers. They are also the wrong comfort. They tell you these platforms still have inertia. They do not tell you the old bargain remains strategically attractive. Long contracts, renewal friction, and embedded process debt can keep revenue healthy long after the logic of the model starts decaying.
If you are a CEO, vendor revenue is not the question.
The question is whether you are paying for value creation or financing your own captivity.
The big mistake: treating coordination as mystical
This is where a lot of pro-SaaS analysis still falls apart.
It treats “coordination” as if it is some sacred enterprise art form that AI cannot touch.
That is too romantic.
A large share of coordination inside enterprises is just logic applied to state:
If the threshold is crossed, escalate.
If legal approves, route to finance.
If the contract is redlined, trigger review.
If the ticket has these attributes, hand it to this queue.
If this vendor fails this check, block the workflow.
If this deal exceeds the limit, require a second sign-off.
That is not mystical.
That is logic.
And once intelligence gets cheap enough to generate, adapt, monitor, and rewrite logic quickly, the strategic question becomes brutal:
Why should that logic belong to the vendor?
The traditional model said: let the vendor own the workflow, the data model, the policy surface, and the release cadence. In return, you get convenience, uptime, and someone else carrying the maintenance burden.
That was a reasonable trade when internal software creation was slow and expensive.
It is a much weaker trade when AI compresses the cost of drafting, extending, and reconfiguring business logic.
The evidence points in that direction. In the UK government’s AI coding assistant trial, developers reported average time savings of 56 minutes per working day. In the 2025 Stack Overflow Developer Survey, 84% of respondents were using or planning to use AI tools in development, and 51% of professional developers used them daily. Brynjolfsson, Li, and Raymond found that generative AI increased customer-support productivity by about 14% on average, with larger gains for less-experienced workers. Dell’Acqua, Ethan Mollick and colleagues found meaningful gains on realistic knowledge-work tasks, while also describing a “jagged technological frontier” where capabilities remain uneven. The point is not that every company has already standardised on a fully autonomous agentic fleet. The point is that the cost curve on logic creation and maintenance is moving sharply against vendor-owned workflow.
Data liquidity is now strategic
This is the point the old SaaS playbook handles worst.
In an AI-heavy enterprise, data becomes more valuable when it is portable, model-readable, recomposable, and easy to route across systems.
But classic SaaS economics were built on the opposite assumption.
Put your data in my system.
Adopt my schema.
Use my workflow.
Access your own operating history through my interface and my API limits.
Then pay me more every year because leaving is painful.
That model worked when software convenience outweighed software captivity.
Now the captivity is more visible.
If your most important operational data lives inside a vendor-defined logic box, then the vendor is no longer just selling software. They are taxing your future optionality.
In the AI era, trapped data is not a moat. It is a strategic liability with a renewal date.
This is why “ease of exit” matters so much.
Not because easy-exit vendors are abundant in public markets. They are not.
But because CEOs should stop rewarding the opposite.
A vendor whose economics depend on your inability to leave is not aligned with your long-term strategic position. That used to be tolerated. It should not be now.
And no, the answer is not to go on a fantasy hunt for perfect portability. The answer is to build leverage yourself: own the data layer where you can, decouple logic from interface where you can, and stop buying software bundles that assume the vendor should permanently own your operating state.
The public markets are repricing entitlement
The software selloff is not a clean referendum on product quality. It is a messy repricing of several things at once.
Part of it is rates. The 10-year U.S. Treasury yield was 4.29% on April 9, and the Fed’s target range remained 3.5% to 3.75% after its March meeting. Long-duration software equities are structurally vulnerable in that environment.
Part of it is capital rotation. The AI stack is pulling spend toward data centres, compute, model access, and data infrastructure faster than toward classic application layers. Gartner’s category split captures that clearly.
But part of it is a much deeper reassessment:
If AI can increasingly generate and adapt business logic, should customers keep paying premium multiples for software that owns the logic on their behalf?
That is the question markets are starting, clumsily, to ask. And if that is the question, then “revenue is still growing” is not enough of an answer. What is being repriced is not just software. It is vendor entitlement: the entitlement to own the workflow, define the schema, pace the roadmap, and charge more because exit is painful.
The new strategic unit: state, logic, view
This is the architectural pivot that matters.
CEOs should stop thinking of the software stack as a collection of applications.
They should think of it as three layers:
state - where the business truth lives
logic - how decisions, routing, permissions, and workflows operate
view - the interface through which people inspect or act on the system
The old SaaS model bundled all three under vendor control.
That is what is breaking.
The AI-era opportunity is to separate them.
Own the state.
Own or at least govern the logic.
Treat views as replaceable.
This does not mean every company should rebuild ERP from scratch. That would be cargo-cult modernity.
It means the architecture of power is changing.
The more your vendor owns your state and logic, the more they own your tempo.
The more you can decouple state and logic from the UI layer, the more strategic room you create for yourself.
That is the real reason “AI-native” is such a weak buying criterion. A vendor can be AI-native and still be building a better cage.
The future belongs to enterprises that treat software less like a destination and more like a thin layer over owned state and governed logic.
The board question is not “buy or build”
It is tempting to turn this into a classic buy-versus-build fight.
That is too simple.
The real board-level question is:
What must the enterprise own to preserve strategic freedom as intelligence gets cheaper?
That usually points to a different answer than either SaaS marketing or engineering bravado wants.
You probably do not need to own every interface.
But you do need far more control over:
your core data exhaust
the logic that routes work and approvals
your ability to swap interfaces and model providers
your ability to extract, inspect, and recompose operational state
the policy layer that governs automation at scale
That is what logic sovereignty looks like in practice.
Not a macho internal-tools fantasy.
A deliberate reduction in vendor control over your operating model.
And that matters because one of SaaS’s oldest arguments is getting weaker: the ownership scare tactic.
For twenty years, SaaS vendors sold “maintenance insurance.” They charged venture-grade and then public-market-grade multiples because hiring dozens of engineers to maintain internal business software was genuinely painful.
In 2026, that insurance premium looks much less defensible.
The same AI wave that pressures SaaS pricing also reduces the cost of a meaningful share of internal software upkeep. The UK trial, the Stack Overflow survey, the NBER field evidence, and the Dell’Acqua et al. study all point in the same direction: AI improves productivity on real software and knowledge tasks, often most for the less-experienced workers who used to make internal capability hard to scale. That does not erase maintenance cost. But it does erode one of SaaS’s oldest structural advantages. If 50 engineers increasingly look like 5 engineers with agentic IDEs and strong internal tooling, the old maintenance-insurance premium starts to look less like prudence and more like an overpriced relic.
What’s coming up next
Below, I get even more operational:
which software categories CEOs should target first for budget cannibalisation
how to spot fake portability in a sales process
what to ask vendors about state ownership, API access, logic escrow, and exit rights
where AI infrastructure should be funded from inside the existing software budget
the simple scorecard I’d use before every major renewal
