At this point in your journey to buy a new software solution, you should have:
You are now ready to quantify the expected benefits into a monetary amount to justify the software purchase, a critical and often required step.
Meet with your executive sponsor to find out the justification needed for purchase approval. Your executive sponsor will know what is required and may also be able to provide examples of similar justifications successful in the past. Confirm that the justification demonstrates how the software will address the company’s goals and the executives’ needs and motivations.
Quantifying is challenging but necessary and doable. If your team has done a good job at business needs identification, then you should have agreement that you need a solution and it is “worth it.” But gut feel, even based on past experiences, isn’t what executive sponsors and CFOs want.
The financial case should include two components:
Think about the financial-benefit factors of this project as a sum of two components:
Increased Revenue + Reduced Costs
Increased revenue for most companies comes from selling more products, improving customer retention, accelerating fulfillment, providing more predictable cycle times, and improving collections.
Reduced costs impact a company’s bottom line. “A dollar saved is a dollar earned.” As discussed in the first chapter, here are some possible areas where costs can be reduced with better information sharing and automation.
Revisit your business needs and requirements by listing all processes that can be improved with the proposed software investment. Usually, better information sharing and more automation speeds processes and reduces errors. This frees up your teams to do more value-added work.
For each process, you want to measure the cycle time and error rates. And any manual or duplicate data entry processes that can be replaced with an integration will help eliminate errors.
At this point, you should assign a dollar value to expected improvements. Remember both factors: increased revenue and reduced costs.
To make quantification believable, you need improvement metrics. Ask vendors for case studies or benchmarks from past implementations to give you an idea of the potential for improvements. You can also look to third-party research and analysis for case studies on costs of bad processes or expected improvements.
Estimate the expected improvements by determining a range based on best, expected, and worst-case improvements.
To do this, talk with people in different roles who understand how each process contributes to the business. You will also need some basic company financials such as company revenue, cost of goods sold, gross margin, and daily team expense (employees). Your formulas will vary depending on both your business and what business needs you are impacting. Our examples are for product and quality business needs for product companies.
To calculate possible financial benefits based on your particulars, use this easy calculator for product and quality business needs.
If you are replacing an existing solution, you need to add those related cost reductions to the calculations. For example, if you have on-premises client/server software, calculate the total cost annually for software, hardware, and upkeep, including FTE resources, particularly for homegrown solutions that require continued oversight. If you have a mismatch of off-the-shelf tools and manual, the actual software used may cost you little today in hard dollars.
As well as hard dollar improvements, consider these benefits of having the solution you need: ability to respond to changes, be more competitive, and have better decision-making inputs.
How do your processes scale with existing technology, personnel, and other resources? What parts of these processes are manual and not repeatable? What could be automated to help your teams address higher-level issues instead of routine administrative work? Contrast this with the new proposed solution. In general, your goal is to increase resiliency: the ability to handle the ups and downs in business cycles.
It’s unrealistic to place an exact dollar value on any software solution’s ability to improve these intangible areas. Yet, you should include these benefits in your justification.
Return on investment describes the financial benefit relative to the investment cost. At its simplest:
ROI = (Gain from Investment – Cost of Investment) / Cost of Investment
ROI looks at:
Real-World Example From a Medical Device Company
Accuryn Medical reported their ECO (engineering change order) cycle times were shortened by 30% using Arena’s cloud-based quality management system. For product and quality management processes, you can see more benchmarks in these customer stories. Let’s look at how you might build a financial case for this business need.
Identify Processes to Improve
Automating ECOs, like Accuryn Medical did, impacts business in three ways.
Target Improvement Metrics
Translate Into Financial Benefits
Ideally, you would model expected, best, and worst case. For the purposes of this example, we’ll use worst case for target improvement metrics, which is 12% ECO cycle time improvement.
Return on Investment (ROI)
For our scenario, assume the favored solution costs $95K annually, plus $15K startup costs in the first year.
ROI = (Gain from Investment – Cost of Investment) / Cost of Investment
3.14 months = (456,000 – 110,000) / 110,000
If the numbers above are valid, you will easily make that investment back within a year—in fact, in less than four months, and your cumulative ROI over five years will be 444%. You can calculate out your yearly costs against continued investment gains and build a sophisticated ROI model if necessary with this template.
You’ll want to validate your findings with the finance team. Share your assumptions, perceived benefits, and justification. Finance should be able to check the company metrics as well as provide any other details you missed. In addition, this discussion provides an opportunity to prepare finance for a possible purchase and for you to verify any additional information finance will need for approvals.
✓ Calculate ROI for a solution
✓ Review ROI with finance