Cloud repatriation debates aside, AI-era capacity needs have outpaced many organizations’ budgets. Paying for expensive GPUs, high-throughput storage, and data egress services often pushes unit costs past acceptable limits.
At the same time, when organizations experiment with adding new AI features, these costs can threaten budget targets as well. According to a recent report by Gartner, public cloud end-user spending is projected to total $723 billion in 2025.
In 2026, winners will operationalize cost governance. It needs to be a managed discipline, not merely a quarterly project.
Cloud costs no longer depend on predictable, steady workflows. They’re often driven by AI training that requires expensive GPU instances.
In addition, enterprises are facing:
For example, picture a data analytics firm that goes out of its way to optimize its compute spend but neglects to account for egress fees. They then implement AI models that start pulling data from one cloud to another. Egress fees quickly spike, accounting for a large share of the organization’s monthly spend. This goes unseen for months—until the finance department flags it as a spend that endangers budgetary targets.
The more volatile cloud spending gets, the more likely CFOs are to shift their expectations. The days of the cloud being “unpredictable” are going to disappear. In 2026, the CFOs who are able to successfully rein in costs will be the ones who insist on:
For example, a CFO may demand that IT teams keep track of the revenue generated by each cloud model. This may break down further into a cost-per-inference analysis, which would put cloud costs in the context of general overhead.
On a more basic level, CFOs may demand cost-per-user statistics. This would link the amount spent on cloud computing to individual users, highlighting the cloud ROI for specific employees.
For instance, a concerned CFO may decide to stop all AI experiments because an unmanaged project doubled the quarterly cloud spend. Before allowing any experimentation to proceed, the CFO may require that a system be implemented to measure the impact on customer acquisition, revenue, or another quantifiable growth-related metric. While this may be a prudent step, it could hinder innovation.
The answer isn’t halting cloud-based innovation or even reducing cloud-dependent projects. The key to navigating the admittedly reasonable concerns of CFOs is for CIOs to increase operational maturity.
Implementing a FinOps 2.0 system that combines reporting and enforcement means you control costs before invoices arrive.
This doesn’t mean you do away with visibility dashboards or stop monitoring costs. Rather, it involves establishing stringent, even automated, budget guardrails.
Consider this example: A CIO sets up a system designed to keep monthly costs under a specific number. Further, they tie that goal to a particular owner, a manager on the IT team.
Fortunately, the manager is able to set up an automated system in the cloud that:
This could prevent a number of unfortunate circumstances. A development team building an AI-enabled system can avoid excessive spending on training. Best of all, the measure is automated, so there’s no need to watch expenditures day after day, fearing costs getting out of hand.
Your infrastructure decisions should be guided by actual workload statistics rather than by worst-case assumptions. This can stop overspending because it’s based on workload realities rather than conservative predictions.
As an example, suppose a team is developing an AI model. They have to perform both training and inference modeling. Instead of running both processes on the same expensive GPU, the team decides to save money by predicting the required workload and allocating each task based on cost implications.
To make this happen, the team separates training and inference in the following manner:
This is effective because:
Depending on the workloads, this could easily result in double-digit monthly cloud savings.
Your cloud contracts don’t have to be static. In other words, there’s no need to be locked into yesterday’s architecture. Using commitments and rebids, you can optimize spending.
For instance, a dev team can structure GPU commitments around project milestones. Returning to the above example, this could consist of:
While committing to enough processing power to provide a comfortable cushion may feel like a good way to reduce pressure on the dev team, the above approach may be more effective. In reality, there’s no need to commit to using extensive GPU power before going to production. The ROI of the system may only be evident post-production, so it’s better to only commit to what you need for a proof of concept.
Then, once the model is stable and shows promise, you can commit to more GPU usage.
To better understand the power of rebids, consider another example: Your team is using two clouds to build a solution. As the project launches, it’s very difficult—perhaps impossible—to accurately predict how much data will have to flow from one cloud to another. This makes egress fees extremely hard to forecast.
Therefore, instead of buying “more than enough,” opt for a less expensive contract. As the project progresses, it becomes clear how egress fees will shape up. The team can then renegotiate the contract using insights from real, observed AI data flows.
With this approach, egress fees start small and increase only if necessary, based on real figures, not rough estimates.
By committing to a continual optimization process, you prevent unexpected cloud expenses from destroying your budget goals. It may also be necessary to adjust innovation timelines or tasks according to budget numbers.
For instance, executives may prefer a longer development timeline that keeps costs within budgetary targets instead of a short one that delivers a product by the close of the quarter.
By spreading out data- and processing-heavy tasks over time, you can present decision-makers with useful options, such as:
The key is to think like a CFO. By presenting multiple options and optimizing as you go, you show your CFO that you’re running a budget-conscious operation that prioritizes smart spending without sacrificing long-term innovation.
Here are some ideas you can use to guide your 2026 cloud spend strategy:
AI, along with other data-heavy cloud development projects, mandates a strategic approach to spending. You can still innovate and create value for your organization—as long as you build your projects on a foundation of cloud spending optimization.
Don’t let cloud costs hold back innovation. Build a foundation for fearless growth. Start with scheduling your 2026 Cloud Cost Readiness Assessment today.