Services

AI and Automation

Spend optimisation

Supplier contractsCloud billsSoftware subscriptionsData platformsMonitoring tools

Practice

All servicesHow it worksAbout
Get in touch

Cloud

Cloud bills

AWS, Azure and Google Cloud. We work out what you are paying for, set it against what is actually running and being used, and put a dollar figure on the difference.

What we look at

Five things, each one measured.

  • Commitments and reserved capacityDiscounts you have committed to, set against a year of real usage — including the ones you over-bought and are now paying to waste.
  • Things running that nobody needsServers, databases and load balancers sitting well below what they are sized for, with the measurement and the time period stated so you can check the reasoning.
  • Storage in the wrong placeData sitting in faster, dearer storage than it needs, and backups with no deletion rule behind them quietly piling up for years.
  • What data movement is costingTraffic between zones, between regions and out to the internet, traced back to the service causing it. This is usually where the surprise is, because it rarely shows on a dashboard.
  • Kubernetes asking for more than it usesWhat workloads ask for against what they actually use, plus machines that exist only to satisfy requests nothing is touching.

What you get

A document, not a dashboard.

  • A ranked list of findings, each with what it costs now, what it would cost after the change, roughly how many hours that takes and what could go wrong.
  • The evidence behind every finding — the measure, the period, the source.
  • A section naming what to leave alone, and why.
  • Every read-only role we used, listed, so you can check afterwards.
  • An hour with whoever has to do the work, to walk through it.

What is not included

Said up front, not found out later.

  • Comparing your rates against what other customers pay — that needs pricing data we do not have.
  • Rewriting your applications. Where a finding would need that, we say so and stop there.
  • Changing anything while we review. It is read-only from start to finish.

If something you need sits outside this, say so when you get in touch. Better to find out now than to read it as a limitation in the report.

Questions

About this one specifically.

Do you need access to our production systems?

We need to read billing and usage data, and to see how things are set up. That is all. The access we use cannot start, stop, resize or delete anything, and you create it yourself inside your own account.

We already have a cost tool. What would you add?

Tools show you where the money goes. They rarely tell you which of it is safe to stop spending, what the change costs in engineering time, or what breaks if you get it wrong. That judgement is what you are paying for here.

Start with the bill

Send us last month’s cloud bill. We will tell you what stands out.

You do not need to tidy anything up first, and you do not need to know where the problem is. A read-only look at one month of spend is usually enough to see where the money is going.