Anyone expecting big announcements about HP Engage during the OpenText Enterprise World conference would have left disappointed. 

It's been almost three months since Waterloo, Ontario-based OpenText announced its acquisition of HP’s software assets, but there's still very little information available about how the acquisition will play out. 

We can however use a number of clues provided by the company to inform some high level predictions about the future of HP software assets.

Caveat: what follows is my private opinion, based on publicly available information, including press releases, interviews with OpenText executives, information about the company’s past acquisitions, as well as information about its product architecture and services. None of the predictions below come from or are endorsed by OpenText — in other words, no warranties — treat these as speculative.

My predictions:

1. Development Will Continue on All Products

OpenText has nothing to gain by sunsetting any of the HP products. First of all, it would immediately impact their maintenance revenue. Second, having multiple options in their tool box allows OpenText to take the consultative sales approach to a level inaccessible to its competitors. “Hello, Mr. Customer. Please tell us what your pain points are, and we will suggest a solution from our broad portfolio that is the best fit for you.”

2. Overlapping Products Will be Backed by Common Underlying Technology

Developing multiple CMSs or DAMs in parallel would be inefficient and would lead to multiple product development teams duplicating each other’s work. 

Learning Opportunities

The likely outcome is that OpenText will abstract the best aspects of its different products into modules or libraries that can be shared between its different solutions. The company's good track record of building modular solutions based on web services has proven its product integration ability. 

What this would look like in practice is that TeamSite and OpenText WEM (a.k.a. Vignette), as well as MediaBin and OpenText Media Manager (a.k.a. Artesia) could share a common platform and functionality, but would differentiate through their UI, target business use cases, target verticals, etc.

3. We'll See a Stronger Push to the Cloud

In strong contrast with HP, which struggled to put its products in the cloud, OpenText has been much more successful with its cloud strategy. Expect to see more HP products being deployed into the cloud and being provided either as SaaS or, more likely, as a managed service.

4. Deeper Native Integration Across the Board

As stated above, OpenText has a proven track record of product integration capabilities. We can expect to see integration between MediaBin and OpenText WEM, TeamSite and OpenText Media Manager, and integration of all of the above with the company’s newly announced cognitive analytics platform, Magellan.

Regardless of whether my predictions prove right or not, this will be an interesting year for enterprise technology, as OpenText throws down the gauntlet to Adobe, IBM, Microsoft and Slack, all at the same time. 

fa-solid fa-hand-paper Learn how you can join our contributor community.