- Bill analysis
- Right-sizing
- Reserved commitments
- Monthly reporting
The cloud bill keeps rising and nobody knows exactly why: instances sized for a peak from two years ago, orphaned volumes and snapshots, test environments running overnight and at weekends. The cloud is pay-per-use, but you still have to know what you consume and decide what you keep.
We start by reading your bills and your console, derive a costed roadmap, then pull the levers and track the result every month. The target we set ourselves: a 15 to 25% cut in the bill, with savings that cover the cost of the engagement from the first months.
What it changes for you
Visibility
A detailed analysis of your bills that names every cost item and the charges nothing justifies.
Immediate savings
The first savings show up as early as the pre-audit: actions you can apply without waiting for a project.
An engagement that pays for itself
The model aims to cover its own cost: no hidden fees, you pay for measured value.
Long-term follow-up
A monthly report on interventions and cloud health: the gains are verified, month after month.
The levers we pull
Size precisely
Right-sizing aligns each instance with its actual consumption rather than an initial estimate: it is the first lever, with 20 to 30% savings on the resources concerned. Containerisation and fine-grained scaling extend the effect by densifying compute.
Commit wisely
For stable workloads, reserved instances and one- or three-year Savings Plans cut compute costs by 40 to 60%. We identify eligible resources and calibrate the commitment so you do not pay for unused capacity.
Switch off and clean up
Non-production environments shut down overnight and at weekends. Orphaned volumes, forgotten snapshots and unused IP addresses are cleaned up automatically, and storage moves to classes suited to access frequency (S3 Intelligent-Tiering, Glacier). Savings without touching the application.
Steer over time
The FinOps roadmap lists the levers with their financial projections. Integrated into managed operations, optimisation becomes continuous rather than one-off: each monthly report revisits the gap between forecast and actual.
Why CAPCOD?
- Transparent pricing: a fixed-price or monthly model depending on scope, with no long-term commitment, designed to be covered by the savings.
- FinOps is not a silo: the same teams do the audit, the migration and the operations, so every recommendation is actionable.
- Cloud & DevOps experts: since 2015 we have been operating the platforms we optimise ourselves.
