The CEO of a small software vendor contacted me last week with a simple question. Did I know of any recent research that provided typical ratios for Tier II ERP implementation cost to software license cost? He didn't say why he was asking, but I assume it was in order to position his own customers' experience against some sort of industry benchmark.
My reply was simple. I wrote:
Dear XXX, Unfortunately, I do not have current stats on implementation to license fee revenue. It is something we should survey, as we do get asked this a lot. I usually quote a range from about 75% to 200%, typically. But as you can imagine, discounts on the software license fees affect that, and also the extent of data conversion and interfaces/integrations and modifications. Also the amount of business change being introduced.
A few moments later, I tweeted a short status update, "Chatting with a vendor about implementation cost to software license cost ratios." That triggered an interesting three-way discussion between Dennis Howlett, Martijn Linssen, and myself on the subject.
Martijn has already
followed up in a blog post. In short, Martijn's position is that "there is a
clear, direct and fairly linear relation between the initial cost of a product, and the additional cost(s) involved servicing it" [emphasis mine]
Not a direct relationshipI agree with Martijn that there is a relationship between the cost of the software and the cost of implementation. But I do not agree that it is a
direct relationship. For example, if Company A pays more for SAP than Company B does, you can expect Company A will pay more for implementation. This might be because Company A has more users or is installing more modules. These factors will cause the software cost as well as the implementation cost to be greater for Company A. But what if SAP greatly discounts the software cost for Company A? Will that bring the implementation cost down for Company A? Of course not.
What drives implementation cost? In fact, I have been in deals where software vendors have basically offered to sell the software at little or no cost. Does that mean the vendor or systems integrator will be willing to support the implementation for little or no cost? Of course not.
This thought experiment essentially proves that the relationship between software cost and implementation cost is not a direct relationship. There is no cause and effect. Rather, based on our
ERP selection and implementation project management experience at Strativa, we find that total ERP cost is affected by a number of factors.
First, there are two factors that affect both the cost of the software and the cost of implementation:
- Number of users. Software is often priced by the number of users. The number of users is also a factor in implementation cost, as more users generally means more user functions affected, more business processes affected, and more training required.
- Number of modules/amount of functionality. Similarly, software is often priced by the scope of functionality included. Software with more functionality is generally more expensive than software with less functionality. Likewise, implementing software that supports a broader set of business functions will cost more.
In addition, there are several other factors that affect implementation cost but do not generally affect software license cost. These include the following:
- Amount of data conversion or interfaces required. An organization that can implement the new system cleanly, without a lot of data conversion from the old system and without building interfaces to legacy or third-party systems, will get by with a lot less implementation budget than an organization that requires much data conversion or integration.
- Amount of business change required. An organization with well-defined business processes that conform to the business processes defined in the software will generally pay less for implementation than an organization that needs a lot of business process change.
- Skills and availability of the internal project team. An organization that has a well-formed internal project team with skilled resources will generally pay less for implementation than an organization that depends mostly on outside contractors to undertake implementation activities. (The organization with the well-formed team is also at less risk of project failure.)
- Choice of the implementation consulting partner. An organization that engages the help of a qualified systems integrator (or the vendor's own consulting arm, if so qualified) will generally spend less on implementation than an organization that chooses an SI with lesser skills or a poor track record in delivering services within budget.
There are other factors as well, such as the degree of standardization of business processes among multiple facilities and the organization's track record in managing cross-functional business change projects.
"Complexity" of the software may be a factorFinally, there is one other factor that is a wild-card, in my opinion. That is, the complexity of the software itself. This may or may not affect software license cost, but it often affects implementation cost.
This may be easiest to define with an example. SAP and Oracle are two well-know, so-called "Tier I" ERP systems. It is generally understood that these systems can support the largest, most complex, most geographically-dispersed organizations. They can support the widest number of industry sectors. They do this by incorporating a great deal of functionality for various industries, business processes, and local regulatory requirements. They are highly configurable. In other words, they are big pieces of software, or as I like to put it, they have a "big footprint."
This complexity comes with a price. It means that to make use of the system in a specific organization, many decisions have to be made during the implementation. These decisions cost time and money to configure the software and test it specifically for the organization's needs. This drives up the cost of the implementation.
SAP and Oracle are well-aware of this issue and have worked hard over the past decade to pre-configure their systems for specific industries and use cases. If a customer fits well into the vendor's pre-configured templates ("accelerators" in Oracle-speak, or "best practices" as SAP calls them), much of the complexity of the software can be hidden from view. Customers that fall neatly into the vendor's template can sometimes achieve very rapid and cost-effective implementations. Both vendors will gladly share references of such with prospects.
But don't the higher-end software packages still cost more than software targeted for small and mid-size businesses? This is not always the case. I have seen situations where SAP and/or Oracle were actually the low-cost bidders. In cases where a software vendor wants the deal, it is not safe to assume that the higher-end package will cost more. For this reason, I don't believe software "complexity" in itself is a consistent factor in either software license cost or implementation cost. As we consultants like to say, "it depends."
Popularity of implementation-to-license cost ratioSo, why do software vendors, customers, or systems integrators continue to use the implementation-to-license cost ratio? Because, as flawed as the ratio is, it does serve to set expectations as to implementation cost. To me, the ratio best works in hindsight. If a system implementation, on average, requires 1.5 times the software cost, a customer better not be assuming that it can do it for half the license cost.
But to really judge the prospective cost of an ERP implementation project, nothing beats doing a detailed estimate based on a realistic work-breakdown structure, with realistic estimates that take into consideration the factors outlined in this post.
Related postsERP implementation: plan for the worstEpicor's Shared Benefits program: watch for unintended consequencesRevisting Epicor's Shared Benefits programOracle claiming ultra-fast installs in SMB market
Send tips, rumors, gossip, and feedback to Frank Scavo at
.
