Customer Story – Making the ROI Case for Stat

The Return on Investment (ROI) for Stat surfaces during every customer discovery call and/or product demonstration.  Most of the time the question is answered in general terms covering the following bullet points:

  • Code migrations took hours, now minutes
  • Audit time reduced significantly
  • Patching time and patching impacts reduced
  • Recovery of objects after an environment refresh taking hours not days
  • Upgrade time reduced by months
  • Increased staff productivity
  • Increased application availability

All points are valid and any one of the points could be used by a customer to make the ROI case to justify acquiring and implementing Stat for their ERP environment(s).  Some of the ROI points are related could even serve as a heading.  For example, one could easily make the point as follows:

Increased staff productivity

  • Code migrations took hours, now minutes
  • Audit time reduced significantly
  • Patching time and patching impacts reduced
  • Recovery of objects after an environment refresh taking hours not days
  • Upgrade time reduced by months

The ROI case is also dependent on the role of the individuals attending the meeting or demonstration.  For example, developers and DBAs rarely get excited about Audit time being significantly reduced.  However, a manager, internal audit, or compliance team member is always interested in hearing how Stat can save time and money on their audits.

Perhaps the most compelling to a general audience is the time and savings from reducing code migrations from hours to minutes.  This scenario led me develop the following scenario for Stat for Oracle EBS and the code migration ROI.  I like to use the use case where a business user requests a new Oracle report. 

I start by listing out all the components that typically make up an Oracle report and describe the manual actions required to migrate the new report to an environment.

Next, I ask them to provide their time estimates for each object.  When done we have the information we need to calculate the savings for a single report by using Stat to version, package, and migrate the new report.

Next, we describe migrating the same report using Stat.

Of course, not every organization will develop and deploy 500 new reports per year.  However, the typical savings Stat customers have reported by automating the versioning, packaging, and deploying developer changes runs in the 70-75% range.

Developers and DBAs spend less time performing tedious manual steps, which are prone to error, and have more time to concentrate on other important tasks that may also lead to savings.

How much is your company spending on manual migrations? How much could you save using Stat?  To find out more, leave me message below or send me an Email.

Anonymous