Everybody gets that procuring and implementing software isn't the same as hardware. I've been writing endlessly about how CRM is different from other enterprise software — not technologically, mind you, but in terms of the business drivers and the physics of the cost-benefit equation.
So why does everyone try to make CRM business cases the same way they would for an HVAC system upgrade? Well, part of it is that many businesses spend less on IT than they do on heating and energy, so they don't feel they have to be that careful. Plus, everyone wants to use the tools and methods perfected in other parts of the business (say, the factory, the distribution system or the network) rather than starting from scratch. Blindly applying rules and methods from other parts of the business yields crummy decisions about CRM projects — and crummy assumptions lead to crummy results.
Unlike any other enterprise software category, CRM systems' costs and benefits vary widely by industry and don't scale up or down in predictable ways. Further, as with news media, the information that's easily accessible to you is very likely to be misleading.
CRM vendors will gladly provide case studies only marginally applicable to your business. Industry analysts will give you lots of data and examples, but the data points are from a fairly skewed population. Unfortunately, benchmark data on the meaningful stuff is hard to find.
If you want the right answers to drive an optimal CRM business case, you're going to have to do some original work.
CRM Costs Always More Than They Appear
The good news? Some costs are fairly easily quantified. You can just ask for quotes and, in a few days, know the up-front obvious stuff.
Of course, that's not the important side of costs. Four factors will completely overwhelm the initial procurement cost:
- For a system of any size, the data maintained inside the CRM is far more costly than the system itself. If you pay only $100 per lead, those 750,000 people in your database cost you at least $75 million. Of course, that's sunk cost at this point, but the amount you should be willing to pay to keep that asset valuable and current far exceeds the cost of nearly any CRM project.
- For CRM use cases that need to have visibility into other systems (in particular, for ecommerce and service and support use cases), the costs of data cleanup, integration, and reconciliation can be amazing — a couple dollars per record, sometimes more. Best of all, you're much more likely to discover new data problems as you dig in. Aside from the unknown financial costs, this is typically the most annoying part of any CRM project, thanks to overburdened personnel and plain old politics.
- For an implementation project of any complexity, the overruns and follow-on phases will almost certainly exceed the size of the initial project. In my humble opinion, this goes double for classic waterfall fixed-price CRM projects, or when a lot of integration is required for the CRM to be really effective.
- For a user base of any size, the biggest costs of all may well be wasted user time. Particularly in politically-charged situations that are all too common in CRM projects, even a "correct" system can lead to a lot of silliness. Yes, you can view this as a sunk cost as well, but employee inefficiency should never be ignored. This is particularly true if you have large field forces for sales and support.
Sign up for CIO Asia eNewsletters.