Evaluation of customer relationship system efficiency: Applying of total cost of ownership approach

Calculating total cost of ownership (TCO) and benefits, building a business case and applying financial measurement methodologies help a company make right customer relationship system for investments solution and build compelling justification for its customer relationship system project. In addition, ongoing measurement of customer relationship system (CRS ) benefits ensures that an enterprise receives expected advantages and achieves strategic objectives. In this paper peculiarities of TCO economic efficiency are analysed. Evaluation method application when developing, using and expanding CRS is being considered, strengths and weaknesses of cost‐oriented approach are discussed. Authors present and interpret their empirical research results.


Introduction
As a result of globalisation, companies face ever increasing global competition. Consumers may choose from an increasing variety of suppliers of goods and services: where to purchase food or spend their holidays, which suppliers of telecommunication services to use, where to borrow money or keep it, etc. The privatisation of former state monopolies and elimination of various limitations increase competition to an even greater extent and force companies to reduce their expenses. As accumulation means for fi xed investment, which generally drives companies' growth (Tvaronavičius, Tvaronavičienė 2008), becomes more complicated, companies are forced to put emphasis on managerial tools enhancing client's satisfaction.
Over the past few decades, one may observe the emergence of the concept of the customer relationship management. With the current level of IT systems, we may just make a step back into the past and personalise mass marketing, sales, and customer service. If earlier the owner of a shop kept information about his 100 customers in his mind, the database of the contemporary customer relationship system (CRS) can store information about 100,000 customers and on the basis of historical information, the company can offer each customer what he needs. It is essential for the companies planning to develop a CRS to use adequate evaluation methods to identify the effi ciency of the CRS under consideration and form the basis for objective decisions. In the case of a CRS that has already been implemented and is in use, it is also essential to apply relevant evaluation methods to carry out regular effi ciency evaluation that must help disclose the actual advantages and disadvantages of the CRS in use and demonstrate the levels at which objectives have been implemented.
In order to implement customer-centric strategies, many organizations have turned to CRS software packages from various vendors such as Oracle, SAP, Microsoft, PeopleSoft, Frontrange, etc. (Conner 2001). Successful CRS implementation initiative is deemed to integrate companies' customer-facing processes, improve the effi ciencies of their sales forces and call centres, and more accurately target their campaigns with the help of sophisticated customer data analytics. Therefore this initiative is deemed to place the company in a better fi nancial position for the future.
Companies are investing in CRS worldwide; however, the rate of successful such system implementations are below 30% (Amerongen 2004;Bordoloi 2000;Chase 2001;Kim, H. and Kim, Y. 2007;Ramdas 2001;Silvon Software 2005;Korsakienė et al. 2008). Many organizations pursue expensive CRS initiatives without fi rst understanding the challenges and costs involved. This approach often results in CRS projects that fail to meet measurable benefi t objectives (Korsakienė 2009;Sūdžius 2007). The problem of CRS effi ciency evaluation in the world and in Lithuania has been solved by using traditional economic effi ciency evaluation methods such as Net Present Value (NPV), Internal Rate of Return (IRR), Return of Investment (ROI), Payback Period (PP), Total Cost of Ownership (TCO), Profi tability Index (PI) or Economic Value Added (EVA).
The purpose of this study is to analyse TCO as fi nancial CRS effi ciency evaluation tool when developing, using, and expanding a CRS, and determine strengths and weaknesses of this cost-oriented approach.
To achieve the purpose of this study, research methods were used: scientifi c and practical literature analysis and generalization, and empirical research of Lithuanian companies.

CRS investment justifi cation issues
Justifying the cost of CRS implementation project is not like doing a fi nancial analysis on capital goods. A milling machine, for example, has readily identifiable acquisition and operating costs, and performance specifi cations can be used to accurately forecast productivity gains.
CRS has uncertain cost categories, no standards for valuing funds fl ows, a changing product, and a varying life. As Cooper (2005) states, this creates several unique cost justifi cation issues: 1) High penalty costs. CRS is a high risk endeavour because companies are betting their revenue stream on the project. Service is both a satisfi er and a dissatisfi er. It takes consistently great service to generate customer loyalty, but only one bad interaction to create dissatisfaction and customer loss.
Enterprise resource planning systems are mostly inward-facing, where marginal effi ciencies in traditional processes can be generated, and where systems can be run side-by-side throughout the conversion stage. Customer relationship systems are customer-facing and have a direct effect on customer satisfaction. Marketing, sales and customer service systems can not be run concurrently during a cut-over. Management of customer relationships is either living or it is not. That what is delivered by implementation of CRS is what customers and prospects experience.
The penalty for mishandling the customer relationship management interaction is more than just the cost of a botched transaction. It is the potential lost revenue from a now impaired relationship with customers. That is why customer relationship management decisions are actually justifi cations based upon customer satisfaction expectations. For many organizations, good service is the requirement to stay in business, and integrated CRS is necessary to deliver the level of service customers are demanding. The ultimate cost of refusing to implement CRS is a reduction in organizational competitiveness, viability and longevity.
2) Slow results. There is some disagreement among analysts about how quickly CRS benefi ts accrue. The differences between internal and external benefi ts are at issue. Internal operational benefi ts begin at implementation. Improving call center effi ciency, increasing fi eld service utilization, or moving sales inquiries to the Web can generate immediate savings. But these marginal improvements in operations are often not enough to fully evaluate integrated CRS projects. Customer revenue benefi ts occur some time later in the CRS project's life cycle. Analysts estimate that true payback justifi cation can take 12 months or more (Silvon Software 2005). Customer loyalty is generated from a series of pleasing marketing and sales contacts and service interactions. It requires time for a new CRS to positively infl uence customer behaviour, depending upon the applicable buying cycle.

3) Benefi t time frame exceeds CRS as project life cycle.
Although CRS results can be slow in arriving, they can also continue for a very long time. Inherent in the above discussion of penalty costs is the concept of "lifetime customer value." What this suggests is that the benefi ts or penalties of a CRS can accrue far beyond its life cycle. For instance, a specifi c Customer Interaction Center sales and support system may have a three-year life, but it is attracting (or repelling) customers who might have an average seven-year long relationship.
A good example is when a major toy retailer was unable to ship its e-commerce orders in time for Christmas. Parents were quoted as saying they would never again buy from the site or the company's stores. And this bad experience is likely to trickle down for decades as the children who were disappointed on this Christmas day remember this when deciding where to buy their children's toys in the coming years.
The results of CRS projects closely linked to customers and revenues, may long outlive the useful lives of specifi c products and systems. A CRS justifi cation study must take into account total funds fl ows, both positive and negative, that result during and beyond the system's expected life. 4) Continuous product improvement. Another factor that makes CRS different than other capital justifi cation studies is that the system's benefi ts are not static. Organizations do not buy CRS software, install it, then let it sit as it is for three years. With the help of CRS it must be adapted as customer expectations, effective service processes, product offerings, organizational structures, and strategies evolve. A good example is an organization's forever changing Website. Consequently, CRS product functionality in Year 1 is not the same as in Year 3 -even with the same product. It is not unusual for a CRS to have hundreds of change requests pending when it fi rst goes live, and to have thousands of changes posted throughout its useful life.
As such, projected benefi ts of CRS should refl ect the continuously improving functionality of the system. Software that is harder to customize and integrate will deliver much less value than an open architecture that is easier to enhance.

5) Costing human behaviour.
A fi nal qualifi er in estimating benefi ts of CRS is that analysts are attempting to put a value on human behaviour. This applies to both inside and outside the organization. Most CRS failures are not due to technical issues, but they are caused by refusal of employees or customers to use the system. Organizational change management issues trip-up many organizations. For example, end-user's foot dragging has driven up costs by 300 to 400 percent in some projects (Cooper 2005).

Applying TCO approach when evaluating CRS effi ciency
The total cost of ownership (TCO) can be defi ned as the systematic quantifi cation of all costs generated over the lifetime of a CRS project. The goal of TCO is to determine a fi gure that refl ects the total cost of the investment, including one-time purchases and recurring costs, not just the initial start-up costs. The onetime and recurring costs are determined by looking at each stage of a project, starting with planning, analysis, design, confi guration, programming and installation, and moving through migration, integration, training, and ongoing application support and maintenance where OTC -one-time costs -initial acquisition costs that are usually incurred at the beginning of the CRS implementation project in the form of software licences and hardware, or at the end of the project in the form of decommissioning costs to retire systems or applications; RC (t) -recurring costs -ongoing CRS costs that are incurred on a periodic basis and originate from the maintenance, upgrades, and annual licensing fees, as well as support of CRS; PD -project duration -the expected lifespan of CRM investment.
We recommend calculating TCO over a three -fi ve year period to get a full understanding of the ongoing costs associated with CRS.
However, some companies do not include the project duration in the calculation, and thus the TCO is a summation of costs that are updated continually over the project's lifetime.
TCO has a number of strengths as a metric unit and it is important to calculate when evaluating technology, but it also has a number of weaknesses that need to be understood if company wants to use TCO results properly.
The strength of TCO is in providing an understanding of future costs that may not be apparent when an item is initially purchased.
Another benefi t of the TCO methodology is its use as a benchmarking tool to compare CRS software vendors. Functionality of CRS software can be similar; however, the costs of it may vary drastically from vendor to vendor if including license fees, maintenance contracts, support, etc. Companies can then determine the TCO for each independent CRS software vendor and select the company that offers the least cost over the lifetime of the CRS software. The yearly TCO fi gure is an excellent indicator of the ongoing costs and is best used as a projection for budgeting purposes.
TCO has an important disadvantage because it completely ignores the benefi ts. For most companies the objective is not to choose the cheapest CRS software but to choose the software that provides the greatest benefi t or return for the company. Many companies along with the press have focused on TCO as an important metric primarily because it is a tangible number. It is easy to point to a complete accounting of cost and make a decision based on a strategy of reducing expenditures. But CRS software, because it is used in key business processes, can have a dramatic impact on the bottom line and TCO only ensures a company to purchase the cheapest CRS, not the best.
Also, product with low acquisition costs and high maintenance is likely to be less attractive than one with higher acquisition and lower ongoing costs, but it may have a similar TCO over the period analysed.
In comparison with return on investment (ROI) and payback period of fi nancial measurement methodologies, TCO is the best indicator of future CRS expenses. However, it is a weak indicator of risk associated with CRS and balance of cost versus return.

Empirical research results
Based on our empirical research results, only 25% of Lithuanian companies calculate TCO of CRS. Whereas half of Lithuanian companies are evaluating summation of all CRS costs (Fig. 1).
The majority of Lithuanian companies calculate CRS initial acquisition costs (Fig. 2). However, ongoing costs are calculated by less than a half companies.
Based on our research results (Fig. 3), costs of initial CRS implementation works (analysis, design, installation, confi guration, programming, integration, and migration) and CRS software licences represent almost half of the total cost of a CRS implementation project (47%). Hardware (servers, computers) costs make 21% of all total CRS implementation project costs. Employee training, internal staff work and external consulting service costs represent relatively a small part of total costs (8%, 8% and 7% respectively). CRS maintenance and support costs represent the smallest portion of total costs (4%).

Conclusions
Calculating TCO and benefi ts, building a business case and applying fi nancial measurement methodologies can help a company make right CRS investments solution and enable it to enjoy the results -instead of complaining that CRS fails to meet expectations. Therefore, an enterprise needs to assess the costs and benefi ts associated with CRS, then express that evaluation in fi nancial metrics.
In addition, ongoing measurement of CRS benefi ts helps ensure that an enterprise receives expected advantages and achieves strategic objectives. The following guidelines should be used to manage TCO successfully (Gartner 2004): 1) build companies' TCO model to include consistent cost categories across all CRS projects for three-fi ve years; 2) build bestand worst-case scenarios to determine TCO tolerances; 3) staff the CRS project with employees who have experience in building and measuring TCO; 4) include fi nancial analysts on the project to assist with the approval process, and to provide insight for senior management during the life cycle of the initiative; 5) expect vendor proposals and internal staffi ng decisions to come before a fi nal TCO calculation; 6) monitor and measure costs and spending throughout the project.
Application of a single TCO method is not suffi cient for comprehensive (complex) evaluation of CRS efficiency because TCO completely ignores CRS investment benefi ts. A range of effi ciency evaluation methods and models must be applied, like ROI, PP, NPV, IRR, EVA, etc.