Start with no upfront cost.
You pay only if we reduce your cloud bill. The fee is the first two months of those savings, verified against your own billing data. No savings, no fee.
-
We find the savings. Your team approves and ships the changes.
-
You pay two months of what was saved. Measured on your invoice, not a projection.
-
From then on, the savings are yours. Continue with us from £1,500 a month, or walk away.
How the fee works
checkout-vm1 is an m6i.2xlarge (8 vCPU, 32 GB). CPU has stayed below 20 percent for the last month. Recommendation: move to m6i.xlarge as a first step.
3-months Premium FinOps on us.
Worth £10,500
Take the success fee engagement and the first three months of FinOps as a Service Premium come with it. Nothing to add to the contract, nothing to pay for separately. The savings work and the service run alongside each other from day one.
After month three, choose your level.
You choose. No default, no pressure.
Prefer a fixed fee?
Some teams would rather know the number up front than share the savings. That route is open, on the terms below.
- No success fee. A fixed fee instead of a share of realised savings.
- 12-month term. Agreed at the start, with the scope set alongside it.
- Environments up to £150,000 a month. Above that, the numbers are specific enough that we quote them.
- 60-day exit clause. Either side can give notice. No penalty attached.
- 10 percent off paid annually. Applied when the year is settled up front.
Read-only. Infrastructure and billing only. Nothing proprietary.
What we access.
Read-only visibility into infrastructure and billing. The metadata that describes how resources are configured and what they cost. Nothing more.
What we never touch.
Your application data. Your databases. Your source code. Your customer records. None of it is in scope, and the access we use cannot reach it. The analysis works entirely from configuration and billing signals.
The questions that come up most.
Most of it never needs the code. The billing and infrastructure data already show the shape of the problem. A resource running more than it needs to, a database where storage dwarfs compute, traffic that points to a missing cache. The cause is usually visible in those signals long before anyone opens a file.
Where a finding genuinely points into the code or a query, we say so and ask first. Nothing at that level happens without your approval, and most engagements never get there.
Two ways it matters, and we account for both.
In the analysis, we size to the workload's real pattern, not a quiet week. Rightsizing reads the peaks as well as the troughs, so nothing is tuned for a lull and then strained at the next peak.
In the verification, seasonality is part of why savings are measured against your billing rather than a projection. We compare like for like and separate a genuine saving from a shift in demand. If spend falls because a change we made took effect, it counts. If it falls because it was a quiet month, it does not.
Yes, and we would expect to. Every environment has accounts that should sit outside the analysis. Legacy, mid-migration, sandbox.
We agree the exclusion list with you in the first call, before anything is counted. Those accounts are excluded from the analysis and from the savings figure, so a migration winding down on its own is never mistaken for a saving you pay against.
Pick the next step that fits where you are.
Book a discovery call.
A 30-minute technical conversation. We look at the shape of your environment, agree the exclusion list, and tell you whether there is opportunity worth pursuing. No obligation to proceed.
See the findings format.
Walk through an anonymised engagement end-to-end. The architectural root cause, not just the dollar number. Useful if you want to see the depth before a conversation.
View a worked example →Start with the structure.
Not ready to talk. Our Cloud Organisation Guide covers the structural thinking. Free, no access required.
Get the guide →