Job vps-cloud-bill-review-with-specific-changes · revised 11 October 2026
Review one cloud bill and get specific, costed changes to make
One month of one cloud account's bill is read line by line and you receive a ranked list of specific changes, each with the saving worked out from your own figures and the risk of making it.
You might be seeing
- The bill grew and nobody can say which resource caused it
- Servers, volumes and addresses exist that nobody remembers creating
- The cost report shows large totals by service but not by project or environment
No passwords, keys, card details or admin invites needed to start.
What usually happened
A cloud bill is a list of usage lines, not a list of decisions. Some lines belong to resources that nothing uses: a volume left behind when its server was deleted, an address kept allocated, an oversized instance, or a snapshot kept long past its purpose. Others are real and necessary. Deleting the wrong one loses data, and a saving worked out without checking usage can be wrong. Prices and discounts differ by provider and account, so a recommendation needs the actual lines.
Who it’s for: A founder or engineering lead whose monthly cloud bill has grown, who cannot say which line items are needed, and who has nobody with time to go through it.
Usually starts when: A bill that jumped, a budget review, or a new rule that infrastructure cost must be explained to the rest of the company.
The result: You receive a written review of one month of one account's bill: every line item above an agreed threshold is classified as needed, unclear or apparently unused, with the evidence. The changes are ranked by saving and risk, with each saving worked out from the figures in your bill, and the steps to make each change safely. You decide and make the changes.
Check whether this job fits
Four checks that decide whether this fixed job fits. Your answers stay on this page unless you choose to email them.
Checks you can run yourself
Find the top three lines
In your provider's cost explorer or billing console, group last month's cost by service and by usage type. This only reads.
Look for: The three largest services and the usage types inside them. Send the names and amounts, not account identifiers.
What you get
- A line-item classification table with the evidence for each classification
- The ranked change list, each with saving calculation, risk, pre-change check and rollback
- A one-page summary for the budget holder, and what the review could not determine
Included
- One cloud account (or one billing export) and one month of charges, plus the previous month for comparison
- Every line item above a threshold we agree, grouped by service, resource and environment where tags exist
- A review of the resources behind the largest lines using read-only listings that you export or a read-only role that you create and revoke
- A ranked list of up to ten specific changes with the saving worked from your figures, the risk, the check before the change and the way back
Not included
- Making the changes, deleting resources or changing commitments and reserved capacity
- A guaranteed saving, or a comparison of providers
- Multi-account organisations, or more than one month
- Tax, accounting or procurement advice
- Ongoing cost monitoring
How we know it’s done
Agreed with you before work starts. Each check produces evidence you keep.
Every line item above the agreed threshold appears in the classification table with a classification and the evidence for it, and the table total matches the bill total for the month.
Evidence: The table with a reconciliation row showing the table total and the bill total.
Each recommended change states the current monthly cost from the bill, the saving, the assumptions behind it, the risk, a check before the change and the way back.
Evidence: The change list with those fields for each of up to ten items.
Each saving can be recomputed by you from the figures cited, using the arithmetic written beside it.
Evidence: The worked calculation for each change, and your recomputation of two chosen by you.
Resources classed as apparently unused cite the check that showed no use, and none is recommended for deletion without a backup step.
Evidence: The use-check evidence per resource and the backup step per deletion.
The review lists what it could not determine and what extra data would settle it.
Evidence: The limitations section.
Sign-off. You sign off after reconciling the table with your bill, recomputing two of the savings and accepting the limitations. Payment follows sign-off.
If it fails. If the data you supply is too incomplete to reconcile with the bill, we tell you what is missing and you do not pay until the review can be completed. We do not invent figures to fill gaps.
When it fits, and when we stop
It fits when
- You can export the bill, or the cost and usage detail, as a file, or give a read-only role for cost and resource listings that you create and revoke
- Someone can confirm which resources are in use and which environments they belong to
- The account is yours, or you have authority to share its billing data
- You can approve any change yourself or name who can
We stop and tell you if
- You cannot export billing data or grant read-only access to resource listings
- Resources and invoices are held by a reseller and you cannot see the line items
- The review is expected to prove a saving target in advance
- The account contains regulated data that cannot be inspected even as metadata
What could go wrong
The review changes nothing in your account. For each recommended change the document states how to take a snapshot or backup first, how to confirm that nothing uses the resource, and how to restore it if the change was wrong.
Scroll the table sideways to read it all.
| Risk | How we handle it |
|---|---|
| A resource that looks unused is the only copy of data or is used by a task that runs rarely. | Classify it as unclear unless a use check shows no recent activity, and require a snapshot or backup before removal. |
| A saving is overstated because discounts, credits or tax were not reflected. | Use net figures where the export has them, state which figure each saving uses, and label estimates as estimates. |
| A recommended resize degrades the app. | Recommend a measured step with a way back, and say what usage data is missing. |
An independent reviewer checks that each saving is calculated from the bill's own figures, that no deletion is recommended without a use check and a backup step, and that unknowns are stated.
How we deliver
We arrange the work and independent review, then show you the result against the agreed checks. You keep authority over your systems.
- Agree the account, the month, the threshold and the confidentiality of exports in writing
- Load the export and group charges by service, resource type and environment
- Compare the month with the previous one and explain each material increase
- List the resources behind the largest lines and classify each as needed, unclear or apparently unused with evidence
- Work out each saving from the figures in your bill and state the assumptions
- Independent review of every proposed deletion or resizing for data-loss risk, then hand over the review
This is a one-off job, not emergency cover or a subscription. We confirm eligibility, the total price, a start window and a delivery date before you accept. Work starts only after agreed inputs, secure access, any licences and necessary permissions are in place. Hosting, platform and supplier charges are excluded unless the written quote includes them. No charge or booking is created by an enquiry.
Need to keep it working?
If you want the bill reviewed every month, ask us for a quote. This job reviews one month once.
Ongoing work is separately scoped and quoted: no monitoring, response-time guarantee or automatic subscription is included in this job.
Explore an ongoing engineering lane, or mention the responsibility you need in your enquiry.
What you can check
This is a new service. We have not delivered this job for a client yet.
Other ways to get this done
- AWS Cost Explorer shows costs by service, usage type and tag for up to 13 months, and its user interface is free to use; a team can start there. docs.aws.amazon.com
- Your provider's own cost recommendations may flag some idle resources at no charge; check them before paying for a review.
Questions
Will you guarantee a saving?
No. The review shows specific changes with the saving calculated from your bill and the risk of each. Whether you save depends on what you change.
Does this only work for AWS?
The examples use AWS documentation, but the method works from any provider's cost and usage export. Tell us the provider when you enquire.
Will you delete things for me?
No. We never make changes in your account. You make each change with the steps provided.
What if most lines are unclear?
Then the review says what to check for each one, and does not recommend deleting what it cannot show is unused.
Send an enquiry
Send us
- The provider, the month, and the total of the bill
- The three largest services on it, as shown in your billing console
- Any change you know of: a launch, a new environment, a migration
- Do not send credentials, access keys or invoices that show card details in the first enquiry
Later, once you agree
- A cost and usage export for the month and the one before it, with account identifiers you are content to share
- Read-only listings of servers, volumes, addresses and snapshots, or a read-only role you create and revoke
- A named person who can say what each environment and resource is for
- A company-controlled secure handoff agreed before access: no live passwords, keys, private code or customer records by ordinary email.
You own the account and the bill. We work from exports or a read-only role that you create with the least access needed and revoke afterwards, agreed in writing. We never ask for console passwords or access keys in the first enquiry, and we never make changes in your account.
Email fallback: open your mail app
If website submission is unavailable, review and send the fallback email yourself. An email fallback is not a website receipt. Or write to hello@syntheticindustry.ai with “vps-cloud-bill-review-with-specific-changes” as the subject.