How Much is Your Competitive Intelligence Worth?
By: Jan P. Herring
Intelligence professionals are often asked to assess the value of their business or competitive intelligence (BI/CI) effort. Most say it cannot be done. I disagree! You can measure its value; both quantitatively and how it is perceived, especially by those that use it. Let’s discuss these two objectives and some ways to approach the task.
I first addressed this problem in a research report, Measuring the Effectiveness of Competitive Intelligence, which I produced for SCIP in 1996. Our objective was to find some quantifiable means of evaluating competitive intelligence (CI). In that project, I interviewed some twenty senior executives, representing eight major companies in very different types of businesses, ranging from aerospace to electronics and including financial services. Surprisingly, none were interested in quantitative measures for their BI/CI programs. In fact, the CFO of the financial services firm did not mention financial measurement of any kind during the formal interview. When questioned about the absence, he replied, “We want to see our BI cause the business to take action ¬ – we can always go back and measure its financial value later!” All the executives interviewed stated they expected to see the BI/CI have some “visible” impact on the company and/or its management decisions.
In addition to simple ROI calculations, the SCIP research identified four quantitative and several qualitative measures that might be applied, including:
– Time saving: Savings for both professional and support personnel.
– Cost savings: Elimination or reduction in expenses.
– Cost avoidance: Elimination of planned expenses.
– Revenue increases: Increases in the number of sales or size of sales.
– Value added: Benefits not easily related to specific dollar values, e.g., more effective strategies or better new products and services.
Assessing Project Value
Such measures-of-effectiveness (MOEs), as they are called, can best be applied to specific projects but they should be selected before the project is actually begun since it is difficult to go back and recover project-specific data after it is complete. I suggest selecting a couple of MOEs initially to be sure the expected result is amenable to the type of measurement you have chosen.
A brief example may be helpful. The management of a high-tech firm decided they needed to diversify their product base but still leverage their technological competence. They would use their existing biotech production process but produce an entirely different type of end-product. To do this as quickly as possible they had decided to purchase the end-product technology for $2.5 million from another firm and use their own production processes and facility.
However, because the new product would have to compete in an entirely difference market they needed both marketing support and competitive intelligence for the new product’s intended marketplace. They would hire an appropriate market research firm but decided to form an ad hoc CI team made up of 4-5 current employees (working part-time).
The ad hoc CI team performed all the usually CI operations. In doing so, the team identified a technical conference where the new $2.5 M product category would be featured. This would provide an excellent opportunity to get a look at both competing product technologies and the competitor companies that the firm would be facing in the new marketplace.
The team prepared well for the conference, including both business and technical personnel. The CI that they collected on the new competitors was great – they not only learned who they were but a lot about the competitive tactics used in that marketplace. But the real surprise came from the competitive technology intelligence (CTI) acquired. The firm that was selling the new-product technology gave a public presentation intending to increase its sales, and in so doing divulged a great deal of the technology’s specific composition – probably more than they had intended.
When the CI team returned from the conference, they met with their own scientists and patent attorneys and it was concluded that the technology, which the firm had intended to purchase for $2.5 million, had been publicly revealed. The firm would not have to purchase it!
The CI team had, from its formation, intended to show the project’s cost-benefit. It kept all the cost data, but was not sure what type of performance measure it might use. A simple ROI was the most likely. As it turned out, the $2.5 M not spent, which falls into the category of “Cost Avoidance” (planned expenditures not spent) was an easily recognizable MOE. But because they had kept good records on the ad hoc CI teams expenses, i.e., about $175,000, they were also able to calculate the project’s return-on-investment: $2.5M minus costs ($175K) divided by cost ($175K) resulting in a simple ROI of over 1,300%. Either measure was more than acceptable to the company’s management team.
Assessing the CI Program’s Value
Programs as a whole are somewhat more difficult, but with some effort on the part of all involved the results can be very satisfying. For example, the NutraSweet BI program was estimated by the company’s CEO to have been worth a least $50 million a year over a 5-year period during the early1990’s. That assessment process was a joint effort, with the BI Department identifying the business decisions and major projects that they had contributed to over the five-year period, and the Finance Department assessing the dollar value for each. Not all BI contributions were accepted, however. The final sum, which was a combination of money saved and/or made, resulted in the $50 million/year average. When Bob Flynn, the CEO, reported the finding at the 1994 SCIP Annual Conference in Boston, he stated that it was in fact a very conservative estimate. For a program that cost about a million dollars a year, that was a pretty good ROI! (Though management was quite satisfied with the dollar amount alone.)
Making CI Success a Part of Corporate Culture
However, I believe the best measure of a CI Program’s value comes in the form of “success stories” – told by those that have benefited from the CI. For example:
• P&G’s competitive benchmarking of a competitor’s distribution system saved it some $40 million when they applied the lessons learned.
• Motorola’s successful acquisition of a European firm, credited to its BI Department, increased its yearly European profits by some $10 million – which is a good example of revenue enhancement.
• NutraSweet’s CEO commented that one decision – not to react to a competitor’s perceived initiative – actually saved the company $38 million. (A classic example of the cost saving MOE.)
• GM’s competitive benchmarking program was credited with saving the company hundreds of millions in comparable manufacturing costs.
• Merck’s CI Program was judged to be worth over $100 million in retained sales for one product alone.
The telling of such success stories by a company’s management is not only good for the CI program’s success, it also adds to the shared belief that CI is a good thing for the company – making it a part of the organization’s “corporate culture”.
In the final analysis you can evaluate your company’s CI effort – if you properly define what and how you intend to measure. In my experience, senior level users of BI/CI are not as interested in financial or quantitative measures of your CI products & services as they are in having intelligence that visibly affects their decisionmaking or business actions in a positive fashion. They do, however, expect to see some form of related action. Those actions that result in grater sales, profits, or other measures of business success are the most valued.
An old friend and associate, Robert Steele, probably put it best, “Information costs money … Intelligence makes money!” Essentially, any competitive information that a business manager acts on becomes intelligence. And, intelligence used by a company that makes money … is good intelligence!