From cloud cost to AI value: The next evolution of FinOps

Why traditional cost control frameworks fail

According to recent research by Flexera, after five consecutive years of decline, estimated wasted cloud spend has ticked back up to 29%, highlighting the growing cost complexity introduced by AI workloads.  

AI introduces a bursty, behaviour-driven cost model that traditional control mechanisms weren’t built to monitor. Instead of regular compute hours or provisioned resources, costs are driven by variable factors like token counts, inference calls, and immediate consumption patterns. To complicate matters, these expenses are heavily influenced by complex contractual pricing terms and multi-layered software subscriptions. Unpredictable and bursty AI workloads are now cited by 27% of organisations as their single top challenge in managing technology costs, making accurate forecasting incredibly difficult for finance departments. 

Compounding the problem are significant tooling limitations. Most current cost-management platforms lack robust tracking mechanisms specifically designed for AI infrastructure. As a result, organisations cannot simply plug in their existing software tools; they must adapt their foundational FinOps practises to compensate for these tracking gaps.

Key differences in traditional cloud and AI spending

 

Traditional cloud spend	AI spend
Often tied to infrastructure capacity	Often tied to usage behaviour
Easier to forecast from known workloads	More volatile due to prompts, tokens, inference and experimentation
Usually owned by IT or engineering	Often spread across business units, SaaS tools and APIs
Optimised through reserved capacity, rightsizing and shutdowns	Optimised through model choice, prompt design, routing, caching and usage governance

From cost containment to value discovery

Effective FinOps for AI requires a shift in focus. Most organisations initially approach AI spend through a cost containment lens, asking how to control or reduce rapidly growing costs. However, long-term success with AI depends less on minimising spend and more on understanding where AI is creating measurable business value.

Before optimisation becomes meaningful, organisations must first establish visibility into what is driving spend, where variability comes from, and which AI investments are producing outcomes worth scaling.

Achieving this requires a structured, iterative approach that shifts the conversation away from reactive cost management and toward intentional, value-driven decision-making.

Step 1: Start small and define scopes

• Do not try to govern all AI spend at once
• Start with a single AI use case, workload, or team to establish visibility and understand cost behaviour before scaling broader governance practises
• Build understanding incrementally so teams can develop confidence in the data, reporting, and resulting financial decisions.

Step 2: Map workloads to cost drivers

• Use whiteboarding sessions and cross-functional discussions to understand what triggers AI usage, what drives variability, and how requests flow through the system
• Identify where spend is influenced by architecture decisions, managed services, automation, or user behaviour
• Connect workload behaviour to business outcomes and financial impact rather than viewing AI costs as isolated infrastructure spend.

Step 3: Identify where costs originate and where waste hides

• Identify underlying cost drivers such as tokens, GPU usage, model training, data movement, and SaaS AI services
• Recognise that AI spend often extends beyond a single AI line item and may include multiple layered costs across platforms and teams
• Establish ownership and lifecycle accountability so experimentation does not quietly evolve into persistent operational spend.

Step 4: Surface optimisation levers before optimising

• Evaluate multiple models early to better understand the tradeoffs between cost, speed, quality, scalability, and flexibility before standardising
• Identify areas where usage behaviour can be shaped through prompt size, retries, routing, caching, or workflow design
• Focus optimisation conversations on making tradeoffs visible and intentional rather than simply driving cost reduction targets.

Step 5: Introduce unit economics

• Shift the conversation from total AI spend to cost per meaningful outcome, such as cost per workflow, customer interaction, recommendation, or AI-generated result
• Recognise that high AI spend does not inherently indicate inefficiency if it is producing measurable business value or competitive advantage
• Use unit economics to improve the cost-to-value equation and guide investment decisions with greater financial clarity.