SaaS Statistics (2026): Market Size, Spend, Retention, and AI

You need a SaaS statistic for a board deck, investor update, market report, or article. You find one market-size estimate, then another that is hundreds of billions of dollars apart.
That does not necessarily mean one is wrong.
SaaS statistics at a glance
Category | Statistic | What it measures |
SaaS market size | $465.03B in 2026 | Precedence Research's projected global SaaS market |
Long-term SaaS projection | $1,367.68B by 2035 | Precedence Research forecast at 12.85% CAGR from 2026 to 2035 |
SaaS end-user spending | $299.1B in 2025 | Gartner's cloud application services forecast |
Worldwide IT spending | $6.31T in 2026 | Gartner's total IT spending forecast, not a SaaS market-size figure |
Median private B2B SaaS growth | 22% | SaaS Capital's 2026 survey of 1,000+ private B2B SaaS companies |
Median NRR | 102% | SaaS Capital's 2025 benchmark for companies with $25K to $50K ACV |
Average annual SaaS spend | $55.7M | Organizations in Zylo's 2026 SaaS Management Index dataset |
Median annual SaaS spend | $20.6M | Organizations in Zylo's 2026 dataset |
Average SaaS portfolio | 305 applications | Zylo's 2026 dataset |
AI-native application spend growth | 108% YoY | Zylo's observed AI-native application spending |
Enterprise generative AI spend | $37B in 2025 | Menlo Ventures' modeled enterprise generative AI market |
These statistics are not interchangeable.
A market forecast estimates the value of a category. A SaaS management dataset measures software estates observed by a particular platform. A private-company survey benchmarks a specific business population. An enterprise AI study models spending within another defined market.
Keep those distinctions attached to the numbers.

Get the Mobile Testing Playbook Used by 800+ QA Teams
Discover 50+ battle-tested strategies to catch critical bugs before production and ship 5-star apps faster.
Why SaaS market-size estimates disagree
"SaaS market size" sounds like a standardized accounting measure. It is not.
Different analysts can include different products, service categories, geographic assumptions, and revenue definitions. One forecast may define SaaS narrowly as cloud application services, while another may use a broader definition of subscription software delivered through the cloud.
That is why two credible SaaS estimates can differ significantly without directly contradicting each other.
For example, Precedence Research projects the global SaaS market at $465.03 billion in 2026.
Gartner uses a more specific public-cloud classification. Its worldwide public cloud spending forecast projected $299.071 billion in 2025 end-user spending on Cloud Application Services (SaaS).
Those numbers should not be averaged together or presented as competing measurements of exactly the same market.
A defensible citation keeps the source attached:
"Precedence Research projects the global SaaS market at $465.03 billion in 2026."
That is much stronger than:
"The SaaS market is worth $465 billion."
The first tells the reader who made the estimate, when it applies, and that it is a projection.
SaaS market size and growth
Precedence Research estimates that the global SaaS market was worth $408.21 billion in 2025 and projects it to increase to $465.03 billion in 2026.
Its longer-term forecast puts the market at approximately $1.36768 trillion by 2035, representing a 12.85% compound annual growth rate from 2026 through 2035. (Precedence Research)
These are forecast figures, not measured future revenue.
Gartner provides another useful view through cloud spending.
Its November 2024 forecast projected worldwide public-cloud end-user spending of $723.4 billion in 2025, including $299.071 billion for Cloud Application Services (SaaS). (Gartner)
The $299.1 billion number is therefore a SaaS spending forecast within Gartner's public-cloud taxonomy, not a replacement for every independent SaaS market-size estimate.
The wider technology budget is much larger.
Gartner's April 2026 forecast puts worldwide IT spending at $6.31 trillion in 2026, up 13.5% from 2025. Software spending alone is forecast at approximately $1.44 trillion. (Gartner)
Neither figure should be labeled "the SaaS market."
They include categories far beyond subscription cloud applications.
SaaS spending and software portfolios
Market size describes the category. SaaS management data gives another view: what organizations are actually buying and managing inside their software estates.
Zylo's 2026 SaaS Management Index is based on more than 40 million SaaS licenses, more than $75 billion in discovered and categorized SaaS and cloud spending, and nine years of spend, license, and usage data.
Within that dataset, organizations spend:
$55.7 million on SaaS annually on average
$20.6 million in median annual SaaS spend
305 applications on average in their SaaS portfolio
240 applications in the median portfolio
The difference between the average and median matters.
A few very large organizations can pull the average upward, which is why $55.7 million should not be treated as a standard SaaS budget for a typical company.
The same applies to application count.
A portfolio of 305 applications is a benchmark within Zylo's dataset. It does not mean every business runs hundreds of SaaS products.
How an organization discovers, identifies, and classifies applications can materially affect its reported portfolio size.
Portfolio growth has flattened while spending continues to rise
One of the more useful findings in Zylo's 2026 index is that the average portfolio remained at 305 applications, with total app counts declining slightly by 0.07%.
At the same time, average SaaS spending increased 8% year over year.
That suggests spending pressure in Zylo's dataset is increasingly coming from how software is priced, packaged, expanded, and consumed rather than simply from companies adding more applications.
It is a useful distinction for procurement teams.
Counting applications alone cannot tell you whether your SaaS budget is under control.
SaaS retention and growth benchmarks
Retention and growth statistics require particularly careful cohort labeling.
SaaS Capital's 2026 Private B2B SaaS Company Growth Rate Benchmarks are based on its annual survey of more than 1,000 private B2B SaaS companies.
The survey reports a 22% median growth rate across respondents.
Funding model matters:
Bootstrapped companies: 20% median growth
Equity-backed companies: 25% median growth
SaaS Capital also found a strong relationship between retention and growth. Moving from the 90% to 100% NRR range into the 100% to 110% range was associated with a five-percentage-point improvement in growth.
That does not mean increasing NRR by itself guarantees five additional points of growth. It is a relationship observed in the survey population.
What is a good net revenue retention rate?
There is no single NRR target that fits every SaaS company.
SaaS Capital's 2025 retention benchmark found 102% median NRR among private B2B SaaS companies with annual contract values between $25,000 and $50,000.
Within that ACV band:
Median NRR was 102%
Top-quartile NRR was 111%
Bottom-quartile NRR was 97%
Net revenue retention measures how recurring revenue from an existing customer cohort changes after expansion, contraction, and churn.
An NRR above 100% means expansion from retained customers more than offsets recurring revenue lost from contraction and churn.
But a benchmark only becomes useful when the comparison group resembles your business.
A low-ACV self-serve SaaS product and an enterprise SaaS company selling six-figure contracts should not automatically use the same retention target.
If your SaaS product includes a consumer or mobile-app surface, mobile app retention benchmarks and churn definitions provide a better companion metric than forcing app retention into an enterprise NRR comparison.
How AI is changing SaaS budgets
AI is affecting SaaS economics in two ways.
Organizations are buying more AI-native applications, while existing SaaS vendors are also introducing AI add-ons, consumption pricing, and usage-based tiers.
Zylo's 2026 index reports that spending on AI-native applications increased 108% year over year.
Among large enterprises in its dataset, AI-native application spending increased 393%. Usage across the broader Artificial Intelligence application category grew 181%. (Zylo)
The pricing impact is showing up as well.
Zylo reports that:
78% of IT leaders experienced unexpected charges tied to AI features or consumption-based pricing
61% said they cut projects because of unplanned SaaS cost increases
Those percentages should remain attributed to Zylo because the survey population and definitions determine how broadly they can be applied.
Enterprise generative AI spending reached an estimated $37 billion
Menlo Ventures' 2025 State of Generative AI in the Enterprise estimates that companies spent $37 billion on generative AI in 2025, up from $11.5 billion in 2024.
Menlo's analysis combines a survey of roughly 500 U.S. enterprise decision-makers with a bottom-up market model.
Of that $37 billion:
$19 billion went to AI applications
$18 billion went to AI infrastructure
Menlo also found that 76% of enterprise AI use cases were purchased rather than built internally, compared with 53% in its 2024 data.
These numbers should not be treated as a census of every enterprise. They are Menlo's modeled view of the enterprise generative-AI market.
But they reinforce a broader trend also visible in Zylo's dataset: AI spending is becoming increasingly intertwined with software spending.
For software teams, that creates another question beyond procurement: how are AI-assisted products and releases being verified?
Quash's AI testing statistics and adoption data examines that adjacent problem without treating testing adoption figures as SaaS market-size data.
What aggregate SaaS statistics leave out
Aggregate SaaS statistics are useful for understanding market scale and operating benchmarks.
They are much less useful for telling you what your own product should cost to build, how much your company should spend on software, or what retention level your business should achieve.
A few important things are usually missing.
Company type
Enterprise SaaS, SMB software, vertical SaaS, developer tools, and consumer subscriptions can have very different sales cycles, contract values, margins, and retention patterns.
Pricing model
Per-seat subscriptions, usage-based pricing, transaction fees, AI-token consumption, and outcome-based pricing do not behave the same way.
Product delivery costs
Market-size forecasts rarely tell you what teams spend on product development, QA, infrastructure, security, customer success, and incident recovery.
Product surface
A SaaS company with a native mobile application has testing, distribution, device, and retention considerations that a browser-only application may not share.
If your SaaS product has a mobile surface, mobile app development cost data can help frame that narrower build-cost question. It should not be treated as a universal SaaS development-cost benchmark.
How to cite a SaaS statistic
Before reusing a SaaS statistic, run a simple six-point check.
Name the source. Write "SaaS Capital's 2026 survey found," not "research shows."
Keep the year. SaaS spending, AI pricing, and growth benchmarks change quickly.
Describe the population. Include the ACV band, ARR threshold, survey population, or observed dataset when available.
Define the metric. Market size, end-user spending, NRR, portfolio size, and growth rate measure different things.
Keep the source's scope. Do not turn Gartner's $6.31 trillion IT forecast into a SaaS market-size statistic.
Use the closest available source. Prefer Gartner for a Gartner forecast, Zylo for the SaaS Management Index, and SaaS Capital for its survey rather than a roundup repeating those figures.
A strong statistical statement has a simple structure:
source + year + population + metric + value
For example:
"SaaS Capital's 2026 survey of more than 1,000 private B2B SaaS companies found a median growth rate of 22%."
That statement is easier to verify and harder to misinterpret than:
"SaaS companies grow 22% per year."
Methodology and sources
This report prioritizes the source closest to each statistic.
Market estimates, analyst spending forecasts, SaaS management datasets, and private-company surveys are kept separate because they do not measure a common population.
Sources used include:
SaaS Capital: 2026 Private B2B SaaS Company Growth Rate Benchmarks
Menlo Ventures: 2025 State of Generative AI in the Enterprise
The central limitation is comparability.
A research firm's market projection, Gartner's cloud-spending taxonomy, Zylo's observed SaaS estates, SaaS Capital's private-company survey, and Menlo's enterprise AI market model should not be merged into a single average.
Where a figure could not be verified closely enough to its original source, it was excluded.
Conclusion
The best SaaS statistic is not necessarily the biggest one. It is the number whose definition still fits the decision you are making.
Precedence Research projects the global SaaS market at $465.03 billion in 2026. Gartner forecast $299.1 billion in SaaS end-user spending for 2025 within its public-cloud taxonomy. SaaS Capital's latest private B2B benchmark reports 22% median growth, while Zylo's 2026 dataset shows average SaaS portfolios holding steady at 305 applications even as spending rises.
AI is adding another layer. Zylo reports 108% year-over-year growth in AI-native application spending, while Menlo Ventures estimates $37 billion in enterprise generative-AI spending in 2025.
None of those numbers answers every SaaS question.
For market size, retain the forecast and its scope. For spending, retain the dataset. For retention and growth, retain the company cohort. For AI, distinguish observed SaaS spending from modeled generative-AI market estimates.
That context is what turns a persuasive-looking SaaS statistic into evidence someone else can actually evaluate.


