Cloud cost optimization that shows where the bill goes and what each fix is worth
Cloud cost optimization is the work of finding what your cloud bill pays for, removing what is not needed and buying the remainder at a lower rate. Goldenroz delivers it as a fixed-price review followed by implementation phases, led by Shai, our CTO. Projects are scoped after a free one-hour call and start at $25,000 at a fixed price per phase, with no fee based on a percentage of savings.
From $25,000, fixed price per phase
Updated 2026-11-14. By Shai Goldenberg
What usually goes wrong
- The bill grew faster than usageCustomers and traffic rose modestly and the invoice rose much more. Nobody can point to the decision that caused it.
- No tags, no ownersResources carry no team or product tag. Finance sees the total and engineering cannot explain a single line.
- Commitments bought on the wrong baselineA one-year or three-year commitment was purchased before right-sizing and now covers instances the team wants to shut down.
- Non-production running all weekendStaging, QA and demo environments run at full size through nights and weekends when nobody uses them.
- Monitoring that rivals computeDebug-level logs and high-cardinality metrics are ingested and stored without limit, and observability becomes one of the largest lines on the bill.
What is included
- Bill breakdownTwelve months of billing data grouped by service, environment and team, with the largest and fastest-growing lines explained in plain language.
- Right-sizing listCompute and database instances compared against measured utilization, with a proposed size and the risk of each change.
- Idle and orphaned resourcesUnattached disks, old snapshots, unused addresses, forgotten load balancers and test environments, listed with owner and monthly cost.
- Storage and data transferLifecycle rules, storage tiers, log retention and the network paths that generate transfer charges.
- Commitment planA recommendation on reserved capacity or savings plans, sized to the baseline that remains after cleanup.
- Tagging, budgets and alertsA tagging standard, budgets per team and anomaly alerts, so the next increase is noticed in days.
AWS cost optimization: where the money usually goes
AWS cost optimization tends to find the same categories. Compute sized for a launch peak. Volumes and snapshots left behind by deleted instances. NAT gateways processing traffic that could use a private endpoint. Object storage with no lifecycle rule. Logs kept at full detail forever. None of these needs a redesign, and each can be priced from the billing data before anything changes.
Larger changes come second: moving to newer instance families, changing a database tier, or replacing an always-on service with one billed per request. Each carries engineering risk, so each is listed with its estimated monthly effect and the work required. The same method applies to Azure and Google Cloud invoices. We do not claim a record of past savings on any platform, and we do not quote a percentage before the review.
FinOps consulting: keep the bill down after the cleanup
A cleanup without ownership does not last. FinOps consulting sets up the routine that keeps cost visible: every resource tagged to a team, a monthly review where engineering and finance read the same report, budgets with alerts, and a rule that new services ship with a cost estimate.
Cloud cost optimization services from Goldenroz end with that routine written down and handed to your team. If you prefer the monthly review to be run for you, it is part of the retainer described under managed IT services. Cost work that needs pipeline or architecture changes is delivered through DevOps consulting.
One plain note on fit. If your annual cloud spend is small next to the price of the project, the review will not pay for itself, and Shai will tell you that on the scoping call.
How the work runs
Scoping call
Before the projectA free one-hour call with Shai about how you release today, what has broken, and what you want to stop worrying about.
Delivery review
Week 1We read the repository, the pipeline, the environments and recent incidents, and write a ranked list of changes with a fixed price.
Pipeline and environments
First phaseCI checks, staging and production separation and automated deploys. The team starts releasing through the pipeline during this phase.
Observability and guardrails
Second phaseAlerts, dashboards, scheduled probes and review hooks, tuned so that an alert means something.
Handover
Final weekRunbooks, a recorded walkthrough and a session where your engineers run a release and a rollback themselves.
What it costs
Each phase has a fixed scope and price, agreed after the delivery review. Cloud, hosting and tool subscriptions are paid directly by you.
- CI/CD, environments and observability projectFixed price per phaseFrom $25,000
- Kubernetes, cloud migration or cloud cost workFixed price per phase after a review, from $25,000Scoped per project
- Larger platform programsSeveral phases$100,000 and up
- Scoping callOne hour with Shai$0
Who it is not for
- Organizations whose annual cloud spend is small next to a $25,000 project.
- Buyers who want a contingency fee tied to savings.
- Vendor contract negotiation or cloud credit resale. You buy from the provider directly.
Who does the work
Shai leads the technology side: business software, SaaS and mobile apps, payments and escrow systems, Postgres security, AI agents built with Claude Code and MCP, and IT and infrastructure projects with senior infrastructure engineers.
Questions buyers ask
What do cloud cost optimization services include?
At Goldenroz they include a breakdown of twelve months of billing data, a right-sizing list, an inventory of idle resources, a storage and data transfer review, a commitment plan and a tagging and budget standard. Implementation of the agreed changes is a further fixed-price phase.
How much does cloud cost optimization cost?
Projects start at $25,000 at a fixed price per phase, quoted after a free one-hour scoping call. We do not charge a percentage of savings and we do not bill by the hour. See pricing for how phases work.
How much will we save?
We cannot say before reading the billing data, and we will not give a figure to win the project. After the review, every finding has an estimated monthly effect, so you can decide which changes are worth the engineering time.
Is AWS cost optimization worth it for a small account?
Usually not as a paid project. With a modest monthly bill, the free tools in the AWS console and an afternoon of cleanup by your own engineers cover most of the gain. A fixed-price review makes sense when the annual spend is several times the project price.
Will the changes cause downtime?
Deleting idle resources and adding lifecycle rules does not. Resizing instances and changing database tiers can require a restart, so those changes are scheduled in maintenance windows and tested on staging first. Each item on the list states its risk.
Guides on this topic
- Kubernetes solves real problems for teams with many services and uneven load. Use this eight-question test to see if you need it, and what to run if you do not.
- A cloud cost optimization checklist in the order that works: see the bill by owner, remove idle resources, right-size, fix storage and transfer, then commit.
- Compare the four ways to modernize a legacy system: rehost, refactor, rebuild or replace. See what each fixes, what it leaves, and how to migrate in phases.
Talk to the person who will do the work
One hour, no sales team. You talk to Shai Goldenberg, the CTO, about your systems or your product, and you leave with a clear next step and a price range.