However, I'm unsure of this model for a few reasons. If potential customers are aware of this "approaching open sourcing", will there be a significant portion who'll just wait? If they are not aware of this event, would they feel ripped off or less hesitant to purchase any other software I write in the future? Are there ways of hopefully mitigating both these potential issues - and is there anyone here who has done something like this successfully?
Ask HN: Feedback on an Open Source business model
1–6 of 6 posts
Re: Ask HN: Feedback on an Open Source business model
#2Re: Ask HN: Feedback on an Open Source business model
#3Re: Ask HN: Feedback on an Open Source business model
#4Charging for something when you know you are going to give away = Not a good idea. If there is existing market that you can reach, you can go with paid option. Else start with open source and then add either paid version (more features) or supported version (dual license). Service in cloud is another option.
Re: Ask HN: Feedback on an Open Source business model
#5Charging for something when you know you are going to give away = Not a good idea. If there is existing market that you can reach, you can go with paid option. Else start with open source and then add either paid version (more features) or supported version (dual license). Service in cloud is another option.
Why isn't it a good idea?
Re: Ask HN: Feedback on an Open Source business model
#6Charging for something when you know you are going to give away = Not a good idea. If there is existing market that you can reach, you can go with paid option. Else start with open source and then add either paid version (more features) or supported version (dual license). Service in cloud is another option.
Why isn't it a good idea?