slippinginfaith
New member
You probably know that recently, Y Combinator published its annual startup request, and one particular area has picked my interest –commercial open-source products..
YC has a history of investing in over 100 OSS startups, as listed [0]. Most of them are developers' tools, but some non-developer products are also emerging. Posthog, Twenty CRM, Tooljet, Activepieces, Refine, Laudspeaker, Jitsu, Lago can fresh out of YC over the past 3 years.
I've been developing an email marketing platform and thought about making it open-source. Initially, I was thrilled by the idea of presenting it as "Mailchimp, but open-sourced." However, I also had reservations about its business potential. So, I began exploring whether this concept could be commercially viable and what niches might be most appropriate.
The primary philosophy behind open-source development tools is to build a substantial user base by offering free access to individual developers. This model encourages these users to become paying customers as their requirements expand, such as when integrating the tool into larger teams or enterprises. Typically, it's reasonable to expect compensation for providing support, consulting, or tailored features. Yet, a highly technical open-source CRM might align differently with this model since such products are often ready for production use right from the start.
To better understand the monetization strategies and market entry tactics, I examined 40 commercial open-source companies across various domains, including CRMs, CDPs, analytical tools, CEPs, help desks, and more. Out of these, 18 have secured venture capital funding, while the rest are either self-funded or languishing.
Here's some takeaways:
The harsh reality is that the company is simultaneously working on 2 or 3 products regarding COSS. Generally, the OSS and the commercial product follow two roadmaps and goals.
When it comes to enterprise suite, Premium Support and Single Sign-On (SSO) are the most commonly offered enterprise features among the researched companies.. Many companies offer air-gapped instances that prevent tool developers from receiving data on what’s going on in self-hosted instances. This is especially important for tools that handle sensitive data, as it limits compliance issues for GDPR et al.
Also interesting is that the open-source product has the potential to expand into a platform strategy. Cal.com is experimenting with building a platform for developers using open-source tools. They provide scheduling capabilities to other applications. The same applies to RocketChat, which enables developers to embed chat experiences into the existing web or mobile app.
Each of these licenses has different requirements regarding distribution, modification, and how derivatives must be handled, influencing the adoption and contribution patterns of the software.
10 of the 18 companies that VC has funded have created their licenses. The second popular choice is the MIT license and AGPL3-0.
An intelligent open-source approach and outstanding design combination can reshape many established markets. I decided not to open-source my tool eventually, but the research has opened some avenues for other niches. For instance, as you see, there aren’t many COSS tools for GTM teams besides CRMs. We’re yet to see open-source alternatives for human email (Apollo), lead scoring (Madkudu), product-led sales (Pocus, Endgame), or enrichment tools (Apollo, ZoomInfo, Clearbit) since more tech-savvy personas are getting into the RevOps space.
If you're building something in a similar space, I would be happy to hear your perspective.
You can check out the entire post here [1]
[0] https://www.ycombinator.com/companies/industry/open-source
[1] https://nonamevc.substack.com/p/should-you-consider-building-a-non
YC has a history of investing in over 100 OSS startups, as listed [0]. Most of them are developers' tools, but some non-developer products are also emerging. Posthog, Twenty CRM, Tooljet, Activepieces, Refine, Laudspeaker, Jitsu, Lago can fresh out of YC over the past 3 years.
I've been developing an email marketing platform and thought about making it open-source. Initially, I was thrilled by the idea of presenting it as "Mailchimp, but open-sourced." However, I also had reservations about its business potential. So, I began exploring whether this concept could be commercially viable and what niches might be most appropriate.
The primary philosophy behind open-source development tools is to build a substantial user base by offering free access to individual developers. This model encourages these users to become paying customers as their requirements expand, such as when integrating the tool into larger teams or enterprises. Typically, it's reasonable to expect compensation for providing support, consulting, or tailored features. Yet, a highly technical open-source CRM might align differently with this model since such products are often ready for production use right from the start.
To better understand the monetization strategies and market entry tactics, I examined 40 commercial open-source companies across various domains, including CRMs, CDPs, analytical tools, CEPs, help desks, and more. Out of these, 18 have secured venture capital funding, while the rest are either self-funded or languishing.
Here's some takeaways:
When it makes sense.
- The dev bro is a crucial decision-maker. The engineering-driven team is led by a tech-savvy founder who prefers self-hosted technology. The second option is when the data or the engineering leadership is a key decision-maker when it comes to the problem you’re trying to solve.
- Strict security requirements. Using open-source software may streamline the process by reducing the need for a hundred XLS files from security and compliance teams. Security developers can look at the running code, even if they don't run it themselves.
- Integration-rich products. This is particularly beneficial for products with long-tail dynamics that need multiple connections with libraries, frameworks, or applications. For instance, Airbyte excels in ETL by offering unique connector support that other solutions may not provide.
Go-to-market strategy
The harsh reality is that the company is simultaneously working on 2 or 3 products regarding COSS. Generally, the OSS and the commercial product follow two roadmaps and goals.
- Community product, which makes the company open source.
- Cloud version of the product with some additional features, aka open-core.
- Enterprise products. There are two directions: the advanced managed cloud plan with security features and custom integrations and the advanced on-premise option, which is only available to select customers.
When it comes to enterprise suite, Premium Support and Single Sign-On (SSO) are the most commonly offered enterprise features among the researched companies.. Many companies offer air-gapped instances that prevent tool developers from receiving data on what’s going on in self-hosted instances. This is especially important for tools that handle sensitive data, as it limits compliance issues for GDPR et al.
Also interesting is that the open-source product has the potential to expand into a platform strategy. Cal.com is experimenting with building a platform for developers using open-source tools. They provide scheduling capabilities to other applications. The same applies to RocketChat, which enables developers to embed chat experiences into the existing web or mobile app.
License stuff
Each of these licenses has different requirements regarding distribution, modification, and how derivatives must be handled, influencing the adoption and contribution patterns of the software.
10 of the 18 companies that VC has funded have created their licenses. The second popular choice is the MIT license and AGPL3-0.
An intelligent open-source approach and outstanding design combination can reshape many established markets. I decided not to open-source my tool eventually, but the research has opened some avenues for other niches. For instance, as you see, there aren’t many COSS tools for GTM teams besides CRMs. We’re yet to see open-source alternatives for human email (Apollo), lead scoring (Madkudu), product-led sales (Pocus, Endgame), or enrichment tools (Apollo, ZoomInfo, Clearbit) since more tech-savvy personas are getting into the RevOps space.
If you're building something in a similar space, I would be happy to hear your perspective.
You can check out the entire post here [1]
[0] https://www.ycombinator.com/companies/industry/open-source
[1] https://nonamevc.substack.com/p/should-you-consider-building-a-non