Analysis / R&D and engineering
Review cloud cost reduction candidates safely
Which cloud resources deserve a cost reduction review? Inspect permitted billing data, reporting limits and a reusable review method in Proforma.
Engineering and operations lead · Finance reviewer
Bring this question into Chat
Your starting prompt.
Review cost-reduction candidates in [Google Cloud project] using resource costs, observed configuration, available utilization and owner records. Keep [core site and database] protected. Separate Keep, Investigate and Proposed change, with dated reasons, dependencies and missing evidence. Explain continuing disk, suspended-memory, networking or retention charges. No requests alone does not mean a resource is unnecessary. Treat savings as estimates until a reviewed change has later billing evidence; do not execute cloud changes.
Copy this starting point, then replace the placeholders with your own inputs.
Method and review
Keep the assumptions visible.
Specify units, calibration, baselines and the experimental method. Check measurement quality and uncertainty before extending a result beyond the observed conditions.
For this task, check
An unused-looking resource can be essential. The analysis Connection does not grant authority to shut down, delete, edit IAM or enforce budgets.
Before you begin
- Permitted inputs covering the listed reporting windows
- Review the Google Cloud setup and supported export coverage
- Review live Connection and Action availability before enabling recurring work
Work with permitted files or queryable data. Verify the result against the original records.
Synthetic illustrative example
See the method in practice.
Synthetic input. Illustrative output checked locally; this is not a live Proforma run or customer result. Low utilization is reviewed alongside purpose and dependency evidence, including a protected core database.
These invented records explain the method. They are not a recorded Proforma run.
| Resource | Monthly cost USD | Observed use | Owner policy |
|---|---|---|---|
| Core database | 45 | 8% CPU | Protected; site depends on it |
| Warm VM | 60 | No requests in observed window | Purpose unconfirmed |
| Old disk | 20 | No current attachment | Retention unconfirmed |
| Resource | Review state | Reason | Next evidence |
|---|---|---|---|
| Core database | Keep | Protected core dependency | Review capacity with owner |
| Warm VM | Investigate | Idle does not prove unnecessary | Owner and dependencies |
| Old disk | Proposed change | Potential retention candidate | Retention approval and restore need |
Method
Apply the protected-resource rule before considering utilization. Record missing owner and retention evidence as unresolved. Configuration suggests continuing charges; these invented costs do not establish the amount that a particular shutdown or deletion would save.
What the result tells you
The core database stays online. The warm VM needs investigation and the disk proposal still needs review. This sample authorizes no cloud mutation and claims no savings; later billing evidence is necessary after an approved change.
Take the next step
Make it your investigation.
Copy the prompt above, create or open your Workspace, and paste it into Chat. Add the inputs you have permission to use and adapt the assumptions with your agent.
Start exploringYour prompt is carried by copy and paste. Signing up does not submit it or start this work automatically.
Start from the reusable template
Inspect the disclosed sample, then sign in and choose Install. Live Google Cloud setup, recipients and schedules require separate review.
Inspect Cloud Cost and ActivityReview Google Cloud setupOr start with your own agent
The setup prompt includes this public task. Your agent will help you connect when needed and use the access you approve.