Seven engagements, published with their baselines.
Each one states the estate we assessed, the commercial positions we priced against one another, and the baseline every figure is measured from. Where a number is not comparable with the others, we say so on the page rather than in a footnote.
Checkable, or it does not go up.
Most published assessment results in this market are the same three vendor benchmarks repeated, with no client, no estate and no baseline behind them.
We would rather publish fewer numbers that hold up. Every figure below comes from an engagement we delivered, measured against a baseline we name on the page. Two of the seven are measured against a different baseline from the other five. The label under each figure says which, rather than averaging them quietly together.
How a county government kept host-level SQL Server licensing intact on AWS
Read the engagement →Telecommunications · United StatesHow a fibre operator found half its estate did not need to move at all
Read the engagement →Healthcare · United StatesHow a healthcare provider found 930 Windows cores it had already paid for
Read the engagement →Software and SaaS · United StatesHow a legal software provider priced its entire AWS operating cost, not just compute
Read the engagement →Financial services · Sub-Saharan AfricaHow a bank took $944,038 a year out of a 716-workload migration
Read the engagement →Public sector · United StatesHow a state agency put 2,466 owned Windows Server cores back to work
Read the engagement →Software and technology · Cloud-nativeHow a 19-workload Azure estate got the same rigour as a 700-instance one
Read the engagement →Your estate is not one of these.
Which is rather the point. Every one of these started as a scoping call about an estate nobody had measured properly.