# 7 Steps to Avoid the Cheap IT Solution Selection Trap

Posted by Jamie Black

Topic(s): Efficient, Effective and Reliable

Given that we continue to hear about IT projects failing at an alarming rate (according to some surveys, more than 50% fail), there are a lot of topics that we could discuss respecting the selection and implementation processes. We have discussed a number of them but there is one trap we see all the time.

## Price Clouds Everything

Consider the Canadian government's recent Phoenix payroll software debacle. They elected to have a payroll system custom developed by IBM and have had nothing but problems with it. According to one assessment:

"... the Harper government put so much emphasis on saving money that it undermined efforts to ensure that the system would function well....instead of saving the government 70 million Canadian dollars this year, as promised, Phoenix has cost the government an extra $50 million (about USD$ 37 million), including \$6 million in additional fees paid to IBM to fix it."

When participating in an IT system evaluation and you find your team leaning toward the low-cost choice instead of the high-value solution: beware. No one wants to pay more for something than they need to. In particular in government, you may even have the obligation to choose the low-cost solution. This default preference/requirement is understood by the IT solutions sales representatives and is often relied upon to accelerate the sales cycle and "close the deal." Even if you're not being exploited by sales teams, the Phoenix case shows how this low-cost bias can lead to dysfunction. Here are two questions to ask yourself to avoid a bad deal when considering the "cheap" IT solution:

### 1) Is it truly cheaper?

In one respect it is obvious; if the number at the bottom of the RFP response or quote is lower, then it's the less expensive option. While technically true, that is only a valuable assessment if you are comparing apples to apples. Before you look at the price, you need to know that you are getting the same thing for the money.

With an intangible like software, it can be difficult to ensure you make an apples-to-apples comparison. If you bought the Chevette above based solely on the price, you could be stuck with the wrong car if acceleration and top speed are necessary. Alternatively, you might say I do not need a Corvette, that Chevette will do. The point is, they have different abilities and merely comparing on price hides those differences.

RECOMMENDATION: Before assessing products, explicitly and formally define your needs/requirements and evaluate your choices based on fit first. Don't allow the price to hijack the process. Use ROI instead of price to select among solutions that fit some/all of your requirements.

#### 2) Why is it cheaper?

There's no such thing as a free lunch.
- Milton Friedman

You've assessed fit first. Then you calculated ROI and the cheap solution comes out on top. What now?

RECOMMENDATION: Treat the low-cost solution with extreme suspicion. This is your warning sign to increase your due diligence. We are currently watching one such "low-cost" vendor in the reporting automation industry cease operations and advise their existing client base they are on their own. For some of these folks, this is happening DURING their implementation of the software.

## The Action Plan - 7 Steps to Better Due Diligence

1. Double check fit-assessment. If you have any doubt, have the low-cost vendors re-demo to confirm they meet your needs.
2. Double check standard pricing variables:
1. modules/features,
2. number of users,
3. number of people being trained,
4. duration and extent of the support period,
These are all variables that might account for significantly reduced cost. Remember you want to compare apples to apples. Also, recall that skimping here may cause cost overruns later when you determine you did need more training or more support.
3. Assess the vendor track record. How many clients do they have? How many times have they solved the problem(s) you have? Ask about failed implementations and what causes their implementations to fail. Be suspicious of anyone who says they don't have any.
4. Closely assess their implementation team. Does the vendor have in-depth knowledge of not only the tool but your business process? Have they been "on your side of the table"? Have they been an HR manager or comptroller or auditor or finance officer and done the tasks that their tool addresses?
5. Contact numerous clients that are currently using their product. Spot check the specific features you are counting on using to see if the reference is using them. We have seen vendors provide references that did not even use the product being evaluated!
If the vendor can not provide an extensive list of clients who use the product, or they do not have extensive experience solving your exact issue, determine if your organization is prepared to be a Guinea Pig. We have encountered numerous organizations that have been stuck in limbo for years while their vendor tries to build what was promised.
6. Go back to the expensive vendor(s) and ask why they are so expensive. Do they charge a premium because of their brand? Did they consider something the others didn't? Was there an error in one of the pricing variables (point 2 above)?
7. Assess the low-cost vendor's stability. One way to do this is to consider their financial health, if possible.
1. If the company is publicly traded, have they ever shown a profit? Do their financial statements look like a stable, successful company? Now, if the vendor provides their software as a service (SAAS) there are (arguably) some other considerations when evaluating performance. You can find some interesting articles on SAAS performance here and here
2. If the company is not publicly traded it can be hard to do this analysis, and you may need to rely on 1 through 6 above more heavily.

Many of the steps outlined above are a great idea even when there is not a major pricing disparity. They become absolutely essential when it seems like there is a great deal to be had, and you want to avoid the cheap solution trap.

For more on this topic(s), see: Efficient, Effective and Reliable

Originally Posted on 18 January, 2017