4
experts mobilized
5
weeks on the engagement
3
environments (AWS, Azure, SaaS)
~$2M/year
in identified savings
Are Your Cloud Costs Increasing Without Clear Explanation?
In five weeks, Leonys analyzed the group’s AWS, Azure, SaaS and legacy environments and identified nearly CAD $2M in annual savings.
The challenge: making legacy cloud costs visible
The client: a complex multicloud environment
A Canadian investment group, with cloud infrastructure split across AWS and Azure, complemented by a portfolio of business SaaS software, for cloud spend and total SaaS spend of more than CAD $15M per year. Part of the technical legacy relied on a shared legacy cost center, largely invisible to product teams.
Two full-time FinOps consultants, engaged by a competing firm, were already working on the topic. However, in the investment group’s view, the savings found remained below the true potential: Leonys was brought in to challenge the existing work and verify whether there was still value to capture.
The need: savings potential still untapped
Despite the presence of two full-time FinOps consultants, the savings identified remained below the potential estimated by the group. Leonys was therefore engaged to take an independent look at the scope and identify levers that were still untapped.
- Assign a cost to shared legacy infrastructure, invisible to business teams
- Quantify double payments between the existing setup and target systems being migrated
- Identify idle and poorly sized workloads across the entire cloud scope
- Obtain quantified leverage to prioritize budget trade-offs
The main blind spot: the legacy cost center
A significant portion of the cloud infrastructure relied on a shared legacy cost center, with no visibility and no clear ownership by product teams. With no cost assigned, there was no signal to trigger migrations to the target architectures already approved:
- Double payments between the existing infrastructure and target systems being migrated
- Idle and poorly sized workloads, silently absorbed by the shared cost center
- No quantified lever to prioritize budget trade-offs with delivery teams
“ Nous voulions savoir combien nous coûte le fait de ne rien faire, de ne rien migrer. Ce price tag, c'est ce qui nous manquait pour mieux arbitrer nos prochains investissements notamment dans l'IA."
Leonys’ FinOps support
A complete cost map
Leonys mobilized a dedicated FinOps team to map the entire cloud and SaaS scope, while focusing the analysis on the legacy cost center identified from the outset as the main blind spot.
The engagement is based on a shared engagement model: a fixed fee, supplemented by a portion of compensation indexed to the qualified savings identified, to align Leonys’ effort with the value actually found.
A team of four complementary experts
- 2 Cloud architects: technical mapping and target architecture recommendations
- 1 FinOps engineer: cost analysis and quantification of findings
- 1 FinOps lead: engagement management and readout to teams
Scope of the engagement
- AWS mapping: multi-account inventory of resources and costs
- Azure mapping: the same exercise on the second cloud environment
- SaaS analysis: review of the software portfolio and actual usage
- Final report: summary of findings and prioritized recommendations
Nearly CAD $2M in annual savings identified
- A previously invisible cost center, now mapped and quantified
- A prioritized action plan, ready to be presented to delivery teams
- Budget trade-offs based on quantified data
- Leonys compensation partially indexed to the qualified savings identified
Result: ~ $2M/year in identified savings across the analyzed scope.
