Skip to content
FinOps workspace
COST LEDGER / OFFICIAL RELEASE

FinOps mission update: from cloud to technology value

Published and reviewed: 1 October 2026

Scope my cloud cost review

On 19 February 2026 the FinOps Foundation moved its mission from the value of cloud to the value of technology.

Illustrative server cabinets in a mint-lit room
Illustration, not customer infrastructure.
On this page
  1. The change, in one word
  2. The evidence the Foundation cites
  3. What to change in a brief
  4. Questions to settle after the mission change
  5. Primary sources

The change, in one word

On 19 February 2026 the FinOps Foundation announced that its mission, approved by its Governing Board, moves from « advancing the people who manage the value of cloud » to « advancing the people who manage the value of technology ». The announcement ties the change to the State of FinOps 2026 survey and says the framework, training and certifications will be updated in the following months. The Framework 2026 update of 19 March 2026 aligned its definition of FinOps with the new mission.

The announcement also says new working groups are being launched on AI value, IT financial management integration and executive alignment. A mission statement is a positioning choice by an industry body. It is not a standard, a regulation or a requirement placed on any company that buys cloud services.

The evidence the Foundation cites

The announcement quotes figures from the State of FinOps 2026 report: 98% of practitioners manage AI spend (31% two years earlier), 90% manage SaaS (65% the year before), 64% manage licensing (49%), 57% manage private cloud (39%), 48% manage data center (36%), and 28% reported managing labor costs. These are survey answers from practitioners who responded, as the State of FinOps 2026 item on this site details, and they describe the Foundation's community, not the average company.

The useful reading for a buyer is narrower.

What to change in a brief

Start from the investment question, not the size of the cloud bill. A lower bill is one possible objective. A unit cost per customer, a safer multi-year obligation or a forecast finance trusts are others, and each calls for different deliverables and different evidence. The SaaS unit economics guide and the forecasting guide show what those deliverables look like.

  • State the decision the work will support and the customer owner accountable for it.
  • Separate the cloud assessment from any other technology category, each with its own data source and acceptance check.
  • Ask how internal engineering time is counted in the benefit, beside provider fees.
  • Ask for a method example on dummy data before you share production exports.

Questions to settle after the mission change

Many providers now describe their offer as « technology value ». Ask what it includes in practice. Which categories have they worked on beyond public cloud, and what deliverable did that work produce? Who performs licensing analysis if it is included, and is that person qualified for the products you run? Which part is advice and which part is implementation that you must approve?

Keep the roadmap apart from the first purchase. A bounded review can set a cost baseline and identify the next question. A later phase would then get its own data boundary and acceptance conditions, as laid out in the audit pricing guide, which lists what a quote should state about scope, deliverables and exclusions.

Primary sources

The FinOps Foundation mission update, read in full for this page:

Continue your review

Get support on my project

A specialist in the subject reviews your request and sends you a quote.

Get support on my project
Get my FinOps quote