Twenty-six technology leaders explain their Snowflake spend plans, and the split is sharp: legacy migrations and AI workloads keep pulling money onto the platform, while cost pressure and single-stack consolidation push a smaller group out.
ETR gathered qualitative commentary from 26 technology leaders on the drivers behind their planned Snowflake spend changes over the next six months, and the accounts describe two different products. For the 18 organizations increasing spend, Snowflake is the destination for on-prem warehouses, aging SQL estates, and a growing roster of AI workloads. For the eight cutting back, it is one platform too many in a stack being collapsed to one.
Business Growth Is the Default Driver: Fourteen of the 18 increasers carry a Business Growth theme, and most describe the added spend as net new budget rather than dollars taken from another vendor.
Legacy Modernization Feeds the Pipeline: Seven increasers are retiring on-prem warehouses or earlier-generation platforms in Snowflake's favor, and several describe it as the standard for their data modernization programs.
AI Is Now Part of the Spend Rationale: Five increaser accounts tie the increase directly to AI, from agentic use cases to AI layers on customer-facing data products.
Consolidation and Cost Drive the Exits: Vendor Consolidation appears in five of the eight decreaser accounts and Cost Pressure in four. The exits are not concentrated in one competitor; the budget scatters across rival platforms, native cloud services, open source tools, and AI initiatives.
The most notable feature of the increase side is how rarely Snowflake's gain is another vendor's loss. Asked whether the change comes at another vendor's expense, increaser after increaser said no. A Fortune 500 VP in Financials/Insurance put it in five words: "This is net new for us." Others described spend that was forecast into the budget cycle in advance, budgets that scale with company revenue, or acquisitions that bring newly purchased businesses under an existing Snowflake footprint.
That matters for how the increase side should be read. These are not accounts where Snowflake out-pitched a rival in a bake-off. They are accounts where the organization is generating more data, more users, and more use cases, and Snowflake is simply where that growth lands.
Five increasers explicitly tie their plans to AI, and the use cases are more concrete than aspirational. A Global 1000 healthcare director in EMEA is extending the Snowflake AI data cloud for agentic applications inside an IT strategy that is "already defined." A Fortune 100 IT/TelCo department head is pairing AI and cloud migration to lift engineering efficiency, with further investment contingent on demonstrated ROI. An APAC IT/TelCo executive runs Snowflake as the data layer behind customer-facing products and plans to keep expanding "as we add more layers of AI into the product." Marketplace demand from end users surfaces as a quieter growth driver in a couple of accounts.
The decrease accounts are fewer but uniform in logic. Five of eight carry Vendor Consolidation, and four carry Cost Pressure. The consolidators are not unhappy with Snowflake so much as unwilling to run more than one data platform. As a large financials department head explained, "We have quite a few overlapping technologies and the idea is to consolidate them into a single non-overlapping technology stack." A midsize IT/TelCo department head said simply, "We have more than one data platform and it's time to consolidate." In both cases, Snowflake is the platform being sunset.
Cost is the other lever, and it produces the more scattered outcomes. One Fortune 100 organization is moving to a rival cloud warehouse it considers a better strategic fit and says Snowflake "is no longer considered directional." A large education VP said "total expense has grown too high" and is shifting to open source tools, accepting added headcount to maintain them. A small firm is building its own data lake on a hyperscaler, and one midsize IT/TelCo executive is taking Snowflake spend to zero and reallocating the budget to AI initiatives. Notably, AI is a reason to spend more on Snowflake in some accounts and a reason to spend less in others.
ETR recruits a minimum threshold of both increasers and decreasers for Edge commentary, so the 18-to-8 split is not a market-share verdict. Snowflake wins when the decision is about modernization, scale, or new AI and data-product workloads, and it frequently wins with new money. It loses when a different question takes over: how many data platforms do we need, and what does this one cost? At least one competitor appears on both sides of that ledger, as a source of workloads migrating to Snowflake in one account and the consolidation destination in others, which makes the single-platform decision the account-level contest to watch as ETR's Observatory for Cloud Data Warehouses arrives September 30.
The July 2026 Edge Report on Snowflake contains all 26 verbatim accounts, with spend levels, drivers, named beneficiaries, and strategic fit for each organization. See exactly which platforms are absorbing the Snowflake dollars that walk out the door: reach out to service@etr.ai or find the full commentary on the ETR Platform.
Source: ETR Edge, Snowflake Qualitative Commentary | July 2026, based on responses from 26 technology leaders.