- Challenge
- The cloud bill was rising faster than traffic, and nobody could say which product was responsible.
- Approach
- We tagged and attributed spend by team, removed idle resources, rightsized compute and databases, and set up commitments for the steady load.
- Stack
- AWS Cost Explorer · Savings Plans · tagging
- Result
- A lower bill, a monthly cost report per team, and budgets that engineering leads own.
Cost optimisation (FinOps)
A smaller cloud bill, and a team that knows what it’s paying for.
Talk to an engineerWhat we do
Cost optimisation consultancy
A bill review with itemised savings, ranked by effort.
Cost optimisation delivery
Rightsizing, commitments and clean-up, applied with your team.
Cost optimisation support
Monthly cost reporting and a watch on new spend.
Cost optimisation training
Tagging, ownership and budgeting practice for engineering leads.
Where the money usually is
| Before review | After review | |
|---|---|---|
| Compute | 92% | 58% |
| Databases | 64% | 46% |
| Storage | 48% | 30% |
| Data transfer | 36% | 24% |
| Idle & unowned | 30% | 4% |
Tools we work with
Visibility
- AWS Cost Explorer
- AWS Cost and Usage Report
- Azure Cost Management
- Google Cloud Billing
- BigQuery billing export
Kubernetes cost
- Kubecost
- OpenCost
Commitments
- Savings Plans
- Reserved Instances
- Azure Reservations
- Committed Use Discounts
Rightsizing & scheduling
- AWS Compute Optimizer
- Azure Advisor
- Recommender
- Karpenter
- Spot Instances
Guardrails
- Budgets and alerts
- tagging policies
- Infracost
How an engagement runs
- 1 A call. 30 minutes with an engineer to understand the problem.
- 2 A look. Read-only access or a walkthrough, so we scope from facts.
- 3 A proposal. Scope, deliverables and a price model: fixed scope, day rate or retainer.
- 4 The work. In your accounts and repositories, alongside your team.
- 5 A handover. Documentation and a session with your team, so you’re not dependent on us.
Proof
A recent Cost optimisation (FinOps) engagement. We keep client names private, but the problem, the work and the outcome are exactly as they happened.
See our workQuestions
Do you work in our accounts or yours?
Yours. Everything we build lives in your cloud accounts and repositories from day one, so there is nothing to migrate when we finish.
Can you work alongside our own team?
Yes, and we prefer it. We can run a project ourselves, embed engineers in your team, or pair with your people so they pick it up as we go.
How is this priced?
Depending on the work: a fixed-scope price, a day rate or a monthly retainer. We agree it in a written proposal before anything starts.