Make cloud and AI spend visible, owned and managed as an operated practice.
iTmethods operates the FinOps work: assessing the estate, finding avoidable cost, planning commitments, implementing approved changes and measuring the result.
Written once, at the boundary.
A billing export answers the finance question; an audit log answers the control question. A joined record answers both for the same event.
Cloud and AI spend grows across accounts, teams and model providers.
Enterprises with growing cloud and AI spend see workloads keep moving while the commitment position stands still. Some spend may be avoidable, and each commitment choice carries a trade-off. The work starts with an assessment of the estate.
Published 18 March 2026 from 753 respondents surveyed in winter 2025. Flexera attributes the rise to cost complexity from AI and new services. Your own number is unknown until somebody looks, and it is usually distributed differently from the average.
That is the FinOps Foundation’s State of FinOps 2026, published 19 February 2026 from 1,192 respondents representing more than $83bn of annual cloud spend, and it names AI cost management the single skillset teams most need to add. Unlike a database, the thing spending the money is making its own decisions about when to.
Find where the spend is coming from, then decide what to change.
iTmethods runs the assessment, maintains the approved optimization and commitment plan, implements the changes and reports the result.
A saving figure quoted before the estate has been examined is a sales tactic rather than an estimate. The assessment reviews billing data, account structure, tags, model usage, commitments and ownership, and expected results are established from the customer’s baseline after the estate is assessed. The assessment →
Material spend is connected to accounts, environments, teams and workloads where the data permits. Where ownership is missing, the assessment says so.
iTmethods implements approved changes under the agreed scope or gives the customer a named-owner action plan, then reports actual usage and cost against the agreed baseline.
iTmethods operates the agreed position. The customer sets the budget rules and risk appetite, decides which commitment changes to make and can see what is committed, what is covered and what it costs.
Cloud and AI cost as an operated practice.
Visibility, right-sizing and commitment strategy, run as an operated practice rather than handed to you as a tool and a login.
| What | How it is run |
|---|---|
| Visibility | Unified spend across the estate, attributed to teams, accounts and workloads where the data permits. Where ownership is unclear, finding it is part of the work. |
| Right-sizing | Idle resources and oversized instances found and fixed as a continuing practice rather than an annual cleanup project somebody volunteers for. |
| Commitment strategy | Budget rules and the commitment position run by an operator rather than maintained in a spreadsheet by whoever last had time. |
| The insurance layer | Delivered with Archera, which supplies its guaranteed-commitment product under Archera’s terms. iTmethods assesses suitability against the customer’s actual usage and operates the agreed commitment position. About the partnership → |
Connect spend to the work that drives it.
Reign Ops brings cloud costs and model consumption into one operating view; for AI workloads, records can show the calling identity, model used and cost, helping teams investigate consumption and apply budgets and policy.
We manage the work. You keep the decisions.
The operating plan defines what iTmethods can change and what needs your approval.
| Who | What they do |
|---|---|
| iTmethods | Assess usage and cost, maintain visibility and attribution, recommend actions, and implement approved changes. |
| Your teams | Set budgets and risk tolerance, provide workload context, and approve changes to capacity or commitments. |
FAQ
How does Archera fit?
What is required to start?
How are savings estimated?
Do you use our figures or yours?
Which deployment options are available?
How is pricing set?
Start with the bills and the ownership map.
Bring the current cloud and model spend, account structure, existing commitments and the teams that own the workloads. Use the conversation to discuss attribution, possible changes and where better data may be needed.