Cloud / Cloud cost review

Cloud cost review with a prioritised savings ledger.

The bill went up and nobody can say why. We produce a ledger your team can work through.

The trigger

When teams ask for this review.

The bill jumped, or the board asked about gross margin and the answer took three days to assemble.

Included

What the review covers

  • Rightsizing and idle or orphaned resources.
  • Commitment coverage: savings plans and reserved instances.
  • Storage tiering and lifecycle rules.
  • Data transfer, NAT and cross-zone traffic.
  • Tagging, allocation and environment sprawl.
  • Kubernetes cluster health, node sizing and idle workloads.
Excluded

What it does not cover

  • Implementing the changes unless scoped.
  • Ongoing cost operation.
  • Licence renegotiation with your vendor.
The deliverable

What you get

A cost ledger. Every line carries a monthly value, an effort estimate and an owner. It becomes your tracking document.

Failure modes

What usually goes wrong.

  • Commitments bought before rightsizing, locking in the waste.
  • Savings counted before the next bill verifies them.
  • The ledger owned by nobody once the review ends.
  • Non-production environments running a production shape.
Instant quote

Get an instant quote in 2 minutes

Answer four questions. The indicative price updates as you go. Prices are ex GST.

Indicative until we confirm scope in writing, within one business day. We use your details only to reply. See our Privacy notice.

Questions before you book

Practical answers.

How much does a cloud cost review cost?

From A$5,500 ex GST for one AWS, Azure or Google Cloud organisation over four working days. Larger monthly spend or more Kubernetes clusters give an indicative range. The price is fixed once scope is agreed, in writing, before we start.

Do you take a percentage of savings?

No. The review is a fixed scope agreed before it starts.

Will you turn things off?

Not without you. The review produces the ledger. Implementation is a separate agreed scope.

How long does it take?

Two to three weeks for most estates, including the billing export analysis.

What do you need?

Read-only billing and resource access, the tagging convention, and the names of the environments.

Cost and design are usually the same conversation. A bill that grew without a feature shipping is often an architecture problem, which is what a cloud architecture review is for, and a cloud security review covers the case where the spend went on controls nobody can evidence. We hold no reseller margin on any of it, and the about page explains why that is deliberate.

Let’s scope it

Ready to scope this review?

Send the accounts in scope and what prompted the question. We will confirm scope and fee first.

Request a quote

Last reviewed: