Keeping cloud costs under control after migration

The migration went beautifully — then the first quarterly bill arrived and someone spilled coffee. Cloud waste is almost never fraud or failure; it is oversized machines, forgotten test environments, and nobody watching the meter. Here's the routine we install for every client.

Rightsize first

Migrations lift-and-shift generously, which is correct at cutover and wasteful by month three. Review actual CPU, memory and disk usage after 30 days and step oversized resources down. This single pass usually saves the most.

Reserve what is steady

Workloads that run 24/7 — domain controllers, databases, core apps — should sit on one- or three-year reserved capacity, not pay-as-you-go rates. The discount is substantial and the commitment is smaller than it looks.

Delete the forgotten

Unattached disks, old snapshots, idle test servers: tag everything with an owner and an expiry date, then run a monthly cleanup. What nobody claims gets snapshotted and switched off.

Set a ceiling and an alarm

Agree a monthly budget per workload, alert at 70% and 90%, and review the bill in a 30-minute meeting every month. Visibility alone prevents most drift.

Make it a habit

Cost control is maintenance, not a project. Our cloud care plans include the monthly review, rightsizing passes and tagging discipline — so the bill stays boring forever.