The Difficulty of Modernizing Legacy Software

As part of my recent project researching ideas on building high quality prospect lists, I reached out to several different providers. One of the companies had a really promising product that allowed for slicing and dicing data, presumably from Dun & Bradstreet or Hoovers. After getting excited about their technology, merely based on their marketing collateral, it came time for the product demo from a sales rep.

Guess what?

The application with a Windows product with no web-based components at all. Their response to the question about them building a Software-as-a-Service product: no plans at all. Now, I don’t know how successful this company is but it was pretty amazing to see a product that clearly should be in the cloud, connected to CRMs like salesforce.com and SugarCRM, and all around part of the normal web ecosystem.

The point here isn’t what one single company should do, but rather the difficulty of modernizing legacy software. Once companies become successful with one product, working one way, it is incredibly difficult to introduce a new or modern product built from the ground up.

With difficulty comes opportunity. Startups don’t have the legacy baggage of code debt, existing customer needs, and the status quo. Wherever you see a legacy system that is still continuing along, there’s room for a startup to do a modern version of the product, in the cloud, and be successful.