New research: The State of SaaS: Build vs. Buy, October 2026.The State of SaaS, October 2026. Read the report
Glossary
The pricing, contract and switching terms that shape your software bill, in plain words.
AI-native software is software whose main workflow depends on AI models rather than treating AI as an optional feature. The label describes how the product delivers its core result, not when the company was founded or whether the product includes a chat window.
Annual contract value (ACV) is the recurring value of a software contract expressed on a yearly basis, excluding one-time fees in our buyer comparisons. Vendors use it to track sales, while buyers can use it to compare commitments with different contract lengths.
Composable software is a setup assembled from smaller components connected through defined interfaces, rather than one large suite. Each component has a focused job and is designed to be replaceable without rebuilding the entire system, although data and integration work can still make replacement difficult.
Custom software is an application built for one business and its own workflows, rather than a packaged product sold to many customers. The business decides what it does, and usually owns or controls the code, the data and where it runs.
Internal tools are applications used by a business’s own staff to run its operations rather than software offered directly to customers. They can be purchased, configured on a platform, or built specifically for tasks such as approvals, reporting, and managing records.
SaaS is not dead, but overpriced SaaS is under real pressure. AI coding tools and AI-native products let teams build or rent the slice of software they actually use, so broad suites with rising renewals are the ones losing ground. Deep, regulated or hard-to-copy tools still earn their price for most teams.
A master service agreement, or MSA, sets the general legal terms for a continuing relationship between a customer and a supplier. Individual orders or statements of work describe the particular software or services being purchased under that framework.
An MCP connector is a saved link between an AI application and an outside service's MCP server. Claude calls these connectors; once one is added and signed in, the assistant can look up data and take allowed actions in that service while answering requests.
An API is a set of endpoints that programs call with code written for that specific product. MCP is a standard layer, usually built on top of an API, that lets AI applications discover a product's actions and use them without custom code for each pairing.
The Model Context Protocol (MCP) is an open standard for connecting AI applications such as Claude or ChatGPT to outside data, tools and workflows. A software product publishes an MCP server, and any compatible AI application can use it without a custom integration for each pairing.
An open source alternative is software offered under a license that permits access to its source code and specified rights to use, modify, and redistribute it, considered instead of another product. It may be self-hosted or supplied as a managed service, and replacing a paid product with it does not remove operating or migration costs.
Outcome-based pricing charges for a defined result rather than simply providing access or measuring raw consumption. A support product might bill for an automated resolution, while a sales agreement might bill for a qualified meeting, with the contract specifying what counts.
SaaS churn measures the customers or recurring revenue a software vendor loses during a defined period. Customer churn tracks departing accounts, while revenue churn tracks lost subscription revenue, including downgrades. For buyers, evidence of departures can prompt questions about value and service, but it does not establish why customers left.
SaaS contract negotiation is the process of agreeing the price, scope, duration, and legal terms of a software subscription. It includes how the agreement renews, how charges can change, and what happens if the customer needs to reduce usage or leave.
A SaaS price increase notice is a message telling a customer that the price of a software subscription will rise. It should identify what changes, when the change takes effect, and which subscription or renewal it affects.
SaaS pricing models are the ways software vendors charge for access, consumption or results. The main models are per seat, usage based, tiered, flat rate and outcome based, and a single contract can combine several of them.
SaaS spend management is the ongoing work of finding, measuring, and controlling what a business spends on subscription software. It connects invoices and contracts with actual use so buyers can decide what to renew, resize, consolidate, or replace.
SaaS sprawl is the accumulation of more software subscriptions than a company needs or can reliably track. It appears as overlapping tools, unused access and recurring bills without clear owners, whether or not the purchases were approved.
SaaSflation is the pattern of software subscription prices rising faster than general inflation, usually through list price increases, repackaged plans and bundled AI add-ons. It is most common among established SaaS vendors whose cost structure includes large sales, support and product teams, while newer AI-native tools often run with smaller teams and can price lower.
The SaaSpocalypse is a nickname for the idea that AI will wipe out traditional software-as-a-service companies, because teams can now build or automate much of what they used to rent. The term spread in early 2026 and is often shortened to "SaaS is dead." In practice, buyers are not leaving all software; they are dropping the tools that cost more than they deliver.
Service-as-software is the idea that AI products will sell finished work instead of seats in a tool. Instead of paying for software your team operates, you pay for a result, such as a resolved support ticket or a reviewed contract. It is an investor framing for where software spending may move, not a product category you can buy off a shelf.
Shadow IT is software that people buy or use for work without the knowledge or approval of the teams responsible for IT and spending. It can begin with a card-paid subscription, a free account or a browser extension that colleagues start using together.
Shelfware is software an organization has paid for but does not use, or uses too little to justify keeping it. The term covers unused subscriptions, unassigned licenses, and purchased applications that never become part of everyday work.
Software bloat means paying for more software than a business needs, including unused features, inactive seats and overlapping tools. In engineering, the same phrase can describe an application that has become unnecessarily large or slow as features accumulate.
A software license audit compares an organization’s software deployment and use with the rights it has purchased. It checks whether the relevant users, systems, and activities are covered by the applicable license agreements.
Software migration is moving your data, users and workflows from one system to another, for example from one CRM to a new one or from a rented tool to one you own. It includes preparing records, rebuilding connections, testing the destination and helping people work in the new system.
Software procurement is the process a company uses to request, evaluate, approve, buy and renew software. It covers who asks for a tool, who checks security and budget, who negotiates the contract, and who decides at renewal whether to keep paying, switch or build.
A software renewal is the point when a subscription contract ends and either continues for another term or stops. Most SaaS contracts renew automatically unless the buyer gives notice before a set deadline, and the new term often comes with a new price.
Switching costs are the money, time and risk involved in moving from one software tool to another. They include migration work, retraining, lost data, broken integrations and overlap months paying for both tools.
Total cost of ownership is the full cost of acquiring, using, maintaining, and eventually replacing a product over a defined period. For software, it includes the subscription or development cost plus implementation, staff time, infrastructure, support, and exit costs.
A true-up is a bill a software vendor sends when actual seats or usage exceed what a contract covers. The vendor compares the agreed allowance with measured consumption and charges the difference under the contract’s counting and billing rules.
Vendor lock-in is when leaving a software vendor becomes so difficult or costly that a business stays despite preferring another option. It can come from contracts, proprietary data formats, integrations and the habits built around a tool.
Vibe coding is creating software by describing what you want to an AI system, then steering the generated code through prompts and observed results. In its stricter meaning, the person accepts code without fully understanding or reviewing it, which separates vibe coding from reviewed AI-assisted development.