Your cloud bill is 20–40% too high. We'll prove it in two weeks.
AWS, Azure or Google Cloud: a fixed-price assessment that ends with a ranked savings list — € figure per finding, effort per fix, risk per change. Implement it yourself, or have us do it for a fixed price or a share of the savings we actually deliver.
Why bills bloat
- Nobody owns the bill. Engineers optimize for shipping, finance sees one line item, and the gap between them compounds monthly.
- Defaults are expensive. On-demand pricing, gp2 volumes, unbounded log retention, NAT gateways moving terabytes — every cloud's defaults are designed for convenience, not your margin. We've seen a single logging misconfiguration produce a $50K CloudWatch bill.
- Savings decay. Even well-optimized estates re-bloat in ~9 months without governance: new services launch on-demand, commitments expire, tags rot.
What the assessment covers
Compute & rightsizing
EC2/RDS/Fargate utilization vs provisioned, Graviton candidates, spot opportunities, idle and zombie resources with owners identified.
Commitment strategy
Savings Plans vs Reserved Instances modelling on AWS (reservations and committed-use discounts on Azure/GCP) against your actual usage curves — coverage targets, terms, and the renewal calendar to govern them.
Storage & transfer
S3 lifecycle and storage-class analysis, EBS/snapshot hygiene, CloudWatch log retention, NAT and cross-AZ data-transfer anatomy.
Governance
Tagging and cost-allocation model, budgets and anomaly alerts configured, per-team/per-customer visibility for SaaS unit economics.
Pricing
| Engagement | Price | Timeline |
|---|---|---|
| Cost Assessment — ranked findings with € figures | €5,000 fixed (credited if implementation proceeds) | 2 weeks |
| Implementation — we execute the findings | €10,000–25,000 fixed, scoped from the assessment | 2–6 weeks |
| Gain-share alternative | 25% of realized first-year savings, capped at €60,000 | 2–6 weeks |
| Continuous FinOps — governance so savings stick | Included in Managed Services Growth and Enterprise plans | Ongoing |
Coverage
AWS is our deepest practice — hence the published methodology and pricing on this page. Azure and Google Cloud run the same playbook: same senior engineers, same assessment method, fixed pricing scoped to your environment. On-prem and hybrid estates (VMware, Proxmox, bare metal) are covered under the same discipline. Tell us what you run →
Frequently asked questions
What if you don't find meaningful savings?
In estates spending $5K+/month that haven't had a structured review in the last year, we have never failed to find material savings — the 20–40% range is what unreviewed estates typically yield. If we ever found less than the assessment fee in annualized savings, we'd say so in week one and stop the clock.
What access do you need?
Read-only: billing data and read access to the resources being analyzed — on AWS that means Cost Explorer and the CUR; Azure and Google Cloud use their equivalent cost exports. No write access is required for the assessment.
How does the gain-share option work?
We implement the findings; savings are measured against your trailing 3-month baseline, normalized for usage growth, and we invoice 25% of realized first-year savings — capped at €60,000. Your incentive and ours point the same direction: real, sustained reduction.
Will optimization break things?
Every change ships with a risk rating, a test plan and a rollback. High-risk changes (instance family moves, storage class transitions on hot data) are staged and monitored. Cost work should be boring — that's the point.
Why do savings decay, and what stops it?
New workloads launch on-demand, commitments expire unnoticed, tags rot, teams change. Governance stops it: budgets, anomaly alerts, tagging enforcement and a monthly review. That's the FinOps module of our managed service — the assessment tells you if you need it.