AI may make it cheaper to build software for small, overlooked audiences—but that does not mean SaaS is disappearing or that open-source projects will automatically thrive. The more useful question is which software functions are becoming easy to reproduce, which still depend on trusted data and complex operations, and who will pay to maintain the alternatives.
What does “SaaS apocalypse” mean?
“SaaS apocalypse” is a market narrative about the possibility that AI will unsettle software-as-a-service businesses. It is not evidence that subscription software as a whole is already vanishing. BBVA Global Markets Strategy’s March 10, 2026 analysis describes the pressure as selective: some functions may be easier to automate or recreate than others.
BBVA identifies four concerns behind the narrative: AI platform commoditisation, increased competition from start-ups, bespoke enterprise applications, and AI-driven seat compression. These are drivers of investor and market concern, not a count of companies already displaced.
Why cheaper software creation could help open source
The opportunity begins with the cost of making software. If AI reduces the time and expense needed to build and adapt applications, projects aimed at small or specialized groups may become more practical. A niche tool that could not previously justify a dedicated development effort might be worth attempting when a smaller team can build a useful first version.
#1 Best Overall
That is the thesis advanced in the original article, not a measured forecast of how many new projects will emerge. Lower creation costs could broaden the range of software people try to make; they do not establish that those projects will find users, stay secure, or survive long enough to become dependable products.
Open source could benefit because people can inspect, adapt, and share code rather than wait for a single vendor to add a specialized feature. But openness is not itself a business model. Someone still has to review changes, fix vulnerabilities, handle upgrades, provide support, and pay for hosting or other operating costs. The available market analysis does not establish how maintainers will fund that work or whether open-source projects will capture revenue from the shift.
Which SaaS products appear more exposed?
BBVA’s analysis suggests assessing software by how reproducible its core function is, whether it holds authoritative records or accumulated data, and how difficult or risky it is for a customer to switch. On that basis, it sees simpler point tools as more vulnerable to automation or in-house replication.
| Software type | BBVA’s assessment | Why the distinction matters |
|---|---|---|
| Simple analytics, basic reporting, service desks, and single-feature marketing tools | More exposed to automation and in-house replication | If the core job is narrow and switching friction is limited, customers may have more alternatives, including custom tools. |
| Systems of record, ERP, core databases, data security, and stateful infrastructure | Comparatively defensible | Authoritative data, accumulated business logic, and switching friction can make replacement harder and errors more consequential. |
This is BBVA’s market judgment, not a guarantee that any particular product category is safe or doomed. A simple tool can still be valuable if it is reliable and deeply embedded in a workflow; a complex platform can still face pressure if customers find a credible alternative.
Quick wins for a faster PC:
Repair Windows errors before they cause bigger problemsFix Now →Scan for outdated or missing drivers - takes under a minuteDriver Scan →Rank #3
- Used Book in Good Condition
Why systems of record may be harder to replace
Generating a new interface or a basic workflow is different from taking responsibility for a company’s authoritative data. Systems that store core records or enforce accumulated business rules are difficult to replace because users depend on their accuracy, history, permissions, integrations, and predictable behavior—not just on a list of features.
Switching also carries costs beyond migration. A flawed change can disrupt operations, expose data, or create errors that are hard to reverse. That gives established products a form of defensibility that does not depend solely on how quickly they can add AI features. It also creates an opening for open-source alternatives only when they can meet the same needs for trust, continuity, and support.
What the AI spending figures do—and do not—show
Rothschild & Co’s February 2026 Growth Equity Update reported that Microsoft, Meta, Alphabet, and Amazon planned about $650 billion in AI capital expenditure in 2026, compared with about $380 billion in 2025. Those are reported plans, not confirmation of audited spending. The figures indicate the scale of investment in AI infrastructure; they do not prove that SaaS will collapse or that open-source projects will receive a windfall.
Rothschild & Co also describes investor concerns around commoditisation, pressure on seat growth, and pricing risk. Those concerns help explain why the “apocalypse” narrative attracts attention, but market anxiety is not the same thing as demonstrated displacement.
Best Value
What an open-source opportunity would have to solve
Cheaper development addresses only one part of making a software product viable. A serious alternative must also work for the people who use it and the people responsible for operating it.
- Maintenance: Someone must review contributions, fix defects, and keep the software compatible as other systems change.
- Security and trust: Public code can be inspected, but openness alone does not ensure that anyone has inspected it or that vulnerabilities will be fixed promptly.
- Data and reliability: Users need dependable backups, access controls, upgrades, and a way to recover when something goes wrong.
- Support and distribution: A useful project still has to reach its intended users, explain how to adopt it, and help them when it fails.
- Sustainable funding: Hosting, support, and development have ongoing costs. The cited market analyses do not establish which funding models will cover them for new open-source projects.
These requirements help distinguish a promising prototype from a viable alternative to a paid service. If the software handles important records or business processes, users may reasonably value accountable support and predictable operations as much as the license or feature set.
How to judge the claim without treating it as a certainty
For customers, developers, and investors, the useful question is not whether “SaaS” lives or dies as a single category. Examine the specific product and ask:
- Can AI reproduce its main function, or does the product depend on unique data and accumulated business logic?
- How difficult is it to switch, and what could go wrong during migration?
- Would a bespoke tool solve a real unmet need, or would it create more maintenance work than value?
- Can an open-source project provide the security, support, and continuity users require?
- Can an incumbent turn AI into a customer benefit that justifies its price, rather than merely adding an AI label?
The strongest version of the opportunity is therefore narrower than the headline might suggest: less expensive software creation may make more niche tools feasible, while exposing products whose value rests mainly on a function competitors can readily reproduce. Whether open source turns that possibility into durable products—and sustainable maintainer income—remains unresolved.
Recommended Free Tools
Quick Recap
Product prices and availability are accurate as of the date/time indicated and are subject to change. Any price and availability information displayed on Amazon at the time of purchase will apply.
