Step 1
Agree the rules
We agree what is measured, who approves a change and what must not get worse: each service level and business measure, with its limit. Those limits are the guardrails.
Forward deployed teamForward deployedGovernance reviewGovernanceCost reviewCost
We find the settings that spend compute for nothing, change them one at a time, and count a saving only after we measure it.
What you get
Every change goes through your own change control, with its rollback written first.
By kind of usage and by resource.
Each one is sized as a range before anything changes.
And a second measurement later, to show the saving held.
Instead ofForecast savingsCuts with no rollbackEstimates nobody measured
Check your own platform
Tick each one that is true of yours. One you cannot answer counts too.
Cost signs present, of ten
What a saving is worth
A lower usage lowers the next invoice.
A lower usage frees capacity and lowers the next commitment.
We ask which applies before we promise a figure.
How it runs
Step 1
We agree what is measured, who approves a change and what must not get worse: each service level and business measure, with its limit. Those limits are the guardrails.
Step 2
We measure the cost of the platform and of each resource, then check the costliest against 37 techniques.
Step 3
You approve a set of changes. Each one is proven on a branch first: a copy that production does not read. Then it is released through your change control.
Step 4
We measure usage and every guardrail again, and count only what is proven. Budgets and alerts hold the gain.
Where it fits
The CIO, the platform owner or the finance lead of an organization whose Foundry cost is rising, or who faces a renewal.
A view of usage for the whole enrollment, which is your organization's account on Foundry. The contract rates, or agreement to report in usage units. A conversation with the owner of each of the costliest resources.
Approved changes for your delivery team to make, and budgets, alerts and standards for it to run.
Every change names its guardrails first, and has a rollback written before it is made.
One change at a time on one resource, so each saving can be told apart.
A saving counts only when it is measured, with every guardrail held.
Not a negotiation of your contract with the vendor.
Not a cut in a service level, unless the business owner chooses it in writing.
Not a forecast dressed as a saving.
Questions people ask
A saving is what a resource used before the change, less what it used after, read from the platform's own usage data. It counts only when every guardrail on that resource held.
These never count: growth that did not happen, a saving where a guardrail failed, a change that was rolled back, and a change in price.
Those checks cover scheduled pipelines. The review also covers storage, business objects, applications, always-on compute and budgets.
The review makes one change at a time, through your own change control. Each has its rollback written first.
Never without the data owner. A retention rule or a legal hold outranks a saving.
Then the cost map says so. You hold a measured account of where the compute goes, and we count nothing that we did not measure.
You can, and we hand over the method. With us you gain time, and a statement that is independent of the team that built the platform.
Tell us the decision you must defend this year, or the Foundry platform you want an answer on. We start there.
Book a briefing James replies to you himself.