Menu
Menu
How to Build a Business Case For SharePoint

How to Build a Business Case For SharePoint

A business case without a well-framed model of costs will not pass the proverbial sniff test

Developing a business case for any IT investment is a complicated exercise. But building a business case for SharePoint poses specific challenges because much of its ROI is intangible: SharePoint deployments can lead to process improvements, but it's not always easy to quantify the dollar value of those process improvements.

Any business case--whether for SharePoint or any other system--typically requires various financial measurements, such as return on investment (ROI), total cost of ownership (TCO), discounted cash flows (DCF), net present value (NPV) and internal rate of return (IRR), to be estimated.

That's the point you want to make in your business case: By leveraging SharePoint and add-ons from Microsoft partners, your enterprise will be able to do more with less.

You'll need to figure out which of these measurements your financial analysts require in a business case for a software implementation.

Fundamentally, a business case for any software implementation should include three core points: the hard savings, the soft savings and risk mitigation. A business case specifically for SharePoint should also address the product's rich functionality and its broad user support--both of which are distinct selling points for SharePoint.

When these five points are well-defined and properly communicated in your business case, it will unquestionably accelerate acceptance and funding of SharePoint investments.

Hard ROI

A business case without a well-framed model of SharePoint's costs will not pass the proverbial sniff test with most financial analysts, and rightfully so. However, with the costing model established (see How To Determine The True Costs Of SharePoint), the business case can progress.

The first element of any business case for any software application is the cost savings that will result. Organizations that deploy SharePoint for imaging-based solutions, for example, can demonstrate how physical storage and retrieval costs are minimized or eliminated. Another example of imaging-related hard savings is the elimination or reduction of shipping costs: Because SharePoint stores documents in one centralized, online environment, documents no longer have to shipped to various locations.

Finally, SharePoint often leads companies to consolidate or eliminate other enterprise content management systems a company may be using, which in turn can result in measurable savings on software licenses, software maintenance and technical expertise.

Russell Stalters, BP's head of information and record architecture, is planning to accelerate his company's SharePoint deployments because of the substantial savings the product is introducing. "SharePoint projects are coming in at approximately 50 percent of the overall cost of traditional enterprise content management (ECM) systems," he says, adding that SharePoint's benefits go beyond the cost savings associated with reducing software licenses.

Soft ROI

The second element of your business case deals with soft savings--the less tangible benefits that result from deploying software and systems. In many cases, the soft savings that stem from SharePoint are efficiency improvements, such as the amount of time a person or group will save as a result of using SharePoint to automate manual business processes or to retrieve stored documents.

You can substantiate your claims of efficiency improvement by performing time and motion studies, which track the amount of time it takes someone to perform an activity before and after SharePoint is implemented. These typically require a fairly in-depth analysis of the workers' activities, and it is important not to overstate the workers' newly available time. For example, if a SharePoint process is introduced that allows a worker to complete a one hour job in five minutes, you should not recognize all 55 minutes as savings. It's safer to estimate a smaller portion of the time savings.

Another SharePoint-related efficiency improvement is the reduction of the time it takes to produce an important deliverable in your organization. For example, by employing SharePoint for case management, you may be able to demonstrate how SharePoint can reduce the closure of a case from 10 days to five. If the speed of case closure is an important factor in your organization, you should include it in the soft savings portion of your business case.

Join the CIO New Zealand group on LinkedIn. The group is open to CIOs, IT Directors, COOs, CTOs and senior IT managers.

Join the newsletter!

Error: Please check your email address.

Tags MicrosoftroicollaborationSharepointmicrosoft sharepointthe business case

More about Analog DevicesMicrosoft

Show Comments