Cloud Cost Optimisation
Find the 25–40% you didn't know you were spending. Lock it in. Build the discipline so it doesn't come back.
- Quick-win savings within 30 days, no architecture risk
- Tagging, budgets, and alerts that survive after I leave
- Savings plans / CUDs structured against stable baseline
Most cloud bills have 25–40% slack. It's not in one place — it's in idle dev environments, oversized RDS instances, NAT gateway egress, log retention nobody picked, GP2 volumes that should be GP3, and snapshots from 2022.
The first 30 days
Audit, prioritise quick wins (no architecture risk), execute, set up tagging and budget alerts, structure your committed-use discount strategy. Most teams see 15–25% off the bill in the first month.
Months 2–3
The structural work: rightsizing pipeline, autoscaling tuning, multi-tenant resource sharing, region/AZ rationalisation, log/metric retention discipline. This is where the next 10–15% comes from — and where it stays gone.
Discipline that lasts
Cost dashboards your engineers actually look at, weekly cost-of-change report, blameless reviews when bills spike. Cost becomes a property of how you build, not a quarterly fire drill.
Talk through cloud cost optimisation.
A 30-minute call to understand the shape, the constraints, and whether I'm the right person for it.