New eXo Platform OEM Program to Modernize Aging Enterprise Software
SAN FRANCISCO, Calif., May 6, 2014. eXo, the enterprise social platform company, announces today its OEM Partner Program, bringing its social collaboration, mobile, and cloud capabilities to independent software vendors who need to modernize their own solutions. While analysts are forecasting slowing growth in sales of traditional enterprise software in coming years, they predict high growth in sales of social collaboration solutions.
This means that, to thrive in the enterprise software market, vendors must be able to offer well-developed social collaboration, mobile, and cloud capabilities. With this in mind, software vendors are looking for solutions to modernize their own offerings, add social collaboration capabilities, and deliver the value their customers expect. Through its OEM partnerships, eXo can help vendors to:
- Modernize their software to deliver additional value to customers.
- Lower their R&D costs by providing out-of-the-box eXo Platform features that can be embedded in their existing products.
- Reduce their time to market by providing a mature off-the-shelf solution that is fully customizable.
Oualid Chaker, eXo’s Executive Vice President of Business, says, “We meet many companies that tell us they have demand for social collaboration features, but unfortunately, they do not offer these out of the box. I’m very glad we are now offering a solution to these concerns. It will greatly benefit the customers of these companies.”
The eXo OEM Partner Program offers support to meet the full range of partners’ needs through four different scenarios:
Front-end portal development – The classic way that eXo is leveraged is to build a front-end portal that unifies one or several software suites.
Vertical solution development – In this scenario, eXo provides the backbone for a social collaboration experience; the platform’s flexibility allows it to be adapted to very different needs. Vendors who operate in specific industries or niche markets have a deep understanding of the precise needs of their audience. These types of business can build an entirely new product simply by customizing eXo Platform.
White labeling of eXo Platform to complete an existing offering – Under this model, OEM partners can distribute eXo Platform under their own brands. With eXo Platform UXPaaS, they can also accelerate delivery of their products as SaaS offerings using the underlying cloud technology, which scales to the partner’s needs.
Reuse of specific layers of eXo Platform to augment or complement existing products – Although eXo Platform’s user interface is very flexible and highly customizable, some companies want to build and maintain their own interfaces. These partners can leverage eXo’s APIs to augment their own software offerings while maintaining their own interface designs.
Accessing eXo’s array of services and support, as well as its more than 10 years of R&D, OEM partners can focus on their core competencies and let eXo Platform deal with the social collaboration, mobile, and cloud features.
Holly Holt, VP of Product Management, WennSoft: “Our commitment to our customers is to deliver innovative solutions that will grow with them. Our eXo partnership supports our ability to do so. Signature Interaction Manager and the audience specific Connect(s) leverage the eXo Platform providing the flexibility and extensibility required by even our most sophisticated customers.”
eXo Platform OEM partnership benefits include:
Licensing Benefits – Partners have access to eXo Platform Enterprise Edition, and can white-label and embed eXo Platform Enterprise in their own software. The pricing is adaptable to accommodate partners’ business models.
Technical Support and Maintenance – Partners can access support with an unlimited number of tickets.
Consulting, Training, and Technical Account Management – Partners have access to training, certification and consulting services to bootstrap product integration and development.
Or continue reading about the eXo Platform OEM Program with these two follow-up articles: