When Good Software Dies: How Great Platforms Become Forgotten Assets
When Good Software Dies: How Great Platforms Become Forgotten Assets
By Jeff Bassill | jeff@mycurisk.com
Every technology executive has experienced it. You spend months evaluating vendors. You sit through demonstrations. You negotiate contracts. You implement the system. The software works exactly as promised. Then the vendor gets acquired.
A few years later the roadmap slows. Key employees leave. Enhancements become less frequent. Eventually customers are encouraged to migrate to another platform and the product quietly disappears.
The software worked.
The customers were happy.
The technology remained viable.
What changed was the corporate strategy behind it.
For credit unions, that is an important lesson. When we evaluate a loan origination system, core platform, or other significant technology investment, we are not simply buying software. We are buying into a vendor's long-term strategy.
One of the best examples I experienced personally was StreamLend Velocity.
Discovering Velocity
I first encountered StreamLend Velocity in 2007 when our credit union needed a more robust decision engine to support a growing indirect lending program.
At the time, many core-integrated loan origination systems felt like bolt-on applications with limited customization and rigid workflows. Most seemed designed around the core processor rather than around the lending operation itself.
Velocity felt different.
It was built around workflow automation and paperless processing long before those became industry buzzwords. We could create custom fields, custom calculations, automated workflows, and decision paths that reflected how we actually wanted to operate. It integrated with our core while still providing the flexibility of a standalone lending platform.
Just as important, the service was exceptional. Enhancements happened quickly, questions were answered by people who understood lending, and the platform continued evolving.
At the time, it felt like a product that would be around for decades.
The Golden Era
Velocity was developed by IA Systems, a company focused on lending technology for financial institutions.
What many people may not realize is that IA Systems was originally part of Securian Financial. Looking back, that connection may help explain what made Velocity distinctive. It was designed around workflow, decisioning, and product integration at a time when many competitors were still focused primarily on loan processing.
Their original StreamLend platform appeared in the late 1990s, and Velocity represented the next generation of that vision.
Today, configurable workflows are expected. In the mid-2000s, they were a differentiator.
Velocity quickly became a legitimate competitor to the industry's largest loan origination platforms.
Ironically, that success may have contributed to its eventual demise.
The Acquisition Trail
Successful software attracts buyers.
In 2007, Open Solutions acquired IA Systems from Securian. The move made strategic sense. Velocity was a strong lending platform and complemented Open Solutions' broader technology offerings.
Then, in 2013, Fiserv acquired Open Solutions, a transaction largely viewed through the lens of the DNA core platform.
Velocity became one of many assets inside a much larger organization.
I cannot know every discussion that happened behind closed doors, but from a customer's perspective, the acquisition marked the point where Velocity stopped being a flagship product and became one application in a massive portfolio.
When large technology providers acquire companies, resources naturally flow toward the highest-priority products and strategic initiatives.
That is not malicious.
It is simply how large organizations work.
The Forgotten Asset Problem
This leads to a question I have wondered about for years.
How many innovative software platforms still exist inside large technology companies as forgotten assets?
Acquisitions often bring together products, development teams, intellectual property, and customer relationships. The acquiring company typically wants certain assets more than others.
Over time, the people who understood why a product mattered leave, retire, or move into different roles.
Eventually institutional memory disappears.
The software may still exist.
The code may still exist.
The intellectual property may still exist.
What disappears is the context.
For the institution left running the software, this lost context creates a silent operational risk.
Without the original architects, auditing, updating, or even fully understanding those embedded compliance controls becomes incredibly difficult.
A decade later, there may be very few people left who remember why the platform was considered innovative in the first place.
That may be the real lesson from Velocity.
Good software does not always die.
Sometimes it simply becomes a forgotten asset.
Could Velocity Be Revived?
Occasionally someone asks an obvious question:
“If the software was so good, why not bring it back?”
The answer is that software is more than code.
Modernizing a twenty-year-old platform is difficult, but it is increasingly possible. Artificial intelligence is making code conversion, testing, documentation, and modernization far faster than they were only a few years ago, and not just in theory. Fiserv itself partnered with Cognition, the company behind the autonomous coding agent Devin, in May 2026 to accelerate modernization of its own legacy core banking code.
The harder challenge is recovering the business knowledge embedded within the software.
Every mature lending platform contains thousands of rules, exceptions, compliance controls, and workflow decisions accumulated over years of real-world operation.
AI can help rewrite code.
It cannot easily explain why a particular lending exception was added in 2004 or why a compliance safeguard existed in a particular workflow.
The greatest barrier to reviving software today is often no longer technical.
It is strategic.
Whether any organization would see value in revisiting a platform like Velocity today is a strategic question, not a technical one.
There is a small irony worth noting. IA Systems, as I recall, stood for Internet Architect. Twenty years later, AI may be the thing that decides what is left of it.
The Risk Management Lesson
Technology risk discussions usually focus on cybersecurity, outages, and vendor performance.
We should spend more time discussing acquisition risk.
When evaluating a major technology partner, credit unions should ask:
• How important is this product to the vendor?
• Is it considered a strategic platform?
• How many developers support it?
• What happens if the company is acquired?
• Is there a long-term roadmap?
Those questions may be just as important as functionality or price.
Final Thoughts
StreamLend Velocity did not disappear because it was a bad product.
Quite the opposite.
It was ahead of its time in workflow automation, customization, and lending process management.
Its story reminds us of an uncomfortable reality in financial institution technology.
The greatest threat to a software platform is not always technical failure.
Sometimes the greatest threat is becoming part of a larger corporate strategy where its future no longer aligns with management's priorities.
When credit unions buy software, they are not just buying code.
They are buying a seat on a vendor's roadmap.
And if that roadmap changes, even great software can become a historical footnote.
One final question remains: Is Velocity truly gone?
Public references to the platform become surprisingly scarce after the Open Solutions era. If your institution still runs Velocity, maintains a customized descendant of it, or recently completed a conversion away from it, I would enjoy hearing the story. The people who used the system may be the only remaining historians of what happened next.
The views above, including the speculation about Velocity's fate and its acquisition history, are my own and do not represent the official position of Kings Federal Credit Union.
