Cloud & AI Cost Readiness Assessment
A 25-question self-assessment across Understand, Quantify, Optimize and Manage — the FinOps Framework's own domains — scoring each capability from "not in place" to "automated and measured". Results are emailed to you.
This is the one item on this site that is not instant. Everything else here computes in your browser and shows you the answer immediately, with no login and no email. The assessment asks for a name and an address and sends the result to you — so it is worth knowing that before you begin, rather than at question 25.
What it covers
The assessment follows the FinOps Framework’s four domains rather than a taxonomy of our own. That matters more than it sounds: the output maps onto vocabulary your team already uses, and the score is comparable to how the rest of the industry describes the same capabilities.
Understand
6 questions- Visibility and allocation
- Planning and forecasting
Everything else depends on this one. A team that cannot attribute spend to a service or a customer cannot prioritise, cannot forecast, and cannot tell an anomaly from a launch. Low scores here cap the score in every other domain.
Quantify
2 questions- Business value
- Unit economics
The shortest section and the one most often scored lowest. Without a unit metric — cost per customer, per transaction, per model call — a rising bill is indistinguishable from a growing business, and cost conversations stay defensive.
Optimize
12 questions- Workloads and architecture
- Commitments and pricing
- Network, storage, licensing and AI
The largest section, because it is where the money is. It is also where most teams over-rate themselves: buying reservations is one capability out of a dozen, and the ones next to it — network, storage, licensing, AI — are usually the untouched ones.
Manage
5 questions- Governance and policy
The domain that decides whether savings stay saved. Without policy, ownership and a cadence, an optimisation programme is a one-off cleanup that quietly reverses over the following two quarters.
How each question is scored
Every question uses the same five-point scale, and each option carries a short note on why that capability matters — so the assessment teaches while it scores.
- 0Not in place
- 1Ad hoc / manual
- 2Defined but inconsistent
- 3Consistently applied
- 4Fully in place, automated & measured
Four of the questions, verbatim
So you can judge the depth before committing the time.
What proportion of your cloud spend can be attributed to a specific team, product or customer without manual work?
Allocation coverage is the foundation metric. Anything below about 80% means the remaining spend has no owner and therefore no one whose job it is to reduce it.
Do you track a unit cost metric that connects cloud and AI spend to business volume?
This is the question that turns "the bill went up 30%" into "the bill went up 30% and we served 45% more, so unit cost fell". Most teams score lowest here.
How systematically do you manage the cost of AI and LLM workloads — tokens, inference, GPU utilisation?
Nearly every FinOps team now carries AI spend, and it is the capability most often described as "we know we should". Agentic workloads consume several times the tokens of a chat exchange, so the gap compounds quickly.
Are cost policies — tagging standards, commitment approval, budget thresholds — enforced automatically rather than by review?
The difference between a policy and a document. Automated enforcement is what stops a cleanup from reversing over the following two quarters.
Frequently asked questions
What is a FinOps maturity assessment?
A structured self-evaluation of how systematically an organisation manages cloud and AI spend, scored capability by capability rather than as a single number. The point is not the total — it is discovering that you are strong on commitments and have no unit metric at all, which is the pattern in most teams and is invisible until you score each capability separately.
What are the four FinOps domains?
Understand (visibility, allocation, planning and forecasting), Quantify (business value and unit economics), Optimize (workloads, architecture, commitments, network, storage, licensing and AI) and Manage (governance and policy). They come from the FinOps Foundation's framework, which is why the vocabulary will already be familiar to anyone who has read it.
How long does the assessment take?
25 questions, about 8 minutes. Each question is a five-point scale and carries a short explanation of why the capability matters, so it reads faster than the question count suggests.
Do I need to enter my email?
Yes — this one is the exception on this site. The assessment collects a name and an email and sends the result to you rather than showing it on screen. Every other tool here computes in your browser with no login and no email, and we would rather say that plainly than have you find out at question 25.
What do I get back?
A maturity score with a breakdown by domain, so you can see which capabilities are carrying the practice and which are gaps. The most common outcome is a strong Optimize score alongside a weak Quantify one — plenty of savings activity, no unit metric to prove it mattered.
Ready when you are
25 questions, about 8 minutes, results by email. If you would rather have an answer on screen right now, the bill diff and the allocation score read your own billing export and tell you immediately, with no email at all.