Commercializing an Open Source Project.
Hi all,
I have been involved in the Open Source Phoronix Test Suite (PTS) for a number of years, my partner in crime there and I are looking at how to commercialize PTS. We know that a reasonable portion of the fortune 500 already use PTS internally. So we know there is a market fit for the technology, but then we've got to work out how to commercialize.
We'd like to grow organically first without funding. So, although I'm a software manager, I'd be wading into biz dev and other areas that are somewhat unfamiliar to me, so my #1 next step is to see if I can find some mentoring to take those first unfamiliar steps.
Thoughts? Anyone been down this path before and can highlight the potholes and mines in the minefield?
@mtippett, Have you had any success in this space?
Have you explored contracting against commercial value-add solutions based on your OSS project?
I have two open source code projects and would like to commercialize one or both of them.
One project is attracting around 200 downloads per month. It's a Python client for a web API for timesheet software. The use cases are in integrations and reporting. It's a tight problem domain but commonly used. Obviously relies upon the uptake of the timesheet software which appears to be popular enough. My project is listed on the vendor website as "the" Python library that's available for integrating with their website. I am not sure if there is much opportunity beyond contracting integration and reporting work.
The other project is attracting about 1,000 downloads per month. It's a Python library which translates MS Excel workbooks into Python. Use cases include quality control and testing of code as well as removing or reducing the work relating to translating Excel spreadsheets to computer code by hand. It is a very broad problem domain. I am certain there are opportunities in value-add solutions which can be charged for.
We haven't commercialized, but we know there is a pull.
As @hatkyinc mentioned below, those are the general three models as a business. It sounds like 2) and 3) aren't really an option, so I'd suggest looking more closely at 1). However if they are fully OSS, you could also look at doing patreon or similar.
I'm not someone who would do the "donate" link on one of my projects, however there are lots of people who feel that it is the right thing to do and do it often. Note that if you do look to commercialize, it goes a bit against the patreon/donate ideal.
Thanks for that.
In my case, the library that translates Excel to Python has potential for value add through a separate product which uses the open source project but is a commercial offering. I guess that's a modification on "option 3".
I hadn't thought of a patreon specifically but had considered a similar business model where there's an enterprise or professional edition which gets things before they turn up in the open source/"community" edition. Again, this seems to be a specialization of "option 3".
Good luck with your journey.
I'm interested to hear how you go.
Cheers
The common paths to monotizing OSS:
Does any of these appeal to you?.. or do you see a specific offer in mind?..
There are a few paths that we have had customer interest (we weren't ready) or actual revenue.
The revenue models we are looking at are:
So it isn't the actual opportunities, it's the where to start and that first 'pay us' part that is foreign to me personally. So I'm really looking for mentoring or advice on how to take those first steps.
My current view is to focus on the customer experience from discovery to commitment, and then the second part is to engage with customers on a listening your to understand where they may want to level up.