FinOps Maturity Assessment

Score your engineering team on 22 FinOps capabilities, set a target for each, and see where the biggest gaps are.

Multi-cloudAssessmentQuestionnaire

Before you start: what to have readyShow

Someone who knows how the engineering team works day to day: an engineering manager or a FinOps practitioner, ideally with a few engineers in the room.
Roughly 20 to 30 minutes for all 22 capabilities, less if some do not apply to you.
Your targets. Every target starts at level 3; lower it where a capability matters less, or leave the capability out.

Prefer a spreadsheet? The same assessment is a free Google Sheets workbook: make your own copy or download it for Excel. It still uses the 2024 capability names; see what changed in 2026.

0 of 110 rated

See the scorecard

Pick the level that describes your engineering team today, lens by lens. Every target starts at level 3; switch to Your targets to change them or to leave something out.

What each level meansShow

Knowledge

How well the team understands the capability.

0No knowledge. Knowledge of the capability is effectively nonexistent in the team. Nobody discusses it, and nobody is working to learn more about it.
1Partial knowledge. Early knowledge of the capability is beginning to spread among key stakeholders and individuals, but it is not yet common knowledge across the team.
2Developing knowledge. A limited number of key stakeholders understand the basics of the capability, but that knowledge has not spread beyond them.
3Full knowledge. Strong knowledge of the capability exists throughout the team, built into onboarding and reinforced from time to time through training or other communication.
4Knowledge leader. The team is driving awareness of the capability beyond itself, to peer groups and the wider industry, and is building new insight into it.

Process

Whether there is an agreed, repeatable way of doing it.

0No process. There are no described, consistent processes for any part of the capability in the team.
1Implementing process. Processes to standardize the capability are being formed, defined and possibly tested, but they are not yet part of business as usual.
2Developing proof of concept process. Relevant, working processes are in place, agreed and followed by at least some of the teams.
3Scaled process. Scaled processes are in place and documented, with regular feedback loops.
4Mature (agile) process. Clearly defined, transparent and fully integrated processes are established everywhere and consistent, and they are refined continuously with feedback from key stakeholders.

Metrics

Whether it is measured, and against what target.

0No metrics. Nothing is being measured, so there is no direct insight into the progress or current state of the capability.
1Identified metrics. The key metrics the business finds valuable for making trade-off decisions on this capability have been identified.
2Baselined metrics. Initial, manually produced metrics are in place, giving a basic red, yellow and green view of the capability.
3Established metrics, collected against targets. KPIs cover at least some of the capability, and they are collected on a set cadence.
4Mature, global KPIs. SMART KPIs are in place everywhere, automated and refined on a regular cadence, with a direct link to business goals and business performance.

Adoption

How much of the team actually does it.

0No adoption. The capability is not in place anywhere in the team.
1Siloed adoption. One group has adopted parts of the capability, without standards or evidence of best practice.
2Initial standardized adoption. Early parts of the capability are being standardized and checked by a few people in the team.
3Key adoption. Standardized parts of the capability are fully established in the everyday work of most of the team.
4Full adoption. The capability exists in full across the whole team and is actively used and improved.

Automation

How much of it runs without manual work.

0No automation. Almost every action the capability needs is done by hand.
1Identified automation opportunities. The team is identifying and mapping what to automate, to cut manual effort and time.
2Experimental automation. Some key actions are starting to run through automated workflows and tools.
3Primary automation. The main or most demanding actions now run through automation.
4Full automation. Every material, repeatable task in the capability is automated, and new tasks are reviewed for automation as the capability evolves.

Understand Usage and Cost

0 of 20 rated

Getting the data in, assigning every cost to an owner, and seeing what changed.

Data ingestion

Collecting billing, usage and resource data from every source into one place you can query.

Target 3

Against target: Not rated

Allocation

Assigning every cost to a team, product or environment through tags, labels and accounts.

Target 3

Against target: Not rated

Reporting and analytics

Reports and dashboards that show each team what it spends and why it changed.

Target 3

Against target: Not rated

Anomaly management

Spotting unexpected spend quickly, finding the cause and getting it fixed.

Target 3

Against target: Not rated

Quantify Business Value

0 of 25 rated

Connecting what technology costs to what it is worth: estimates, forecasts, budgets, KPIs and unit costs.

Planning and estimating

Pricing a workload or a change before it is built or deployed.

Target 3

Against target: Not rated

Forecasting

Predicting future spend from usage trends and planned changes.

Target 3

Against target: Not rated

Budgeting

Setting budgets for teams or products and tracking spend against them.

Target 3

Against target: Not rated

KPIs and benchmarking

Setting cost-efficiency KPIs and comparing them across teams, workloads and peers.

Target 3

Against target: Not rated

Unit economics

Cost per customer, transaction or feature, tied to the value it delivers.

Target 3

Against target: Not rated

Optimize Usage and Cost

0 of 25 rated

Using only what you need, at the best rate you can get.

Architecting and workload placement

Designing with cost as a requirement, and choosing where each workload runs: which cloud, region, data center or service.

Target 3

Against target: Not rated

Usage optimization

Rightsizing, scheduling and removing idle resources, so you pay only for what you use.

Target 3

Against target: Not rated

Rate optimization

Savings Plans, reserved instances, committed use discounts and negotiated rates.

Target 3

Against target: Not rated

Licensing and SaaS

Managing the software licenses and SaaS subscriptions that run on or beside the cloud.

Target 3

Against target: Not rated

Sustainability

Measuring and reducing the carbon footprint of the workloads you run.

Target 3

Against target: Not rated

Manage the FinOps Practice

0 of 40 rated

Running, teaching, governing and measuring the practice itself.

Executive strategy alignment

Tying FinOps work to executive priorities and multi-year investment plans, and giving leaders the cost data behind strategic decisions.

Target 3

Against target: Not rated

FinOps practice operations

Running the practice: owners, cadence, reviews, how decisions get made, and bringing new teams and workloads in.

Target 3

Against target: Not rated

Governance, policy and risk

Policies and guardrails, such as tagging rules and approval limits, how they are enforced, and the cost risks they cover.

Target 3

Against target: Not rated

FinOps education and enablement

Training engineers and others so cost becomes part of everyday work.

Target 3

Against target: Not rated

Invoicing and chargeback

Reconciling invoices, and showing or charging costs back to the teams that incur them.

Target 3

Against target: Not rated

FinOps assessment

Measuring the maturity of the practice on a regular cadence, as this tool does.

Target 3

Against target: Not rated

Automation, tools and services

Choosing, running and automating the tools and services the practice depends on.

Target 3

Against target: Not rated

Intersecting disciplines

Working with security, procurement, IT asset management and sustainability where they overlap.

Target 3

Against target: Not rated

Your scorecard

Rate at least one capability above to see your scorecard: how close you are to your targets in each domain and lens, a heatmap of every rating, and where to start. to see what one looks like.

Runs in your browser; nothing you enter is sent to Finitizer. The link to this result carries your ratings in the address, so keep it to come back and measure again. Level definitions adapted from the FinOps Foundation’s FinOps Assessment Guide, CC BY 4.0, edited for length and US spelling.

Want finance, product and procurement assessed too, not just engineering?

FinOps Current State Assessment: We review your FinOps practice across finance and engineering and give you a scored plan for what to fix first. $1,500, fixed. Nothing paid upfront.

See the service

About this assessment

Engineers make most of the decisions that set a cloud bill, yet most FinOps assessments read as if they were written for finance. This one was first published as a free spreadsheet on finitizer.com, built for the engineering persona: it asks how your engineering team understands, runs, measures, adopts and automates each part of managing cloud cost.

It covers the four domains of the FinOps Framework 2026: understanding usage and cost, quantifying business value, optimizing usage and cost, and managing the FinOps practice. Under them sit its 22 capabilities, from data ingestion and allocation to unit economics, rate optimization, and governance, policy and risk.

How to use it, in the workbook’s four steps:

Set targets for every capability, or only the ones you want to focus on, and leave the rest out.
Rate where the team is today on each lens you set a target for.
Review the gaps for each domain and overall, and start with the capabilities furthest behind.
Come back and measure again as you make changes. The link to your result keeps every rating.

Gaps are usually closed with training, better practices and better use of tools. Measured over time, the assessment also shows whether that work is paying off.

The spreadsheet version

The same assessment as a free Google Sheets workbook. Its Start Here tab has the purpose, the steps and every level definition; its Engineering tab has the 22 capabilities with a Target and an Actual column for each lens, and the totals for each capability, each domain and overall. The original is view-only, so make your own copy before you fill it in. The workbook still uses the 2024 capability list; the differences are listed under “What changed in the 2026 Framework” below.

Make a copy in Google Sheets Download for Excel (.xlsx)View the original

Making a copy needs a Google account. The Excel download does not.

What changed in the 2026 Framework

The FinOps Foundation published the FinOps Framework 2026 on March 19, 2026. This page follows it; the spreadsheet still has the 2024 list. Still 22 capabilities, with these differences:

Added: Executive strategy alignment, in Manage the FinOps Practice.
No longer listed: Onboarding workloads. FinOps practice operations now covers bringing new teams and workloads into the practice.
Renamed: Benchmarking is now KPIs and benchmarking.
Renamed: Architecting for cloud is now Architecting and workload placement.
Renamed: Workload optimization is now Usage optimization.
Renamed: Cloud sustainability is now Sustainability.
Renamed: Cloud policy and governance is now Governance, policy and risk.
Renamed: FinOps tools and services is now Automation, tools and services.
The domains dropped “Cloud” from their names: Understand Usage and Cost, and Optimize Usage and Cost.

Definitions

Framework: The FinOps Foundation’s end-to-end view of a FinOps practice: its domains, capabilities, lifecycle, maturity model and principles.
Domains: The areas of activity a practice needs to cover. You can assess any or all of them.
Understand Usage and Cost: Getting the data in, assigning every cost to an owner, and seeing what changed.
Quantify Business Value: Connecting what technology costs to what it is worth: estimates, forecasts, budgets, KPIs and unit costs.
Optimize Usage and Cost: Using only what you need, at the best rate you can get.
Manage the FinOps Practice: Running, teaching, governing and measuring the practice itself.
Personas: The teams involved in a FinOps practice: leadership (IT, finance and the wider organization), finance, product, engineering, procurement and the FinOps practitioner who guides and trains the rest. This assessment is for engineering, the team that builds on and runs the cloud.
Measurement lenses: The five sides from which each capability is scored, each from 0 to 4:
Knowledge: How well the team understands the capability.
Process: Whether there is an agreed, repeatable way of doing it.
Metrics: Whether it is measured, and against what target.
Adoption: How much of the team actually does it.
Automation: How much of it runs without manual work.

For the full model, see the FinOps Foundation’s FinOps Assessment Guide.

Questions

What is a FinOps maturity assessment?

A structured way to score how well a team manages cloud cost, capability by capability, on levels the rest of the industry also uses. This one follows the FinOps Foundation’s assessment model: the 22 capabilities of the FinOps Framework 2026, in its four domains, each rated from 0 to 4 on five lenses. The detail is the point. A common result is strong rate optimization and rightsizing beside no unit cost at all, which one overall number would hide.

How is it scored?

Each lens of each capability gets a target and a current level, and a rating counts once it has both. The score is the sum of your current levels divided by the sum of your targets, the same sum the spreadsheet uses, so 100% means you are at your targets on balance. Capabilities, domains and lenses are summed the same way. The gap list counts only the lenses below target, so being ahead on one lens never hides a gap on another.

What do Crawl, Walk and Run mean here?

They are the FinOps Foundation’s names for how far along a practice is. Here they come from your average current level, rounded: 0 or 1 is Crawl, 2 is Walk, 3 or 4 is Run. That mapping is ours, so read it as shorthand for the averages rather than an official rating. Not every capability needs to reach Run: set higher targets where the money is.

Who should fill it in?

Usually an engineering manager, a FinOps practitioner or a consultant, working through it with the engineering team. The results are written for senior management in engineering and finance. It covers the engineering persona only; finance, product, procurement and leadership see the same capabilities from a different side.

Can I use the spreadsheet instead?

Yes. The original workbook is view-only, so make your own copy in Google Sheets or download it for Excel. It has the same lenses and levels, but the 2024 capability list: six capabilities carry their older names, and it has Onboarding workloads where this page has Executive strategy alignment. It also counts a cell you have not rated as zero, where this page leaves it out until you rate it, and it has no heatmap or stages. Download the CSV here to keep your ratings beside it.

Which version of the FinOps Framework does it follow?

The FinOps Framework 2026, published by the FinOps Foundation in March 2026. That release added Executive Strategy Alignment, renamed six capabilities (Workload Optimization became Usage Optimization, for example), and no longer lists Onboarding Workloads, which FinOps Practice Operations now covers. A result saved before this page moved to the 2026 list still opens: its ratings move to the new names, and the page tells you what could not be carried over.

Is anything I enter sent to Finitizer?

No. The scoring runs in your browser. Your ratings are kept in the page address, so the link is your saved copy: bookmark it, share it, and open it again when you measure next time. Usage statistics record that the tool was used, never the ratings. Only if you use "Email me this result" is the link sent, with the figures if you tick the box.

How is this different from the Cloud & AI Cost Readiness Assessment?

The readiness assessment is 25 questions on the whole practice, AI spend included, and emails you the result. This one is for engineering teams, scores 22 capabilities against targets you set, and shows the result on the page as you go.

Related tools

Cloud & AI Cost Readiness Assessment

Score your FinOps practice against the four framework domains.

Open

Cost Allocation Score

Score how much of your cloud spend you can assign to a team.

Open

FOCUS 1.4 Validator

Check a billing export against FOCUS 1.4, with no file size limit.

Open

More tools for: Billing data, allocation and governance

A self-assessment says where you think you are. Your bill says where you are.

Finitizer reads your AWS and Google Cloud billing, read-only and keyless, and tracks allocation, anomalies and commitments every day, so the metrics behind your next assessment come from the bill rather than from memory.

See how Finitizer works