“Who is accountable for the cloud bill, and what is it paying for?”
All four FinOps domains and their 22 capabilities, the Inform, Optimize and Operate phases, the personas, the maturity model, scopes and technology categories — with billing data shaped around the FOCUS specification. Cloud, SaaS, data center and AI spend land in one book with the budget, the portfolio and the strategy they serve, and untagged spend is assigned to its likely owner. Set your own scopes, tags and rules. Annual framework revisions and new FOCUS releases arrive as change sets you approve. And TBM, tokenomics and asset management count the same dollars.
The pressure
Most FinOps practices run in a cloud cost tool beside everything else. Tags decide ownership, so untagged spend has none. Savings are found every month and few reach the budget. Finance ties the bill to the invoice and the ledger by hand. And the parts of the framework that reach past the cloud — SaaS, the data center, AI, executive strategy — sit outside the tool entirely.
What it looks like today
Full coverage
Domains, capabilities, phases, personas, technology categories and the FOCUS datasets — each mapped to where it runs, beside the budget, the portfolio and the architecture.
Mapped to the FinOps Framework (March 2026) and FOCUS 1.4
Know what is spent, and by whom.
Plan it, forecast it, measure what it returns.
Spend less for the same work, and spend it in the right place.
Run FinOps as a discipline, not a dashboard.
How the practice runs and grows.
What the spend is, and why it exists.
One shape for every provider’s bill.
What changes
FinOps as a cloud cost tool
FinOps across cloud, SaaS, data center and AI, in the same book as the rest of IT
Ownership by tag, or not at all
Every dollar with an owner — untagged spend assigned to its likely owner for confirmation
Savings reported as found
Savings tracked from identified to realized, and banked only when the budget moves
A bill nobody ties to the ledger
Usage to billed to invoiced to booked, in one chain
Rate and usage, worked together
Rate optimization judges commitments on two measures: how much usage they cover, and how much of what you bought you actually use. Dotwork shows both, never blended into one number, with the effective savings rate and the agreements nearing their notice window. Usage optimization becomes a ranked backlog — each item with its evidence, its owner and its value — followed until the saving lands in the budget.
Where other tools stop
Cloud cost platforms rank the savings and stop there. Here each commitment and each saving sits in the same book as the budget, the contract and the product it serves.
Flexed to how you run
The FinOps Framework says what a practice should do, not how your company is organized. Shape scopes, allocation and chargeback around your own structure; the capabilities stay intact for comparison.
Your scopes, not a template
Define scopes as products, cost centers, environments or initiatives. They can overlap — the same dollar shows in each view and is counted once in the total.
Tags where you have them, rules where you don’t
Allocate by tag, account or shared-cost rule. Untagged spend gets a proposed owner instead of a shared bucket, and the confirmation sticks.
Showback before chargeback
Show teams what they use with a bill they can question line by line, and move to chargeback when the numbers have earned it.
Start at your maturity
Begin with one technology category at crawl — usually public cloud — and add SaaS, the data center and AI as each category’s data comes in.
Every annual revision
The FinOps Foundation revises the framework each year, and FOCUS ships new releases through the year. Each revision is compared with your capabilities, scopes and billing fields, and the renames and remaps go to the FinOps lead for approval. Prior periods keep the names and shape they were reported under.
A new capability: Executive Strategy Alignment
Technology spend read beside the strategy and multi-year investments in Steer and Strategic Portfolio Management
Public cloud, SaaS, data center, data cloud platforms and AI became technology categories; scopes became business segments
Categories label the spend; scopes become views over products, cost centers and initiatives — each move proposed for approval
Six capabilities renamed, including Usage Optimization and Governance, Policy & Risk
New names shown everywhere; the mappings behind them don’t change
Onboarding Workloads no longer listed as its own capability
Its records re-homed under Architecting & Workload Placement, with past periods kept as they were
FOCUS 1.4 adds Invoice Detail and Billing Period datasets
Mapped to Confirm the Invoice, where usage already ties to billed, invoiced and booked
FOCUS 1.4 expands contract commitments and splits the provider into service provider, host provider and invoice issuer
Commitments mapped to Fix the Commitments; who sold, hosted and invoiced proposed as separate fields
Every framework, one model
Most companies run FinOps beside TBM, asset management, a planning tool and a capability map — each with its own number for the same spend. Here the spend is recorded once and every framework reads it.
IT spend taxonomy
TBM allocates the same cloud and SaaS lines into its towers and pools — one number, two views.
Explore TBMFinOps for AI · token and model spend
The AI technology category, metered by model, team and agent.
Explore TokenomicsISO/IEC 19770 · licenses, contracts and renewals
SaaS licenses, contracts and renewals sit beside the cloud commitments they compete with.
Explore IT Asset ManagementActivity-based costing · rolling forecasts · Beyond Budgeting
The cloud forecast is part of the same driver-based plan finance uses for everything else.
Explore Cost & Planning MethodsTIME model · 7 Rs
Cloud cost per application feeds the TIME decision, and after a migration the bill follows the app.
Explore App RationalizationCapability and process maps
Cloud spend shows up in cost by capability, beside everything else it costs.
Explore BIZBOK & APQCAI-native FinOps
Finding owners, flagging anomalies, ranking waste, reading commitments and tying the invoice to the ledger run continuously. Each finding goes to an engineering, FinOps or finance owner to act on, and every change can be undone. Estimated savings are never reported as realized ones.
Infers the likely owner of untagged spend from its tagged neighbors and queues it for confirmation.
Flags spend that jumps well above its recent trend and services that appear for the first time, and sends each one to the backlog.
Ranks idle and oversized resources by cost and utilization, with idle age, confidence and a recommended action.
Reads coverage, utilization and unused commitment together and flags agreements expiring inside their notice window.
Follows each provider’s charges from usage to billed, invoiced and booked, and flags invoices with no purchase order or not yet booked.
Moves each opportunity from identified to accepted, in progress and realized, and warns when realization falls behind the estimate.
Carries each allocated cloud dollar to the product, capability, project and business unit it serves, so cost can be read against value.
Lines up each new framework or FOCUS release against your capabilities, scopes and billing fields, and drafts the renames and remaps.
Where it runs in Dotwork
Dotwork does not ask you to adopt a new method. The framework becomes a view over the same model these solutions already read and write.
Fund & Optimize
“What is the cloud bill actually paying for — and is it worth it?”
ExploreFund & Optimize
“Where does the money actually go — and can I trust the number?”
ExploreFund & Optimize
“Can we still move money before the period closes?”
ExploreFund & Optimize
“What does our AI actually cost — and what did it return?”
ExploreFund & Optimize
“What did we buy, and is it used?”
ExploreHow it compares
Cloud cost platforms cover the cloud bill well. Provider consoles and spreadsheets cover the rest by hand. FinOps on Dotwork covers every domain and technology category and connects the spend to the budget, the portfolio and the strategy it serves.
| Capability | Cloud cost platforms | Provider consoles & spreadsheets | FinOps & FOCUS on Dotwork |
|---|---|---|---|
| Spend by service, account, team and tag | |||
| Anomalies, waste and rightsizing | Partly | ||
| Commitment coverage and utilization together | Partly | ||
| Untagged spend assigned to its likely owner | Partly | ||
| Usage to invoice to ledger in one chain | Partly | ||
| Savings tracked from identified to realized | Partly | ||
| Cloud, SaaS, data center and AI in one book | Partly | ||
| Every FinOps capability mapped, including Executive Strategy Alignment | Partly | ||
| Yearly framework and FOCUS changes approved as change sets | Partly | ||
| Wired to budgets, the portfolio, architecture and strategy |
Who it is for
“Can we run every capability without a separate tool for each one?
“What do my team’s services cost, and what should we change first?
“Does the cloud bill tie to the invoice and the ledger?
“What does my product cost to run per user, and is that rising?
“Which commitments are underused, and which SaaS renewals come up next?
“Is our technology spend moving the strategy — and which savings reached the budget?
Before you buy
How to get a number instead of a pitch.
1
Good answer · A likely owner for each line, confirmed once and remembered.
Bad answer · A shared bucket, spread by percentage.
2
Good answer · Usage, billed, invoiced and booked in one chain, with every difference explained.
Bad answer · Finance matches it in a spreadsheet after the close.
3
Good answer · Renames and new capabilities arrive as a change set you approve, with history kept.
Bad answer · A re-implementation, or a line on the roadmap.
More in Finance & Cost
IT spend taxonomy
ExploreFinOps for AI · token and model spend
ExploreASC 350-40 · ASU 2025-06 · IAS 38
ExploreISO/IEC 19770 · licenses, contracts and renewals
ExploreActivity-based costing · rolling forecasts · Beyond Budgeting
ExploreFinance & Cost
The standards finance and IT finance use to say what technology costs and who uses it.
The model underneath
Steer, Fund & Optimize and Govern & Deliver all read and write the same Enterprise Operating Model. The first module you license builds the model. Every module after it adds context instead of another silo — and Dotwork AI reads all of it, stopping where the decision is yours.
See the Enterprise Operating Model© 2025-2026 Dotwork, Inc. All rights reserved.