Cost optimisation
FinOps practice, right-sizing, and commitment strategy across your AWS estate — with the tagging and allocation to keep the savings from quietly eroding.
Typical scope
2–6 wks
From spend analysis to a savings plan your team can run.
- Basis
- Fixed fee or share of saving
- Output
- Savings plan + practice
- Includes
- Tagging strategy
What we deliver
Savings that persist.
A one-off clean-up drifts back within two quarters. The deliverable is a practice — allocation, review cadence, and ownership — as much as the immediate cut.
Right-sizing
Instance, storage, and database sizing against observed utilisation.
Commitment strategy
Savings Plans and reserved capacity modelled on real usage curves.
Tagging & allocation
Cost attributed to teams and products so waste has an owner.
Waste elimination
Orphaned volumes, idle environments, and forgotten NAT gateways.
Review cadence
A monthly FinOps rhythm your team runs after we leave.
How it runs
Cut, then hold the line.
Quick wins in the first fortnight fund the engagement. The practice we leave behind is what keeps the number down.
Analyse
Spend broken down by service, account, and workload.
Quick wins
Waste and obvious right-sizing actioned in the first two weeks.
Commit
Savings Plans and reservations purchased against modelled usage.
Institutionalise
Tagging, dashboards, and a review cadence handed to your team.
Technology
What we build it on.
- Cost Explorer
- Compute Optimizer
- Budgets
- CUR
- Trusted Advisor
- Savings Plans
Cost & AWS pricing
Fixed fee, or a share of first-year realised savings where you would rather tie our fee to the outcome. The AWS tooling involved is free; the modelling is the work.
See funded AWS programmesNext step
Find out what you are overspending.
Discovery comes first — a short, bounded review that ends in an architecture, a scope, and a price. You keep the output either way.