Cloud cost review
What you spend on AWS, Azure or GCP, checked against what you actually run. A ranked list of savings, each with its risk, the effort involved and how to make the change safely.
Where cloud money usually goes
Spend and tagging
Where the money goes by service, environment and team, and whether tags make that visible.
Rightsizing and idle resources
Instances, databases and clusters sized well above what they use, and resources nobody uses.
Commitments
Reserved instances, savings plans and committed-use discounts: what you hold, what you use and what fits.
Storage and lifecycle
Old snapshots, unattached volumes and data that could move to a cheaper storage class.
Data transfer
Egress and cross-region traffic, which is often the line nobody can explain.
Non-production environments
Test and staging running around the clock when they are only used in working hours.
Access, analyse, report, walkthrough
Access
Read-only access to billing and usage data for the accounts in scope.
Analyse
We map spend to what each resource does and find the savings.
Report
Every saving ranked by size, risk and effort, with how to make the change safely.
Walkthrough
We go through the report with your team and agree what to do first.
What you get
- A ranked savings report, with an estimate for each item calculated from your own billing data
- The risk and effort of each change, and which ones need testing first
- A short summary for non-technical readers
- A walkthrough with your team
Not included
- Making the changes, unless agreed as a separate engagement
- Re-architecting applications
- Negotiating prices with your cloud provider
Duration
Agreed at scoping, based on the number of accounts and services in scope.
Price
On request. Fixed and agreed in writing before work starts.
Is this the right fit?
Teams whose cloud bill has grown faster than the product, companies preparing a budget, and anyone who suspects they pay for more than they run. For ongoing work, see Cloud & DevOps.
Common questions about the cloud cost review
What access do you need?
Read-only access to billing and usage data for the accounts in scope, such as AWS Cost Explorer and the cost and usage report, Azure Cost Management or the GCP billing export, plus read-only access to see what each resource is.
Will the changes put our uptime at risk?
The review itself changes nothing. In the report, each saving carries its risk and whether it needs testing first, so you can start with the safe ones.
Do you guarantee a saving?
No. Each saving is estimated from your own billing data, and the report shows how. We don’t promise a figure before we have looked.
Which clouds do you cover?
AWS, Azure and Google Cloud, including businesses that use more than one.
Can you make the changes for us?
Yes, as a separate engagement scoped after the review, or your team can make them using the report.
Start with last month’s bill
Tell us which clouds you use and roughly what you spend. We’ll tell you whether a review is worth it, and if your setup is already lean, we’ll say that.