Operations teams looking to adopt autonomous optimization need to show business value to get buy-in from leadership. Here are four areas to consider including in your autonomous business case and ROI. Your autonomous business case should consider cloud cost savings, performance gains, availability improvements and time savings.
Operations teams looking to adopt autonomous cloud management need to show business value to get buy-in from leadership even when the technology "just makes sense". Gartner called out this potential disconnect with business as an obstacle to the adoption of autonomous workload optimization in their report "Hype Cycle for Monitoring and Observability, 2023" (written by Pankaj Prasad and Padraig Byrne).
Four Areas to Consider in an Autonomous Cloud Managementย Business Case
Here are four areas to consider including in your autonomous business case and ROI:
1) ๐๐น๐ผ๐๐ฑ ๐๐ผ๐๐ ๐ฆ๐ฎ๐๐ถ๐ป๐ด๐
The most readily understood area of value. Business case benefits can be projected at three levels:
a) ๐ช๐ผ๐ฟ๐ธ๐น๐ผ๐ฎ๐ฑ: gains from finding the optimal resource settings (e.g., CPU, memory) that meet performance needs at least cost
b) ๐๐ป๐ณ๐ฟ๐ฎ๐๐๐ฟ๐๐ฐ๐๐๐ฟ๐ฒ: optimizing the mix of instance types (e.g., M5, C5 or R5 for AWS) based on this updated workload configuration
c) ๐ฃ๐๐ฟ๐ฐ๐ต๐ฎ๐๐ถ๐ป๐ด: optimizing discounts based on ML-based traffic forecasts
Projections for each of these can be established by completing a pilot exercise on a representative set of workloads (later stage business case) or using general ranges from other companies' experiences (early stage).
2) ๐ฃ๐ฒ๐ฟ๐ณ๐ผ๐ฟ๐บ๐ฎ๐ป๐ฐ๐ฒ ๐๐ฎ๐ถ๐ป๐
Autonomous systems can also uncover latency gains by optimizing resources (somewhat of a mirror image to cost above). However, identifying the subset of services where latency impacts revenue is key when calculating the business value of latency gains. Examples:
a) ๐๐๐๐๐ผ๐บ๐ฒ๐ฟ ๐ณ๐ฎ๐ฐ๐ถ๐ป๐ด ๐ฎ๐ฝ๐ฝ๐น๐ถ๐ฐ๐ฎ๐๐ถ๐ผ๐ป๐ in industries like e-commerce and SaaS where customer experience and revenue are linked (over time) to page load speed.
b) ๐ฃ๐ฟ๐ผ๐ฐ๐ฒ๐๐๐ถ๐ป๐ด-๐ถ๐ป๐๐ฒ๐ป๐๐ถ๐๐ฒ ๐๐ผ๐ฟ๐ธ๐น๐ผ๐ฎ๐ฑ๐ where lower latency improves product quality (e.g., faster security scans) or time to revenue improves (e.g., drug discovery).Projecting the revenue impact of latency is also needed and reference to benchmarks (e.g., Amazon's 100ms = 1% of revenue) or internal data is needed.
3) ๐๐๐ฎ๐ถ๐น๐ฎ๐ฏ๐ถ๐น๐ถ๐๐ ๐๐ฎ๐ถ๐ป๐
Autonomous systems also optimize availability by preventing issues (e.g., out of memory) that could trigger revenue-impacting incidents (e.g. payments in e-commerce). Projecting improvements on a metric tied to customer experience (like Failed Customer Interactions (FCIs)) is ideal but errors can be used as a proxy, assuming you've started measuring availability on a request basis. As with performance, the value of reducing this metric is needed. Inhouse estimates or benchmarks can be used.
4) ๐ง๐ถ๐บ๐ฒ ๐ฆ๐ฎ๐๐ถ๐ป๐ด๐
Time savings accrue as autonomous systems act as AI copilots for operations teams (e.g., SRE, DevOps, FInOps). A simple approach is to determine the volume of potential actions that the system will take and the typical time today needed to perform them.โ
Key Metrics to Build an Autonomous Cloud Managementย Business Case
In the chart below we show how these four areas can be used to define a set of metrics that can be used to calculate the overall benefits in an autonomous cloud management business case:

To get help on creating an autonomous business case based on this approach and tailored for your organization, please contact us via website chat or our contact us page.
โ
