How to Measure the ROI of Your Cloud Spend

By: Morpheus Data

Quantifying the cost of cloud ownership is no simple task.Take some of these tips to measuring the ROI of your cloud spend


Getting an accurate assessment of the total costs of public, private, and hybrid clouds requires thinking outside the invoices.

Quantifying Cloud Cost of Ownership

The big question facing organizations of all types and sizes is this: Which is more cost-effective for hosting our apps and data, in-house or cloud? While it may not be possible to achieve a truly apples-to-apples comparison of the two options, a careful cost accounting can be the key to achieving the optimal balance of public, private, and hybrid cloud alternatives.

If accountants ruled the world, all business decisions would come down to one number: maximum profit for the current quarter or year. In fact, basing your company’s strategy solely on short-term financial returns is one of the fastest ways to sink it. Yet so many IT decision makers look to a single magical, mystical (some would say mythical) figure when planning their tech purchases: total cost of ownership, or TCO.

Determining TCO is particularly elusive when assessing cloud alternatives to in-house development and management of an organization’s apps and data. How do you quantify accurately the benefits of faster time to market, for example? Or faster and simpler application updates? Or an IT staff that’s more engaged in its work? These are some of the questions posed by Gigaom Research’s David S. Linthicum in a May 9, 2014, article.

Linthicum points out that while tools such as Amazon Web Services TCO calculator, Google’s TCO Pricing Calculator, and the collection of cost calculators at The Cloud Calculator help you understand the simple costs and benefits of using cloud services, they exclude many of the most important aspects of the to-cloud-or-not-to-cloud decision.

The AWS TCO Calculator is intended to provide customers with an accurate cost comparison of public-cloud services vs. on-premises infrastructure. Source: AWS Official Blog

The most glaring shortcoming of TCO calculators is their one-size-fits-all nature. By failing to consider the unique qualities of your company your business processes, the skill level of your staff, your existing investment in hardware, software, and facilities the calculators present only a part of the big picture.

An even-greater challenge for organizations, according to Linthicum, is how to quantify the value of agility and faster time to market. By including these more-nebulous benefits in the TCO calculation, the most cost-effective choice may be the cloud even when a traditional hardware-software-facilities TCO analysis gives the edge to in-house systems. Linthicum recommends seven aspects to include in your living model to better understand your cloud spend:

  1. The cost of sidelining the assets in your existing infrastructure
  2. The amount of training for existing staff and hiring of new staff needed to acquire the requisite cloud skills
  3. The cost of migrating your apps and data to the cloud, and the degree of re-engineering the migration will require
  4. The cost of using public cloud services over an extended time, including potential changes in operational workload
  5. The value the company places on faster time to market, faster updates for apps and data, and the ability to respond faster to changing business conditions
  6. The savings resulting from reduced capital expenditures in the future, which often boils down to opex vs. capex
  7. The risk of the potential failure to comply with rules and regulations governing particular industries, such as healthcare, insurance, and financial services

Boiling down the public cloud vs. private cloud equation

As tricky as it can be to get an accurate read on the total cost of public cloud services, calculating the many expenses entailed in operating a private cloud setup can leave experienced IT planners scratching their heads. In a September 9, 2014, article on ZDNet, Intel’s Ram Lakshminarayanan outlines four areas where the costs of public and private clouds differ.

While public cloud services don’t usually charge software licensing fees, their per-hour compute instance fees are likely to be higher for proprietary OSes such as Microsoft Windows than for Linux and other open-source systems. By contrast, proprietary cloud providers often apply a licensing fee for their virtualization software by the CPUs or CPU cores they require. (Use of OpenStack and other open-source private cloud software does not entail a licensing fee.)

The biggest cost difference between public and private cloud setups is in infrastructure. To build a private cloud requires upfront expenditures for compute, network, and storage hardware, as well as ongoing costs for power, cooling, and other infrastructure. Public cloud services charge based on pro-rata, per-hour use, although their rates cover the providers hardware and facilities costs

Likewise, support costs that are built into public cloud rates are a separate line item for most private clouds and must be negotiated separately in most cases. Finally, IT staff training must be considered both an upfront and continuing cost that will likely be higher for private clouds than their public counterparts, which benefit from straightforward dashboard interfaces designed for end users. A prime example is the Morpheus application management service, which features an intuitive UI for provisioning databases, apps, and app stack components on private, public, and hybrid clouds in just seconds.

Hybrid clouds in particular depend on cost management

The Goldilocks cloud solution the one that is just right for a great number of small and large organizations is the hybrid approach that mixes public and private components. This allows the companies to benefit from the public cloud’s efficiency and cost savings while protecting critical data assets in a private cloud. Accurate cost accounting is imperative to ensure both sides of the cloud equation are applied to best advantage for your firm’s data needs.

CFO’s Penny Collen writes in a March 12, 2015, column that TCO for hybrid clouds shouldn’t be approached from a project-life-cycle perspective, but rather as presenting a big-picture view of all operational costs. That’s the only way to get an accurate assessment of all your provisioning alternatives, according to Collen. She identifies four areas in which specific costs must be identified:

  1. Hardware acquisition (asset records, purchase orders, vendor price lists)
  2. Hardware maintenance (as a percentage of acquisition costs and maintenance averages)
  3. Software (based on historic hardware/software ratios in your company)
  4. Infrastructure and tech support (connectivity, facilities, disaster recovery, administration)

One-time costs include the following:

  1. Design
  2. Architecture
  3. Data migration
  4. Data porting
  5. Data cleansing and archiving
  6. User and technical support training
  7. Standardization, upgrades, and customization

Categories in cloud cost accounting include servers, storage, software, labor, networking, facilities, and support. Source: CFO

Cloud-specific costs that must be part of the analysis include the following:

  1. The need for more network capacity
  2. Vendor fees (primarily for public cloud services)
  3. Administration of cloud invoices
  4. Management of relationships with cloud vendors

Last but not least, consider fees related to the cancellation terms stipulated in the cloud service’s contract. Also factor in the cost of migrating to an alternative cloud provider to avoid being squeezed by vendor lock-in.

To find out how Morpheus’ PaaS solution can help you avoid cloud lock-in to save time and money, download the use case here.