BatchWise

FinOps — Cloud Financial Management Framework

Ravi Patel headshot

By — Founder + Editor-in-charge

Last updated Reviewed

FinOps = framework for cloud financial management. Three phases: Inform / Optimize / Operate. FinOps Foundation; 2026 Executive Strategy Alignment update.

Definition

FinOps is an operational framework and cultural practice for cloud financial management — maximising the business value of technology investment by enabling data-driven decisions and creating financial accountability through collaboration between engineering, finance, and business teams. The framework is maintained by the FinOps Foundation (a Linux Foundation project) and has matured into the de facto reference architecture for cloud cost management since 2018.

In 2026, the FinOps Foundation expanded the framework’s scope from pure cloud spend to all major technology spend categories — including AI/ML platform spend, SaaS subscriptions, licensing, and data centre operating costs. This makes FinOps directly applicable to the AI-finance practice that BatchWise AI operates in.

The three phases — Inform, Optimize, Operate

The framework is organised around three operational phases that an organisation iterates through continuously:

PhasePurposeCore activities
InformDeliver cost visibility and create shared accountabilityCost allocation, benchmarking, budgeting, forecasting
OptimizeReduce waste and improve efficiencyReserved capacity / committed-use discounts, right-sizing, vendor consolidation, workload routing
OperateTrack KPIs and enforce governancePolicy automation, alerts on anomalies, FinOps-as-code, executive reporting

Different members of a FinOps team can work on different phases simultaneously — engineering teams typically work in Optimize, finance teams in Inform, and leadership in Operate. The phases are not sequential gates; they are concurrent disciplines.

2026 framework updates

The 2026 FinOps Framework refresh introduced three material changes:

  1. Executive Strategy Alignment — a new core Capability under the “Manage the FinOps Practice” domain. Recognises that FinOps now operates as a strategic partner to executive leadership, not just an optimisation function. Connects technology investment to business outcomes, supports multi-year planning, and enables informed trade-offs across the technology estate.
  2. Technology Categories — refreshed taxonomy distinguishing cloud, SaaS, licensing, data centre, AI/ML, and other technology spend. Allows consistent FinOps practice across the full technology cost base.
  3. Converging Disciplines — explicit recognition that FinOps converges with adjacent disciplines: GreenOps (carbon-aware cost optimisation), AIOps (AI-driven operations management), DevSecOps (security cost optimisation), and ITAM (IT asset management).

FinOps and AI spend specifically

The 2026 framework explicitly extends FinOps practice to AI/ML platform spend — which is structurally different from traditional cloud spend optimisation in three ways:

  1. 15× cost differential between GPU and CPU compute — model + provider + instance type decisions carry materially more financial impact than equivalent decisions in traditional cloud workloads.
  2. Foundation model API consumption pricing is fundamentally different from infrastructure pricing — per-token, per-call, per-image rather than per-hour-per-instance. This requires different cost allocation logic.
  3. Make-vs-buy economics on AI platforms — fine-tuning vs API consumption vs in-house foundation model development each have distinct unit economics. FinOps frameworks built for cloud infrastructure don’t natively handle this trade-off.

BatchWise AI applies the FinOps Framework 2026 as foundation architecture, extending it with India-specific tax + regulatory overlay. See the AI Systems Review methodology page for the full integration — the 6 domains map directly to the three FinOps phases with domain-specific extensions.

India context

FinOps practice in Indian enterprises is at an earlier maturity stage than US / EU peers. Per NASSCOM 2026 data, 67% of Indian enterprises allocate less than 10% of IT budget to AI — but that figure is rising at 25-35% CAGR. This means Indian CFOs face two distinct challenges:

  • Traditional cloud cost management discipline is still maturing in many Indian mid-market companies (Inform + Optimize work largely incomplete)
  • AI spend layer is growing on top of that incomplete foundation

The result: AI spend tends to compound existing cloud cost discipline gaps rather than benefiting from a mature FinOps baseline. The BatchWise AI Systems Review engagement explicitly addresses both layers in sequence — establish the FinOps Inform baseline first, then layer in the AI-specific Optimize work.

  • GreenOps — carbon-aware cost optimisation; FinOps with sustainability overlay. Indian context: relevant for BRSR Core entities seeking to reduce both spend and reported emissions.
  • AIOps — using AI to drive operations and infrastructure management decisions. Converges with FinOps as AI itself becomes a major spend category.
  • Cloud Center of Excellence (CCoE) — organisational pattern for centralising cloud governance; FinOps practice typically sits inside or adjacent to the CCoE.

Practitioner reading