For agencies & dev shops
AWS cost optimisation for agencies and software consultancies
Agency AWS accounts have a failure mode all their own: infrastructure outlives the project that paid for it. Every finished engagement risks leaving instances, databases and storage behind — billed to you, benefiting no one.
The free scan inventories every region and flags resources with no recent activity — the ghost projects show up immediately.
Run the free scanWhere agency AWS bills leak
- →Ghost projects. The client signed off in 2024; their staging environment is still running. Project-end checklists rarely include "destroy the infrastructure" — and touching old client resources feels risky, so nobody does. The meter keeps running.
- →Demo and pitch environments. Spun up to win the work, forgotten after the decision. A handful of demo stacks at £50–150/month each is a real number by year end — for environments nobody has opened since the pitch.
- →One account, no cost allocation. Everything in one AWS account with no tagging means no idea which client, which project, which team. You cannot bill it back, and you cannot see waste when every cost is anonymous.
- →Hosting drift. Client sites hosted "temporarily" during a build that became permanent, running on oversized instances sized in a hurry. Recurring hosting revenue is great — unless the infrastructure was never rightsized and the margin quietly went to AWS.
- →Duplicate tooling per project. Each project team spun up its own CI, monitoring and bastion hosts. Five projects, five sets of shared services. Consolidation is boring and saves hundreds a month.
Put numbers on it
Is my AWS bill too high?
Benchmark your spend against typical ranges for your team size in 30 seconds.
Open calculator →
EC2 idle cost estimator
What your under-5%-CPU instances cost, and what rightsizing the quiet ones saves.
Open calculator →
EBS snapshot cost estimator
Snapshots accumulate forever by default. Price your backup graveyard.
Open calculator →
Frequently asked questions
Can you audit an account with live client workloads safely?
Yes — the scan is read-only by construction (a CloudFormation role with ReadOnlyAccess you create and delete). Nothing is modified. The audit report lists findings per resource with evidence, so you decide what belongs to a live client and what is genuinely dead.
We bill some AWS costs back to clients. Does optimisation still help?
More, not less: cost allocation (tagging) is usually finding #1 for agencies — it turns the bill from one anonymous number into per-client lines. Waste you cannot bill back stops being invisible, and pass-through costs become defensible to clients.
£499 fixed. Free scan first. 20%+ found or it’s free.
The scan is read-only — a role you create and delete, no keys shared — and shows your estimated monthly saving before anyone talks about money.