Inform, optimize, operate
FinOps Foundation · FinOps Framework
Visibility first, then optimization, then an operating rhythm — each with its own room, its own measures and its own owner.
Cloud spend tied to what it is for — and proof the savings landed.
“What is the cloud bill actually paying for, and is it worth it?”
Cloud cost tools are good at finding savings. They can’t tell you what the spend is for. Cloud Spend Optimization does the FinOps job — break down the bill, find the waste, manage commitments, flag anomalies, confirm the invoice — and then does what only an operating model can: it ties every cloud dollar to the team, product, capability and project it serves, tracks each saving from identified to realized, and puts cloud in the same book as people, software and AI. So the question changes from “how do we spend less?” to “is this spend earning its keep?”
Rooms you open
- See the Cloud Bill
- Confirm the Invoice
- Allocate the Cloud
- Find the Waste
- Fix the Commitments
- Act on the Backlog
Methods supported
FinOpsFOCUSTBM
Part of Fund & Optimize · How do we plan, allocate and optimize resources?
The problem
Cloud tools save money. Nobody can say what the spend is for.
The cloud bill is broken down by account and service, but not by the products and capabilities it serves. Savings are identified every month and few of them reach the budget. Commitments are judged on one number. The bill, the invoice and the ledger are reconciled by hand. And when spend rises while the business value stays flat, nobody can see it until finance asks.
What it looks like today
- Untagged spend with no owner
- Savings identified but never realized
- Commitments judged on coverage or utilization, never both
- Bill, invoice and ledger that never quite match
- Spend rising while the value it delivers stays flat
What changes
What changes.
TodayWith Dotwork
Spend by account and service
Every cloud dollar with an owner, a product and a capability
Savings identified
Savings tracked from identified to realized — and banked only when the budget moves
Coverage or utilization
Commitments judged on both at once, with the effective savings rate
Bill, invoice and ledger reconciled by hand
Usage to billed to invoiced to booked, in one chain
Optimization as the goal
Cost judged against the value it delivers
Value, not just savings
Know what the cloud spend is buying — not just what it costs.
Because cloud cost lands in the operating model, every allocated dollar carries the product, capability, project and business unit it serves. See cost per user and per unit of work beside the outcomes that spend is meant to move, follow savings from identified to realized, and count them as banked only when the budget actually comes down.
Where other tools stop
Cloud cost platforms stop at savings. They see the bill but not the business it pays for, so they cannot say whether rising spend is waste or growth.
The FinOps thinking built in
The FinOps framework — carried through to value.
Cloud Spend Optimization runs the practices FinOps teams already follow, and connects them to the finance and value disciplines that decide whether the spend was worth it.
Both commitment denominators
FinOps commitment practice
Coverage asks how much usage is protected; utilization asks how much of the commitment is used. Judge both at once, with the effective savings rate.
Unit economics
FinOps unit economics
Cost per user, per transaction and per million tokens — so spend is judged against the work it does, not the size of the bill.
Showback
FinOps practice
Engineering teams see the cost of what they run, with untagged spend assigned to its likely owner instead of a shared bucket.
FOCUS billing data
FinOps Foundation · FOCUS
Built around the FOCUS specification, so cloud and SaaS billing share one shape and one book with the rest of IT.
Benefits realization
Benefits management practice
Savings move from identified to realized to banked, and estimated savings are never reported as realized ones.
The rooms
The rooms inside Cloud Spend Optimization.
Each room answers one question a leader actually asks, with the view that answers it and the measures that say whether it is working.
A room is a ready-made view that answers one leadership question, built on the same shared data as every other room.
Room 01
See the Cloud Bill
“Where is the cloud money going?”
Spend by service, account, region, team and application, billed or amortized, with the biggest movers, the burn-down against budget and anomalies flagged.
How you know it is working
- Cloud spend with a named owner, up
- Time to explain a month-over-month change, down
Room 02
Confirm the Invoice
“Does the invoice match usage and the ledger?”
The chain from usage to billed to invoiced to booked, with variances by reason and invoices missing a purchase order or not yet booked.
How you know it is working
- Gap between the cloud bill and the ledger, to zero
- Invoices without a purchase order, down
Room 03
Allocate the Cloud
“Who owns each dollar — and what is it for?”
Tag coverage against target, showback by team, cost per user, untagged spend with its likely owner inferred, and cloud cost by product, capability and project.
How you know it is working
- Tag coverage against target, up
- Cloud cost allocated to a product or capability, up
Room 04
Find the Waste
“What can we turn off or shrink?”
Big-and-idle resources first, idle age, rightsizing and storage moves — each with its evidence, owner and approval status.
How you know it is working
- Addressable waste, down
- Idle resources older than 30 days, down
Room 05
Fix the Commitments
“Are we covered — and using what we bought?”
Coverage and utilization side by side, the effective savings rate, unused commitment and agreements expiring inside their notice window.
How you know it is working
- Effective savings rate, up
- Unused commitment, down
Room 06
Act on the Backlog
“Are the savings actually being realized?”
A savings funnel from identified to accepted, in progress and realized, with the realization rate, owners and what is overdue.
How you know it is working
- Realization rate of identified savings, up
- Overdue savings actions, down
Agents and skills
The busywork is automated. The calls stay with your teams.
Dotwork does the matching, flagging and tracking behind the scenes, and Dot answers questions about the cloud bill citing the records behind every figure — always separating estimated savings from realized ones.
Owner Finder
Every billInfers the likely owner of untagged spend from its tagged neighbors and queues it for confirmation.
- What you get
- Untagged spend with a proposed owner
- Where you decide
- The owner confirms, and the tag sticks
Anomaly Watch
Every billFlags spend that jumps well above its recent trend and services that appear for the first time, and sends each one to the backlog.
- What you get
- Anomalies triaged from new to explained
- Where you decide
- Owners explain or act on each one
Waste Finder
ContinuousRanks idle and oversized resources by cost and utilization, with idle age, confidence and a recommended action.
- What you get
- A waste worklist with evidence and owners
- Where you decide
- Owners approve each action
Commitment Advisor
MonthlyReads coverage, utilization and unused commitment together and flags agreements expiring inside their notice window.
- What you get
- Where to buy, exchange or rebalance
- Where you decide
- FinOps and finance decide the purchase
Invoice Tie-Out
Every invoiceFollows each provider’s charges from usage to billed, invoiced and booked, and flags invoices with no purchase order or not yet booked.
- What you get
- A reconciliation per provider, per month
- Where you decide
- Finance resolves each difference
Savings Tracker
ContinuousMoves each opportunity from identified to accepted, in progress and realized, and warns when realization falls behind the estimate.
- What you get
- A realization rate finance can rely on
- Where you decide
- Finance confirms what was realized
Value Linker
Every allocation runCarries each allocated cloud dollar to the product, capability, project and business unit it serves, so cost can be read against value.
- What you get
- Cloud cost by product, capability and project
- Where you decide
- Finance owns the mapping rules
Ask Dot
On requestAnswers questions about the cloud bill in plain language, citing the records behind every number.
- What you get
- Answers you can drill into
- Where you decide
- Read-only — it never changes anything
Use cases
Where FinOps and finance put it to work.
FinOps lead · Engineering leaders
Running the FinOps practice
See the bill, find the waste and work the backlog in one place, with every recommendation backed by its evidence.
- A ranked waste worklist
- Anomalies triaged to explained
FinOps · Finance
Commitment strategy
Decide what to buy, exchange or let expire using coverage and utilization together — before the notice window closes.
- Effective savings rate tracked
- Expiring agreements flagged in time
Engineering leaders · Product owners
Showback to engineering teams
Give each team the cost of what it runs, with untagged spend assigned rather than hidden in a shared bucket.
- Cost by team and application
- Tag coverage against target
IT finance · Accounting
Reconciling cloud to the ledger
Tie usage to the invoice and the invoice to the books, so the cloud number finance reports matches the one engineering sees.
- One reconciliation per provider per month
- Unbooked and no-PO invoices flagged
CTO · Product leaders
Cloud unit economics
Read cost per user and per unit of work by product, and see whether rising spend is growth or waste.
- Cost per user and per unit of work
- Cloud cost by product and capability
CFO · Transformation office
Savings that reach the budget
Follow every saving from identified to realized, and into the transformation plan where it is banked only when the budget comes down.
- A realization rate finance trusts
- Savings banked against the budget
How it compares
Everything a cloud cost platform does — then what the spend is worth.
Cloud cost platforms and provider consoles find savings in the cloud bill. Cloud Spend Optimization does that job, then connects the bill to the business it pays for and to the savings that actually landed.
| Capability | Cloud cost platforms | Provider consoles | Cloud Spend Optimization |
|---|---|---|---|
| Spend by service, account and team | |||
| Waste and rightsizing recommendations | Partly | ||
| Commitment coverage and utilization together | Partly | ||
| Anomaly flags | |||
| 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 cost tied to products, capabilities and projects | Partly | ||
| In the same book as people, software and AI spend | |||
| Spend read against the outcomes it is meant to move |
Value realization
Past optimization: what the spend is actually buying.
Optimization asks how to spend less. Value realization asks whether the spend is worth it. Because cloud cost sits in the operating model, Dotwork can answer both.
Every dollar has a purpose
Allocated cloud cost carries the product, capability, project and business unit it serves.
Cost against the work done
Cost per user and per unit of work, by product — so growth and waste stop looking the same.
Savings proven, not promised
Identified, realized and banked are kept apart. Estimates are never reported as realized savings.
Outcomes, not just invoices
Through Transformation Management, cloud savings and spend roll up to the outcomes and key results they were meant to move.
Who it is for
Who opens it, and what they ask.
CFO
“Which cloud savings actually reached the budget?
CTO
“Is rising cloud spend growth or waste — product by product?
FinOps lead
“Where is the waste, and are our commitments working?
Engineering leader
“What do my team’s services cost, and what should we turn off?
Product owner
“What does my product cost to run per user?
IT finance
“Does the cloud bill match the invoice and the ledger?
What it replaces
Retire the workarounds — on your schedule.
- Standalone cloud cost dashboards, on your schedule
- Tagging spreadsheets
- Savings trackers that never reach the budget
- Manual cloud-to-ledger reconciliations
How it is licensed
Cloud Spend Optimization is licensed within Fund & Optimize, with Cost Allocation included underneath.
Start in IT, one function or a division. Cost Allocation is included automatically with every module.
See pricingMethods and frameworks
Runs the methods you already use.
Dotwork does not ask you to adopt a new method. The frameworks your teams run become views over the same model.
More in Fund & Optimize
Same model. Next question.
Cost Allocation
“Where does the money actually go, and can I trust the number?”
ExploreBudgeting & Forecasting
“Can we still move money before the period closes?”
ExploreAI Token Economics
“What does our AI actually cost — and what did it return?”
ExploreWorkforce & Labor
“Do we have the people we funded?”
ExploreProcurement & Commitments
“What did we buy, and is it used?”
ExploreFacilities & Real Estate
“Is our space worth what we pay for it?”
ExploreThe model underneath
Every module makes the next one smarter
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 ModelBe Decisive.Build Fast.Connect Everything.
Start ConnectingSolutions
Platform
Resources
© 2025-2026 Dotwork, Inc. All rights reserved.