- Industry
- IT Company
- Department
- Engineering
- Team
- Platform and Reliability
- Kind
- Decision-maker
- Approver
- Head of Service Delivery
- Code
- ENG-13
It finds wasted cloud spend on the SaaS platform and in managed-services client accounts (idle and oversized resources, unattached storage, untagged spend and commitments that no longer fit usage) and estimates the saving in USD per month. It proposes which savings to act on, protecting the project margin on fixed-fee managed contracts, and acts only where the client contract lets the company change resources.
How it works
7 steps, and a person signs off before step 7.
- 01Looks it up
Finds the record the request is about in the cloud monitoring and observability stack: cost, utilisation and tags per resource for the accounts named over the lookback..
- 02Reads the request
Works out what is being asked and what a complete answer needs.
- 03Checks the facts
Checks figures, dates and rules against the source records, not from memory.
- 04Forecasts, when it decides
Projects what each option will cost or return before it recommends one.
- 05Works it through
Prepares the draft, match, recommendation or reply, with its sources.
- 06Asks a person
Hands the work to Head of Service Delivery with its reasoning before anything goes out.
- 07Acts
Once approved, it acts in the ticketing and service management system: it raises the change for each approved saving and records the saving. and records what was done.
What it works with
Your knowledge, your systems, your people.
Knows
The FinOps policy: idle and rightsizing thresholds, commitment rules, who owns savings under each managed-services contract, protected tags and how cloud cost is passed through to clients.
Reads from
the cloud monitoring and observability stack: cost, utilisation and tags per resource for the accounts named over the lookback.
Acts in
the ticketing and service management system: it raises the change for each approved saving and records the saving.
Hands back
A list of savings, each with resource, account_ref, kind, action (stop, resize, delete, commit or recommend), saving_usd_per_month, margin_effect (ours or client) and risk.
Asks a person when
A saving touches production, a client account, or a commitment purchase.
Settings
Your limits, set by your managers.
| Setting | Default | What it controls |
|---|---|---|
| Idle below CPU (%) | 5 | Resources averaging below this are idle. |
| Least saving worth acting on (USD per month) | 100 | Smaller savings are listed only. |
| May act by itself on | non_production_only | Where it may stop or resize resources itself. |
| Longest commitment (years) | 1 | Commitments longer than this are never proposed. |
| Protected tags | do-not-stop, production-critical, client-owned | Comma-separated tags that are never touched. |
Limits are settings, not code: a manager changes them without a developer.
Rules it always follows
- Call a resource idle below 5 percent CPU over the lookback.
- Act only on savings of 100 USD a month or more, and only within non_production_only.
- Never touch resources tagged do-not-stop, production-critical, client-owned.
- Change a client's resources only where their managed-services contract lets the company do so; for pass-through accounts recommend to the client instead.
- Propose commitments no longer than 1 years and only against a client contract term that covers them.
See the Cloud Cost Agent agent on your own work.
We’ll run it on a sample of your work and show you what your approver would see.