Where Good Tools Go To Die

By | | 3 min read

Tag , , ,


Over the years working in the field of IT I’ve seen many products come and go. Some weren’t all that good in the first place, while others were very promising but ultimately failed to deliver on expectations. When I was working in the large enterprise world, we (those of us who cared) compared notes on what small companies were ripe for takeover and which of the much bigger software companies would buy and ultimately ruin their product. Basically we were betting that some software giant (usually companies with 2 or 3 letter acronyms) would buy a useful product and kill it over time.

How Do You Kill Software?

ripWhat do I mean by “kill it”? It’s not like software is a living, aware entity (yet). Here is what it means to me to “kill” a software product:

  • Let it stagnate so that it falls behind the times and becomes outdated
  • “Integrate” it with your other products in a loose (i.e. crappy) way such that it is a pain to configure and provides little value anyway
  • Ignore the needs (new features and functionality) of the majority of your customers and focus solely on the needs of a few large customers who spend the most money and scream the loudest
  • Provide poor customer service after the sale (slow response to issues, unresolved support calls, etc…)


Time to take a trip down memory lane…

  • Remember Cyanea? They were founded in 2001, bought by IBM and rename ITCam in 2004. Currently a high ranking member of my “Promising Tools that Went Nowhere” list. Thanks IBM!
  • And who can forget Mercury and HPs brutalization of Performant Diagnostics? So very young. So very sad.
  • Then there was the absolutely horrific beat down of Precise i3. Precise was bought by Veritas, who was then bought by Symantec. Then when Symantec had brought i3 to the brink of death they sold it to a VC company which brought back the Precise name but did little to revive i3. Another promising tool ruined.

There have been other similar acquisitions in the past few years and only time will tell if the trend of large companies snuffing out promising tools will continue. You can see a list here.


Why does it always seem to happen? Why can’t a large software vendor keep a product they purchased relevant? I really believe that it is not so much a case of “can’t” as “won’t”. “Can’t” implies that the company is incapable from a technical perspective. “Won’t” has a much worse connotation. “Won’t” is a calculated decision that the company can realize more net profit by selling a product based upon what it once was than by investing and keeping that product current and relevant (more risk). “Won’t” is about putting Wall Street expectations for your next quarter ahead of the needs of your paying customers. “Won’t” seems like a good idea in the short term but ultimately leads to the death of a product in the long term.

Choose Wisely


I really hope your favorite software products are not in the process of being killed by a giant software company. It’s really a shame to watch it happen over and over again.

When you’re deciding which software products to purchase it is important to understand what type of company you are dealing with. Look at their history, look at their customer satisfaction and Net Promoter scores, ask about their corporate goals and direction. If you choose the wrong company to do business with your new favorite software product might be headed toward an early demise.

Jim Hirschauer

Jim Hirschauer

Jim Hirschauer is a Technology Evangelist for AppDynamics. He has an extensive background working in highly available, business critical, large enterprise IT operations environments. Jim has been interested in application performance testing and monitoring since he was a Systems Administrator working in a retail bank. His passion for performance analysis led him down a path where he would design, implement and manage the cloud computing monitoring architecture for a top 10 investment bank. During his tenure at the investment bank, Jim created new processes and procedures that increased overall code release quality and dramatically improved end user experience.