
By Daniel Lambert
Artificial Intelligence is fundamentally changing the economics of enterprise software. As AI agents become increasingly capable of executing business processes, automating workflows, analyzing information, and supporting decisions, organizations face a strategic question: Should they continue paying recurring subscriptions for every SaaS application, or can some of these business capabilities be delivered more efficiently through AI? Enterprise Architecture provides the framework for answering this question systematically, balancing business value, cost optimization, flexibility, security, and long-term architectural sustainability.
For the past two decades, Software-as-a-Service (SaaS) has transformed enterprise technology. Organizations have increasingly adopted cloud-based applications to support customer relationship management, finance, procurement, human resources, marketing, project management, and numerous other business functions.
SaaS has delivered significant benefits, including faster deployment, reduced infrastructure responsibilities, continuous software updates, and access to sophisticated business functionality without substantial upfront development investments. However, this convenience has come at a cost.
Many organizations now operate hundreds, sometimes thousands, of applications. Their portfolios often contain overlapping functionalities, underutilized licenses, fragmented data, complex integrations, and increasing vendor dependencies. Subscription costs continue to accumulate, even when the business value delivered by individual applications remains difficult to quantify.
Artificial Intelligence introduces a new alternative. AI agents can increasingly perform activities previously requiring dedicated software applications, specialized interfaces, or extensive human intervention. AI-assisted software engineering is also reducing some of the historical costs and complexity associated with developing customized solutions. This development challenges a long-standing assumption: Organizations must purchase or subscribe to a software application whenever they need a new business capability. In her LinkedIn article, “AI Is Changing the Economics of Enterprise Software – and the Business Case May No Longer Add Up,” enterprise architecture strategist Gwen Murphy raises an important question: Why should organizations continue renting capabilities they can increasingly build, own, extend, and economically optimize themselves? [i]
However, replacing SaaS applications with AI is not simply a software development or cost-reduction exercise. It requires understanding how business capabilities are delivered, how applications interact, where enterprise data resides, which operational controls must be preserved, and whether alternative architectures generate sustainable business value. The objective should not be to replace SaaS with AI indiscriminately. It should be to determine which business capabilities can be delivered more effectively, economically, and securely through SaaS, AI, or a combination of both. This is where Enterprise Architecture (EA) becomes indispensable.
1. The Rise of AI Agents: Is the Traditional SaaS Model Under Threat?
Traditional SaaS applications are built around predefined functionality, standardized business processes, configurable workflows, and user interfaces. Organizations subscribe to these applications and adapt their business operations to the capabilities and constraints of the selected platforms. AI agents introduce a fundamentally different approach. Instead of requiring users to navigate multiple application interfaces, AI agents can interpret business objectives, retrieve information, interact with enterprise systems, execute workflows, and coordinate activities across applications.
-
Customer Relationship Management: AI agents can qualify leads, prepare personalized communications, update customer records, and recommend sales activities.
-
Human Resources: AI agents can coordinate employee onboarding, answer policy questions, process routine requests, and support employee administration.
-
Procurement: AI agents can research suppliers, compare quotations, prepare purchase requisitions, and monitor procurement activities.
-
Finance: AI agents can assist with invoice processing, expense classification, reconciliations, financial analysis, and management reporting.
-
Project Management: AI agents can track deliverables, identify risks, prepare status reports, and coordinate follow-up activities.
-
Enterprise Architecture: AI agents can support application-to-capability mapping, application rationalization, architecture documentation, impact analysis, and capability-based roadmap development.
Many of these activities currently require specialized SaaS functionality. The emergence of AI raises the possibility that organizations could deliver selected capabilities through AI agents integrated with enterprise data and existing systems rather than purchasing additional software products.
From application-centric to capability-centric technology
Historically, enterprise technology investments have often followed an application-centric approach. When a business function requires new functionality, the organization evaluates available software products, selects a vendor, implements the application, integrates it with existing systems, and pays recurring licensing fees. AI enables an alternative approach. Instead of beginning with software products, organizations can begin with the business capability itself. For example, rather than asking which procurement application should be purchased, an organization could first determine which procurement activities require automation, which decisions can be supported by AI, and which transactions must remain within existing enterprise systems.
An AI agent might research suppliers, analyze quotations, and recommend purchasing decisions while an ERP platform continues to manage purchase orders, financial commitments, and transaction records. The result is not necessarily the elimination of the ERP application. It is a more intelligent distribution of responsibilities between AI agents and traditional enterprise systems. AI may replace the functionality of certain SaaS applications without replacing the systems of record, data structures, or transactional controls on which the enterprise depends.
The SaaS business model is evolving
AI is also challenging the economics of per-user SaaS licensing. Traditionally, software spending increases as organizations add employees, licenses, modules, and applications. However, AI agents can perform substantial volumes of work without requiring a conventional human user interface. [ii] This creates an opportunity to reconsider whether software pricing should be based primarily on user access, transactions, consumption, or measurable business outcomes. It also creates competitive pressure on SaaS vendors to incorporate AI capabilities, revise pricing models, and demonstrate greater business value.
The likely outcome is not the disappearance of SaaS. Rather, the enterprise software market may evolve toward a combination of traditional applications, AI-native solutions, intelligent agents, and consumption-based services. For enterprise architects, application portfolio strategies must evolve to accommodate new ways of delivering business capabilities. [iii]
2. SaaS vs. AI: Comparing Costs, Flexibility, Capabilities, and Business Value
One of the strongest arguments for reconsidering SaaS investments is economic. Organizations often continue renewing SaaS subscriptions because the applications are already implemented, integrated, and embedded in daily operations. However, historical investments should not automatically justify future expenditures. As AI changes the cost of developing, integrating, and operating software functionality, organizations should revisit the traditional build-versus-buy decision.
From renting software to owning capabilities
Gwen Murphy’s article highlights a potentially significant shift: organizations may increasingly be able to own the data models, business logic, knowledge, and workflows that support their operations rather than depending entirely on proprietary SaaS platforms.
This is particularly relevant when the organization’s competitive advantage resides in its unique business processes, institutional knowledge, and enterprise data. A SaaS vendor may provide a sophisticated application interface, but the underlying business knowledge and relationships often belong to the enterprise.
AI-powered solutions built around enterprise-owned data, open standards, reusable services, and knowledge graphs may provide greater architectural flexibility and control. However, ownership does not automatically mean lower costs. Organizations that develop their own AI-enabled solutions also assume responsibility for engineering, maintenance, cybersecurity, reliability, monitoring, governance, and ongoing technological evolution.
The hidden cost of SaaS plus AI
A particularly important concern is the tendency to add AI functionality to existing SaaS environments without eliminating corresponding costs. An organization might continue paying its SaaS subscriptions while introducing AI agents, orchestration platforms, model inference services, data pipelines, and additional integration infrastructure.
Instead of reducing technology expenditures, AI becomes another layer of recurring costs. Every new agent can generate additional inference costs, API transactions, data retrieval operations, monitoring requirements, and maintenance responsibilities. Organizations must evaluate both the initial implementation cost and the ongoing operational economics. Figure 1 above compares traditional SaaS and AI-powered alternatives across financial, functional, operational, and governance criteria.
Neither approach is universally superior. A mature SaaS application supporting complex financial transactions may remain more economical and reliable than developing an AI-native replacement. Conversely, an expensive specialized SaaS application supporting simple administrative workflows may be an attractive candidate for replacement. An illustrative financial comparison Figure 2 illustrates the potential annual cost difference between the two architecture approaches discussed below. Gwen Murphy presents an illustrative Enterprise Architecture scenario involving approximately 1,000 applications. Her analysis compares an annual run rate approaching $915,000 for a traditional SaaS architecture supplemented with agentic capabilities against approximately $570,000 for an alternative architecture using an enterprise-owned graph, an open-standards data model, and an AI platform. [iv]

These numbers are illustrative assumptions, not vendor quotations or validated savings projections. They do not establish migration costs or total financial return. Nevertheless, they demonstrate why traditional SaaS economics deserve renewed scrutiny.
Moving from AI activity to AI economics
Organizations should establish a business case for every significant AI agent and workflow. At a minimum, the financial evaluation should address:
-
Current cost of delivering the business capability.
-
Implementation and ongoing costs of the AI alternative.
-
Expected cost per completed business transaction or workflow.
-
Financial impact of increasing AI usage.
-
Costs of maintaining necessary systems of record.
-
SaaS licenses, infrastructure, and services that can actually be eliminated.
-
Expected productivity improvements and other measurable benefits.
The distinction between avoided costs and realized savings is essential. If an AI agent automates a workflow but the organization continues paying for the same SaaS application, the financial benefits may be limited. A successful AI transformation should identify which existing technology costs can be reduced or eliminated without sacrificing business value.
3. Which SaaS Applications Can AI Replace, Enhance, or Leave Untouched?
Not all SaaS applications are equally suitable for AI replacement. Some primarily support relatively simple workflows, document processing, reporting, and information management. Others provide complex transactional functionality, regulatory controls, specialized algorithms, and mission-critical systems of record. Enterprise architects must distinguish between these categories.
Three categories of SaaS applications
-
Category 1: Potential candidates for AI replacement. Applications supporting repetitive administrative tasks, basic reporting, information retrieval, document classification, workflow coordination, and simple analytical activities may offer attractive replacement opportunities. Examples include certain standalone reporting tools, document-processing applications, basic workflow utilities, and specialized administrative software.
-
Category 2: Applications that should be enhanced with AI. CRM platforms, procurement systems, HR applications, service management solutions, and project management platforms can benefit from AI agents while retaining structured records, business rules, and operational controls. AI augmentation may generate greater value than replacement.
-
Category 3: Applications that should generally be retained. Core ERP systems, banking transaction platforms, financial ledgers, regulated recordkeeping systems, and other mission-critical applications are less likely to be immediate candidates for complete replacement. They provide transactional integrity, established controls, specialized functionality, auditability, and operational reliability.
As illustrated in Figure 3, a single SaaS application may support multiple business capabilities, each presenting different opportunities for AI replacement or enhancement. Enterprise architects should therefore assess each capability individually to determine whether AI can deliver greater business value, reduce costs, or improve operational efficiency, rather than evaluating the entire application as a single replacement candidate. The fundamental mistake would be to evaluate replacement opportunities solely at the application level. A single SaaS application may support multiple business capabilities

The organization may be able to replace certain functions while retaining the core application for essential transactions. This capability-based approach enables more precise investments and reduces unnecessary disruption.
Five architectural decisions
-
Retain: Continue using the application when it delivers appropriate business value and remains economically justified.
-
Enhance: Introduce AI agents to improve efficiency, automation, decision-making, or user experience.
-
Consolidate: Eliminate duplicated applications or functionality through shared platforms and reusable AI services.
-
Replace: Substitute selected SaaS functionality or complete applications with AI alternatives when justified by business value and risk.
-
Retire: Eliminate applications or functionality that no longer support meaningful business requirements.
These decisions should be based on measurable business outcomes, not technological enthusiasm. The most attractive opportunities will often combine SaaS rationalization, AI automation, and business process improvement.
4. The Enterprise Architecture Perspective: Assessing Opportunities, Risks, and Readiness
Replacing SaaS with AI is not merely a technology substitution. It can fundamentally change how business capabilities are delivered, how enterprise information is managed, how processes operate, and how organizations control their technology investments. EA provides the structure required to evaluate these changes across the enterprise.
4.1. Business strategy and expected outcomes
Every SaaS replacement initiative should support a defined business objective, such as reducing operating costs, improving customer experience, increasing productivity, accelerating time to market, or reducing vendor dependency. Without measurable outcomes, AI initiatives risk becoming additional technology expenditures.
4.2. Business capabilities and value streams
Enterprise architects should map SaaS applications and AI agents to the business capabilities they enable. They should examine the value streams and processes through which these capabilities contribute to outcomes. This identifies duplication, capability gaps, automation opportunities, and dependencies, and prevents optimizing individual tasks at the expense of end-to-end processes.
4.3. Application and integration architecture
The assessment must determine which SaaS functions can be replaced, which systems must remain, and which integrations are required. AI agents should interact with enterprise systems through governed APIs, services, and integration mechanisms wherever practical. Organizations should avoid hundreds of independently developed agents introducing new dependencies and complexity.
4.4. Data architecture, ownership, and knowledge graphs
Enterprise data, business relationships, metadata, business rules, and institutional knowledge are often more strategically valuable than the applications used to manage them. Organizations should preserve control over these assets independently of individual software vendors. An enterprise knowledge graph can represent relationships among capabilities, applications, processes, data, organizational units, and technology components. AI agents can use this contextual information for consistent analysis and decision support. Knowledge graphs are not mandatory for every AI implementation; their value depends on relationship complexity, contextual reasoning, and reuse. The architectural objective is to maintain enterprise knowledge and data as reusable strategic assets rather than leaving them unnecessarily locked inside individual applications.
4.5. AI governance, security, and operational resilience
AI-powered solutions introduce risks including inaccurate outputs, unauthorized actions, prompt injection, data leakage, uncontrolled agent behavior, and unpredictable operating costs. Enterprise architects must help establish controls for agent identity, authorization, data access, human approval, auditability, testing, monitoring, and incident management. Governance should reflect the level of autonomy granted to each agent. An agent generating management reports requires different controls from one authorized to execute financial transactions or modify supplier information. Human oversight should remain proportionate to business criticality and consequences.
4.6. Financial architecture and technology economics
Traditional application portfolio management emphasizes licensing costs, utilization, technical health, and functional fit. AI requires a broader perspective: the cost of individual agents, workflows, inference, data movement, integration, and operational support. Costs should be connected to the business capabilities and outcomes they enable and assessed at production scale.
Avoiding a new generation of AI sprawl
Organizations spent years rationalizing complex application portfolios. They now risk accumulating AI agents, models, prompts, retrieval pipelines, orchestration services, and integration components. Without standards, reusable services, financial transparency, and governance, this environment could become as expensive and difficult to manage as the SaaS portfolio it was meant to simplify. An enterprise architecture repository should increasingly document AI agents, their supported capabilities, data dependencies, operating costs, business owners, and governance requirements. AI adoption should contribute to enterprise simplification rather than introduce another layer of complexity.
5. From SaaS to AI: Building a Capability-Based Transformation Roadmap
Organizations should not begin by selecting AI platforms or developing large numbers of agents. They should begin by understanding existing capabilities, application portfolios, financial commitments, and strategic priorities. A practical transformation roadmap can be organized into six steps.
5.1. Establish the current-state application and capability landscape
Inventory SaaS applications, business owners, supported capabilities, functional scope, integrations, annual costs, contractual commitments, and business criticality. Map applications to capabilities and value streams. Establish a financial baseline.
5.2. Identify and prioritize AI opportunities
Assess capabilities and activities against AI feasibility, business value, complexity, financial benefits, and risk. Identify functions to replace, enhance, consolidate, or retire. Prioritize meaningful benefits and manageable risks.
5.3. Design the target AI-enabled enterprise architecture
Define how AI agents, SaaS applications, data platforms, knowledge graphs where appropriate, APIs, and integration services work together. Establish principles for interoperability, vendor independence, security, data ownership, and agent governance.
5.4. Validate technical feasibility and financial value
Conduct controlled proofs of concept. Compare alternatives on accuracy, processing time, cost per transaction, user satisfaction, reliability, and risk. Include implementation, ongoing consumption, migration, and achievable SaaS retirement savings.
5.5. Develop the transition roadmap
Phase initiatives by business priorities, technical dependencies, readiness, and benefits. Coordinate contract renewals, migration, integrations, retirement, training, and operational transition. Set financial and architectural decision gates.
5.6. Scale, govern, and continuously optimize
Expand successful AI solutions incrementally. Monitor benefits, performance, security, compliance, and adoption. Reassess SaaS necessity and AI economics. Update the EA repository with evolving relationships. As illustrated in Figure 4, Enterprise Architecture is evolving from an application-centric approach, where business processes and workflows depend heavily on individual SaaS applications, toward an AI-enabled, capability-centric approach. In this emerging model, AI agents, reusable APIs, and business services work together to deliver business capabilities while leveraging existing SaaS platforms, systems of record, and enterprise data. This evolution enables greater flexibility, reduces application dependencies, and creates opportunities to optimize technology investments.
Historically, organizations structured technology around software products. Each application provides functions, workflows, interfaces, and data structures. AI creates opportunities to separate business capability delivery from the applications that traditionally support it.

In the emerging architecture, business capabilities become the primary reference point for technology decisions. AI agents coordinate activities across systems while traditional applications continue providing essential transactional services. This can improve flexibility, reuse, and independence, but it must remain economically justified.
Replacing a mature SaaS application with a custom AI solution that is more expensive, less reliable, or harder to maintain is not architectural progress. EA must distinguish genuine transformation opportunities from unnecessary technological substitution.
Conclusion: The Future Is Not SaaS vs. AI — It Is Business Capabilities Delivered More Intelligently
Artificial Intelligence is challenging the traditional economics of enterprise software. For decades, organizations responded to new business requirements by purchasing applications, expanding subscriptions, and integrating increasingly complex portfolios. AI introduces a different possibility. Organizations can reconsider whether certain business capabilities need dedicated SaaS applications or whether AI agents, reusable services, and existing systems can provide better alternatives. The opportunity extends beyond licensing savings to process improvement, agility, less duplication, data control, and innovation.
However, AI introduces new financial, architectural, operational, and governance challenges. Without disciplined investment management, organizations could replace SaaS sprawl with AI sprawl while increasing overall expenditures. The objective is not to deploy more AI or replace more SaaS applications. It is to deliver business capabilities at the lowest sustainable cost while maintaining required business value, flexibility, security, and reliability. Enterprise Architecture connects business strategy, capabilities, value streams, applications, data, technology, and financial decisions. It helps determine where AI should replace, enhance, consolidate, or coexist with SaaS and ensures that investments fit a coherent target architecture.
Ultimately, the organizations that benefit most from AI will not necessarily deploy the most agents or retire the most applications. They will make the best architectural and economic decisions. If we were designing our enterprise architecture from scratch today, knowing what AI can do, would we still purchase all the SaaS applications we currently use? For many organizations, the answer may be no. And that is precisely why it is time to reassess the enterprise application portfolio.
___________________________
[i] Gwen Murphy, “AI Is Changing the Economics of Enterprise Software – and the Business Case May No Longer Add Up,” LinkedIn, https://www.linkedin.com/posts/gwencarasmurphy_cio-cfo-enterprisearchitecture-share-7508250268581617664-UNiL/
[ii] Deloitte, “The Changing Economics of Enterprise Software,” July 2026, https://www.deloitte.com/ca/en/services/consulting/perspectives/changing-economics.html
[iii] Engineering.com, “AI Is Rewriting the Enterprise Software Business Model,” July 2026, https://www.engineering.com/ai-is-rewriting-the-enterprise-software-business-model/
[iv] Gwen Murphy, “Get Off Your SaaS – Comparing Two Enterprise Architectures,” LinkedIn, https://www.linkedin.com/posts/gwencarasmurphy_as-a-follow-up-to-yesterdays-get-off-your-activity-7508508137457438720-83gU
