If you usually follow the growth stages of open source solutions, I bet that you have ever read the article named List of 16 open-source business models in 2012 written by Peter Groen and Roger A. Maduro. Although from 2016 until now, the number will grow, the key strategy to follow will still not too different. Never afraid of mixing and matching elements from the different models are so good. However, you should careful with trying to create something brand new. That said, it had better look at some successful business models to apply open source solutions:
1. The Professional Services Model
We can say that this model still has the software completely open-source. However, some services such as consulting, installation, support, and training will be only available for a fee. In fact, consulting services will include the management and implementation of the software within specific industries. You can check the case of Red Hat, that is one of the most typical examples
2. The Software-as-a-Service Model
Software-as-a-Service Model or Saas Model see your software as a centrally hosted service that is only accessible through a paid subscription. Subscriptions are usually user, transaction volume, or time-based. SugarCRM and Heroku follow the Saas model they offer a platform solution, rather than a software solution.
3. The Open Core Model
The core software of this model still remains open-source, which is similar to the Professional Services model. In the future, they will continue to develop it. However, there will be a fee for some special features and modules extending or enhancing the core product. You can look at the case of Talend, they use the open core model to sell value-added features for core modules.
4. The Proprietary Software Model
Do you know the term GPL? It tells you that the source code of any program that uses GPLed parts needs to be made available under the same license terms. That sounds quite problematic for any company requiring your open source solutions projects to integrate with their proprietary software. There is a solution to this issue. That is developing a closed-source version. It is similar to your OSS version (note: no GPL libraries or source code).
5. The Drug Pusher Model
Unlike the Proprietary Software Model, in this model, the developer will continue to develop and update the open-source version. The developers working with this model follow popular myth persists that creating initially a market by providing their products for free. Once the customers are hooked, switching to charging exorbitant prices. After establishing a niche, they abandon completely the open source solutions project, and a version similar to the open source solutions project is now only available commercially.
Making a sound decision in choosing a business model or open source solutions will never be a simple task. Nothing is perfect from the beginning and shifting to a completely different model, later on, will put your entire client-base at risk; however, change is an adventure but beneficial. Remember that the change is not just for you, it is for your customers as well.