0 / 24

Model 40 of 74 · Technology & Data

FinOps / Cloud Cost Management Maturity Assessment

Assess how well your organisation understands, controls, and gets value from its cloud and technology spend.

Pillars & areas

Inform

See where money goes

  1. 01Cost Visibility & Allocation
  2. 02Accountability & Collaboration

Optimise

Spend wisely

  1. 03Budgeting & Forecasting
  2. 04Usage & Rate Optimisation

Govern

Connect cost to value

  1. 05Unit Economics & Value
  2. 06Governance & Policy

Levels

  1. 1Bill ShockSurprised by the invoice
  2. 2Cost-VisibleAllocated & reviewed
  3. 3Value-OptimisedCost tied to value

01 Cost Visibility & Allocation

Can the organisation see what it spends, and attribute costs to the teams, products and customers that drive them?

0/4 answered

VA-1How quickly can your organisation see what it is spending?

Think about whether cost data is available daily or only when the monthly invoice arrives.

VA-2How are costs allocated to teams, products or services?

Consider whether resources are tagged or organised so that each cost has an owner.

VA-3How are shared costs handled?

Think about shared platforms, networking, support contracts and other costs that serve many teams.

VA-4How visible are costs to the engineers who create them?

Consider whether engineers can see the cost of their services and the impact of their changes.

02 Accountability & Collaboration

Do the people who drive costs take responsibility for them, working together with finance and the business?

0/4 answered

AC-1Who is accountable for cloud costs?

Think about whether teams that create costs are responsible for them, or whether a central team or finance carries the burden alone.

AC-2How do finance and engineering work together on technology costs?

Consider whether they share data, language and goals, or blame each other.

AC-3Is there a central function supporting cost management?

Think about whether someone sets standards, provides tools and data, and helps teams optimise.

AC-4How is cost awareness built across the organisation?

Consider training, sharing of successes and recognition of good cost decisions.

03 Budgeting & Forecasting

Are technology costs budgeted and forecast accurately, with surprises spotted early?

0/4 answered

BF-1How are cloud budgets set?

Think about whether budgets are based on expected usage and plans, or simply last year plus a percentage.

BF-2How accurate are your cost forecasts?

Consider how close forecasts are to actual spending, and whether accuracy is measured.

BF-3How quickly are unexpected cost increases detected?

Think about whether a sudden spike is caught within hours or days, or only on the next invoice.

BF-4How are budget variances managed?

Consider what happens when a team overspends or underspends.

04 Usage & Rate Optimisation

Is waste removed and are the best available prices secured?

0/4 answered

OP-1How are idle and oversized resources dealt with?

Think about unused servers, oversized databases, forgotten environments and storage that is no longer needed.

OP-2How does your organisation use commitment-based discounts?

Consider reserved capacity, savings plans, committed-use agreements and enterprise discounts.

OP-3How is cost efficiency considered in architecture?

Think about whether services are designed with cost in mind — for example choosing managed services, storage tiers and scaling approaches.

OP-4How are SaaS subscriptions and licences managed?

Consider unused licences, duplicate tools and auto-renewing subscriptions.

05 Unit Economics & Value

Is technology spending linked to the business value and outcomes it supports?

0/4 answered

UE-1Does your organisation measure unit costs?

Think about measures such as cost per customer, per transaction, per order or per active user.

UE-2How is cost growth judged?

Consider whether rising costs are automatically seen as bad, or judged against growth in usage and revenue.

UE-3How does cost information influence product and pricing decisions?

Think about whether the cost of serving customers or features is considered when pricing or prioritising.

UE-4How are technology investments evaluated?

Consider whether new services, migrations and major changes have a clear cost-benefit case, and whether benefits are checked afterwards.

06 Governance & Policy

Are there sensible guardrails that prevent waste without slowing teams down?

0/4 answered

GP-1What guardrails exist to prevent excessive spending?

Think about policies on resource types, regions, sizes and budgets, and how they are enforced.

GP-2How are spending decisions approved?

Consider whether approvals are proportionate, or whether everything requires the same heavy process.

GP-3How are cloud providers and contracts managed?

Think about negotiations, enterprise agreements and dependence on particular providers.

GP-4How is the environmental impact of cloud usage considered?

Consider whether carbon emissions are measured alongside cost, and whether this influences decisions.

Self-assessment report

FinOps / Cloud Cost Management

Answer the questions above and your report builds here: an overall score, a score and target for each area, and the three changes that matter most.

About this model

About the FinOps / Cloud Cost Management maturity model

Cloud computing turned technology spending from a few large, planned purchases into millions of small decisions made every day by engineers. That flexibility is enormously valuable, but it also means costs can grow quickly and invisibly. Many organisations discover the problem through a shocking invoice, respond with a short-lived cost-cutting drive, and then watch spending creep back up.

This model treats cloud cost management as a shared discipline between engineering, finance and business teams rather than a finance policing exercise. The goal is not simply to spend less, but to spend well: to know what is being spent and why, to make the people who drive costs aware of and accountable for them, to forecast reliably, to remove waste, and to connect spending to the value it creates. It applies to public cloud, SaaS and other consumption-based technology spending.

The FinOps / Cloud Cost Management maturity model contains 24 questions across 6 areas: cost visibility and allocation, accountability and collaboration, budgeting and forecasting, usage and rate optimisation, unit economics and value, and governance and policy. Each question describes three levels of maturity through observable practices. It goes deeper than the cost management area of the Cloud Maturity model and is relevant to any organisation with significant consumption-based technology spend.

Who this assessment is for

  • FinOps practitioners and cloud cost or cloud centre of excellence teams
  • Engineering and platform leaders
  • Finance business partners, FP&A and procurement teams supporting technology
  • CTOs, CIOs and CFOs
  • Product owners responsible for the economics of their services

The three maturity levels

  • Level 1 — Bill Shock: Cloud costs are reviewed only when the invoice arrives, and surprises are common. Spending cannot be attributed to teams, products or customers, engineers have no visibility of what their decisions cost, and finance and engineering speak different languages. Cost-saving efforts are occasional campaigns triggered by alarm, and savings rarely last.
  • Level 2 — Cost-Visible: Most cloud costs are tagged and allocated to teams or products, and owners see their spending regularly. Budgets and forecasts are set with engineering input, anomalies are investigated, and common optimisations such as right-sizing, shutting down idle resources and committed-use discounts are applied as routine. Finance and engineering meet regularly to review spending.
  • Level 3 — Value-Optimised: Engineering teams treat cost as a design consideration alongside performance and reliability. Spending is tied to business measures such as cost per customer or transaction, forecasts are accurate, and optimisation is continuous and largely built into how platforms work. Decisions about technology investment are made using a shared understanding of cost and value across engineering, finance and the business.

The 6 areas assessed

1. Cost Visibility & Allocation

How well cloud and consumption costs are understood. This area covers access to timely cost data, tagging and allocation of costs, the treatment of shared costs, and the visibility of costs to the people who drive them.

2. Accountability & Collaboration

How responsibility for cost is shared. This area covers ownership of costs by engineering and product teams, collaboration between finance, engineering and business, the role of a central cost management function, and how cost awareness is built.

3. Budgeting & Forecasting

How the organisation plans and predicts consumption-based spending. This area looks at budget setting, forecasting methods and accuracy, detection of anomalies, and how variances are managed.

4. Usage & Rate Optimisation

How the organisation reduces unnecessary spending. This area covers right-sizing and removing idle resources, commitment-based discounts, architectural efficiency, and the management of SaaS and licence spending.

5. Unit Economics & Value

How cost is connected to value. This area covers unit cost metrics, the link between cost and business performance, the use of cost information in product and pricing decisions, and cost-benefit analysis of technology investment.

6. Governance & Policy

The policies and controls that shape spending. This area covers spending policies and guardrails, approval processes, provider and contract management, and the environmental impact of technology consumption.

How this model relates to other frameworks

This is an original, simplified maturity model and is not derived from or intended to replace any of the following. However, organisations that use this assessment may also find value in these established frameworks:

  • FinOps Framework (FinOps Foundation) — a widely used framework describing principles, capabilities and roles for cloud financial management
  • FOCUS (FinOps Open Cost and Usage Specification) — an open specification for consistent cloud cost and usage data
  • Cloud providers' well-architected cost optimisation guidance — cost optimisation guidance published by major cloud providers
  • Technology Business Management (TBM) taxonomy — a standard taxonomy for allocating and communicating technology costs

Frequently asked questions

What is the FinOps / Cloud Cost Management maturity model?

Assess how well your organisation understands, controls, and gets value from its cloud and technology spend. It is an original, simplified model with three maturity levels (Bill Shock, Cost-Visible and Value-Optimised), assessed through 24 questions across 6 areas: Cost Visibility & Allocation, Accountability & Collaboration, Budgeting & Forecasting, Usage & Rate Optimisation, Unit Economics & Value and Governance & Policy.

How long does the FinOps / Cloud Cost Management assessment take?

Most people finish in 10–14 minutes. Each of the 24 questions has three concrete answer options. Your progress is saved in the page URL, so you can bookmark it and come back later.

How is the score calculated?

Each answer scores 1 (Bill Shock), 2 (Cost-Visible) or 3 (Value-Optimised). An area's score is the average of its answered questions, and the overall score is the average of the area scores, so every area counts equally. Scores run from 1.0 to 3.0.

Is my data stored or shared?

No. Your answers are never sent to a server. They are stored only in the page URL, which you control. Copy the link to share results with colleagues, or export a PDF or CSV report.

How should I use the results?

Start with "Where to focus" in your report. It lists the questions with the biggest gap to the target you set for each area, and shows what the next level looks like in practice. For a fuller picture, ask several people from different teams to complete the assessment and compare their links. Differences in perception are often as revealing as the scores themselves.