Give every bill line a workload and an owner
Consider an online store with a monthly cloud bill of HK$12,000. Split the bill by workload before changing machine sizes. A database used by checkout needs a different review from a staging environment left running overnight. The amounts below are invented to demonstrate an audit, not provider prices or an expected saving.
| Workload | Current | Trial budget | Evidence before changing |
|---|---|---|---|
| Application compute | 4,200 | 3,000 | Peak traffic, latency and memory |
| Database | 3,600 | 3,600 | Keep capacity until query and I/O review |
| Storage and logs | 1,800 | 1,400 | Retention owner and restore test |
| Network transfer | 1,200 | 1,000 | Traffic destinations and cache behaviour |
| Staging | 1,200 | 400 | Team usage window and restart test |
Measure both the bill and the unit cost
HKD per month · zero baseline
Illustrative targets only. Baseline HK$12,000; trial HK$9,400. Validate actual usage and service quality before calling the HK$2,600 difference a saving.
View data table
| Workload | Baseline | Trial |
|---|---|---|
| Compute | 4200 | 3000 |
| Database | 3600 | 3600 |
| Storage | 1800 | 1400 |
| Network | 1200 | 1000 |
| Staging | 1200 | 400 |
At 6,000 completed orders, the baseline is HK$2.00 per order. If the trial also completes 6,000 orders, HK$9,400 is about HK$1.57 per order. But if orders fall to 4,000, the same HK$9,400 bill is HK$2.35 per order. A smaller bill can hide worse efficiency. Use the same reporting period and include failed orders in your reliability review.
Change one workload and keep a way back
Schedule non-production first
Agree when staging is needed, automate its shutdown and test its restart before relying on the schedule. Exclude systems required by customers or overnight jobs.
Test one capacity change
Keep the original configuration. Compare peak-period latency, errors and queue length after the change; revert if agreed service limits are breached.
Review the next complete bill
Reconcile observed charges with the estimate, then decide whether longer-term commitments make sense for the remaining steady workload.
Before you proceed
- Identify the owner of every significant recurring cost.
- Test changes across peak and normal usage.
- Include restoration and monitoring in cost reviews.
