Cost ownership
Review billing exports, allocation tags, budgets and responsibility for the agreed cloud scope.
Cloud platforms · 01 · The problem and the decision
FinOps reviewWho gets the call when the bill is 20% over?
The cloud bill is growing, but the team cannot explain which changes are driving it. Establish a cost baseline and decide which actions merit investigation or implementation.
For CFOs, CTOs, cloud cost owners and MSPs supporting a growing cloud estate.
2 weeks elapsedAn agreed cloud billing scope and workload sampleA named architect accountable
02 · What we check
Agree the scope. Inspect the evidence.
We agree the billing scope, workload sample and review depth, then separate the measured bill and usage from estimates of what could change. Recommendations name their assumptions and operational tradeoffs.
Usage and demand
Inspect the available utilisation evidence, idle-resource candidates and demand patterns for the agreed workloads.
Options and risks
Compare practical rightsizing, scheduling and commitment options. Record reliability, flexibility and procurement dependencies.
What we need from you
- Billing and usage data for an agreed period, with access to the cost owner.
- An inventory of the accounts and workloads included.
- Known demand patterns, reliability constraints and existing commitments.
Scope and boundaries
- Purchasing commitments, changing resources and guaranteed savings are excluded.
- Additional accounts, deeper application profiling, remediation and detailed implementation-ticket engineering require separate scope.
03 · What you get
A decision you can act on.
- A cost and ownership baseline with missing data identified.
- A ranked action list showing evidence, assumptions, owners and expected tradeoffs.
- A decision summary distinguishing immediate investigations from changes needing workload approval.
- A measurement plan to check any savings after authorised changes.
04 · Relevant work and a sample
See the thinking behind the review.
Evidence before a savings claim
This example shows the intended finding format. It is not a customer case or proof of a measured saving. Client evidence will be added only with supported results and permission.
05 · Duration and price
A defined engagement. An agreed scope.
From €5,000Starting price, excluding VAT
From €5,000, excluding VAT. We quote a fixed fee after agreeing the cloud and account inventory, billing period, workload sample, access and review depth. The two-week elapsed window is confirmed around those inputs. Remediation, detailed implementation-ticket engineering and additional scope are separate.
We agree the included scope, deliverables and fixed fee in the proposal before work starts.
- Duration
- 2 weeks elapsed
- Base scope
- An agreed cloud billing scope and workload sample
- Your data
- Read-only access, in a workspace that holds only your engagement. If your policy requires it, we work with EU-only processing and zero data retention. Any extra cost is named in the proposal.
Our own AI-assisted tooling collects evidence and drafts findings; a named architect checks and signs them. How we work and handle data →
06 · Request a working session
Start with the question you need to resolve.
Use 45 minutes to discuss the cost question, the data available and who owns the affected workloads. Agree whether a focused review can answer it.
This requests a 45-minute conversation. We confirm a suitable time with you.
Do unclear controls and ownership extend beyond cost? Explore the landing-zone assessment.