I am giving away my code as FOSS, so I'm doing the following, in this order:
1. Charging for bug reports or feature requests.
2. Support. (And I have great examples of public support as marketing.)
3. Consulting. (This would be exclusively to help companies trying to use my software, but unlike support, it would be about writing the stuff that uses my software and ensuring the client understands it so that I could do a handoff. The result would be carefully commented and documented code, probably just short of literate programming [1].)
4. SaaS. (If I did this, the server might not be FOSS, but the client would be, and it would use encryption.)
gavinhoward|2 years ago
1. Charging for bug reports or feature requests.
2. Support. (And I have great examples of public support as marketing.)
3. Consulting. (This would be exclusively to help companies trying to use my software, but unlike support, it would be about writing the stuff that uses my software and ensuring the client understands it so that I could do a handoff. The result would be carefully commented and documented code, probably just short of literate programming [1].)
4. SaaS. (If I did this, the server might not be FOSS, but the client would be, and it would use encryption.)
[1]: https://en.wikipedia.org/wiki/Literate_programming
raybb|2 years ago
Do you charge per report / request? Or is it a subscription (storygraph has this model)?
It seems like a great idea to lessen the workload and focus on people who actually might turn into customers.
jjice|2 years ago
shyn3|2 years ago
djaro|2 years ago