Product1 distinct publisher3 min readUpdated
UBS asked 12 Fortune 500 CIOs and CTOs why software budgets softened. Price-increase backlash, AI crowding out and mix shift all ranked above macro, and nobody blamed seasonality.
The Product Desk · Product desk

Compiled by The Product DeskSomething wrong?How this is made
UBS put the question of why software spending has weakened to 12 of its Fortune 500 CIO and CTO contacts, and published the initial unvarnished feedback [3]. The answers matter because the sector has already de-rated materially over the last few months [1] on a cause that was not obvious [2], and because the ranked list the CIOs produced describes a deliberate cleanup rather than a soft quarter.
There was no single explanation, according to UBS, but a combination of issues [4]. First and most widely acknowledged: a more concerted rationalization of software spend, especially at the SaaS layer, in reaction to what respondents called "excessive" price increases and following an over-investment phase [5]. Second: AI crowding out other software spend, both because dollars have to be freed up and because CIOs are hesitating or de-prioritizing while they work out what AI does to a given category [6]. Third: a mix shift inside budgets, with some SaaS projects de-prioritized and dollars moving to cloud infrastructure, cyber-security and open source [7]. Macro uncertainty, rates and weak consumer spend, showed up fourth, further down the list than many might expect [8]. Not one of the CIOs cited unusual 4Q-1Q seasonality [9], which is to say zero of the 12 [2]. Three of the four causes on the list are structural [1].
The uncomfortable part for vendors is the mechanism. UBS says the repeated message was that customers have over-bought, suffering from enterprise license agreement fatigue, and that software firms over-played their hand on price [10]. Buyers are now actively rationalizing in a still-tight budget backdrop [11]. The comparison UBS draws is exact: companies are doing to their SaaS budget what they spent the last 18 months optimizing away in AWS and Azure [12]. That earlier cleanup took four to five quarters, and with it largely finished at many large enterprises, attention has moved to other budget lines [17].
Application software is the target because it is where the fat was. Enterprises historically overprovisioned there relative to infrastructure, data and security [13]. It is also where price increases were sharpest, in part because SaaS firms facing weaker customer headcount growth, and therefore weaker seat expansion, tried to offset it through pricing and bundling [14]. And it is where the AI stories are still evolving or unclear [15], which makes deferral cheap. Timing may reflect the start of a new year, or a reaction to aggressive sales pushes at 4Q renewals [16]. UBS also raises the possibility that some customers are only now moving AI work from small proofs of concept into production, so the crowding-out effect is just starting [18].
The distinguishing tests UBS is applying to individual names are the same ones an operator should apply to their own vendor list: how much shelfware exists, which suppliers pressed hardest on pricing and bundling, and which are premium-priced versus low enough per seat to be rationalized last rather than first [19]. Adobe is offered as the counter-example, not immune but possibly bucking the trend in its May quarter given less over-provisioning in creative software, no real competition, and a credible AI story in Firefly [20].
What to watch: whether renewal negotiations in the coming quarters produce seat reductions rather than deferrals, since seat expansion is already weak [14]; whether the money leaving SaaS keeps landing in infrastructure, security and open source [7]; and whether AI moving into production widens the squeeze on non-AI lines [18]. If macro were the driver, seasonality would have been mentioned by someone [9].
Follow any of these and your For You feed starts watching them — no settings page required.
Ranked by verification strength, evidence, and original report placement.
The software sector has de-rated materially over the last few months.
While it seems clear that software spending has weakened, the root cause is far less obvious.
UBS laid out possible explanations and offered initial unvarnished feedback from 12 of its Fortune 500 CIO/CTO contacts with whom it regularly swaps thoughts.
According to the CIO/CTO feedback, there is not one singular cause of the software sector weakness of the last few months but rather a combination of multiple issues.
The most widely-acknowledged explanation was software spend rationalization: a more concerted rationalization of software spend, especially at the SaaS layer, in reaction to 'excessive' price increases and following an over-investment phase.
The second explanation was AI crowding out: AI is beginning to crowd out other software spend, both in terms of the need to free up dollars and hesitation or de-prioritization as CIOs/CTOs consider AI impacts.
Evidence-backed comparisons of source perspectives and observed adoption signals. Read the methodology
Which Builder, Operator, and Investor concerns the observed source mix emphasized—not a truth score.
Evidence, demonstrated adoption, hype gap, incentives, and confidence are assessed independently, each on its own current evidence. How these are measured.
Single sell-side note on a small qualitative panel
All claims trace to one UBS publication reporting unvarnished feedback from 12 self-selected Fortune 500 CIO/CTO contacts. The reporting of what those contacts said is internally consistent and explicit about ranking, including the clean negative finding on seasonality, which lifts it above anecdote. But there is no sample methodology, no response distribution, no spend, renewal or shelfware data, and the causal interpretation is repeatedly hedged ('perhaps', 'tough to say'), so the structural-versus-cyclical conclusion is not independently corroborated anywhere in the cluster.
No adoption signal in supplied material
The cluster contains no release, deployment, benchmark, pricing-change or usage-disclosure datapoint. References to customers moving AI from proofs of concept into production and to enterprises finishing cloud optimization are unquantified assertions inside a hedged hypothesis list, with no named deployments, counts, contract values or dates, so adoption cannot be scored without inventing facts.
Framing runs ahead of a 12-contact qualitative check
The confident ordering of causes — three structural drivers above the cycle, nobody blaming seasonality — is presented as a diagnosis of a sector de-rating, but rests on an undisclosed-methodology panel of 12 contacts with no spend data, and UBS itself admits it cannot say why the shift landed in 1Q. The note is genuinely hedged in its analytical passages, which keeps the overstatement modest rather than severe; the gap comes from the strength of the ranking and the leap to stock-level screening and an Adobe call on the same thin base.
Sell-side research with direct positioning interest
The publisher is an investment bank writing for software investors, and the note ends in an equity screen plus a favorable read on a named covered company (Adobe, with Firefly cited as a credible AI story). The panel is also a proprietary contact network UBS markets as differentiated access. No disclosure of coverage, banking relationships or positioning appears in the supplied text, so the commercial interest in the conclusions is material and unmitigated within the cluster.
Clear on what was said, weak on whether it is true
Confidence is moderate: the source text is unambiguous, so what UBS reports and how it hedges can be assessed with high reliability, and the perspective read is straightforward for a single-publisher cluster. Confidence in the underlying market diagnosis is much lower, because there is one publisher, no corroboration, no quantitative data and an undisclosed panel methodology, and no adoption dimension could be scored at all.
invest
H100 rentals are back to $2.35 an hour, and your AI cost model is stale1 distinct publisher
build
The middle tier for Postgres: own kernel, no public IP, and you own the backups1 distinct publisher
product
Adobe ships Firefly's audio tools with a licensing claim attached, not just better output2 distinct publishers
build
Force the tool call, then hand Lightsail a long-lived key1 distinct publisher
Distinct publishers with included, body-backed reporting in this cluster.
1 article · August 17, 2026